Skip to main content

Flows Overview

An integration in Prismatic is comprised of one or more flows that each serve a specific purpose. For example, if you're building a bi-directional integration with Salesforce, you might have a few 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.

A flow in the low-code designer represents a series of steps that are run, one after another. Each step runs an action (like "Create Salesforce Lead" or "Get Salesforce Contacts"). You can feed the steps of results 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 you'd like - 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 if 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, which can be on a schedule (i.e. "Every 5 minutes") or can be invoked in response to an app event (i.e. "when a new file in Dropbox is created.").

When a flow's trigger is invoked, an execution starts. Prismatic is designed to scale, and multiple executions of a flow can run concurrently.