Flow Components

Flows are user-created workflows that define the data transfers between connectors on the App Xchange platform. In other words, a flow moves data.

A flow is one of the most important components of an integration, as it uses a series of triggers, steps, and flow configurations to make all the critical business decisions and data transformations.

You create flows in your workspace using App Xchange’s flow builder, which is a low-code JavaScript environment intended to simplify the flow writing process for technical and non-technical users. Flows can be shared, called, or made into a template to be used across integrations in your workspace.  

Required Flow Components

Certain components are required in every flow. At a minimum, each flow must have the following:


Flows must have an entry point, which is called the trigger. A trigger starts the flow. Each flow requires one trigger. 

For example, the most common type of trigger is a Cache Event, which starts a flow when there is a Create, Update, or Delete of the connector's data object. For more information, see Triggers.

Flow Steps

After the trigger, a flow requires a series of steps to accomplish different tasks. There are many different types of flow steps, which you can combine to define business decisions in the integration. To add flow steps, select the Plus signs. For more details, see Flow Steps.

Additional Flow Components

Outside the required components, there are additional aspects that are useful to anyone building a flow:

You can also use the following features to help you when building a flow:

View saved versions of the flow

Choose a version from the dropdown list to see previous interactions of a flow. For more information, see Revise a Flow.

Define the flow configuration

Define the flow configuration for different instances of the flow. Select Define Configuration to set this up. For more details, see Configure a Flow.

Enter configuration values

After you define the flow configuration, input configuration values for that specific flow instance. You can only edit configuration values here if the flow is not managed by an integration.

View history of flow runs

From the Runs tab, see the history of the flow runs. Here you can also see the version number of the flow for every run, which you can also look up in the revision history. For more details, see Flow Run History.

View additional flow data

From the Data tab, look up cache objects or actions that the flow might interact with. You can search by triggers, lookups, or actions for that flow.