Skip to main content

Flows Overview

An integration in Prismatic consists of one or more flows, each serving a specific purpose. For example, if you're building a bidirectional integration with Salesforce, you might have several flows:

  1. A flow that is invoked by your app, and syncs leads from your app to Salesforce.
  2. A flow that is invoked by your app, and syncs contacts from your app to Salesforce.
  3. A flow that queries Salesforce for new leads, and syncs changes to your app.
  4. A flow that queries Salesforce for new contacts, and syncs changes to your app.

In the low-code designer, a flow represents a series of steps that run one after another. Each step runs an action (like "Create Salesforce Lead" or "Get Salesforce Contacts"). You can feed the results of steps into subsequent steps, so the results of "Get Salesforce Leads" can be fed into a step that syncs SFDC leads to your app.

A flow in code-native represents a TypeScript function that runs when the flow is invoked. Your flow's code can be as simple or complex as required - it can be a simple HTTP call to fetch data from a third-party, or it can be a sophisticated function that fetches, parses, filters and transforms data from one app to another.

Regardless of whether you're using low-code or code-native to build your integrations, each flow begins with a trigger. A trigger determines when the flow starts - either on a schedule (for example, every 5 minutes) or in response to an app event (for example, when a new file in Dropbox is created).

When a flow's trigger is invoked, an execution starts. By default, multiple executions of a flow run concurrently. You can optionally run executions sequentially using a FIFO queue.