After adding a feature, you can add resources to the feature, including flows. Flows define the data transfers between connectors in your integration. 

In most situations, you will create a new flow.

• New Flow: Build a new flow from scratch.

• Existing Flow: Select an existing shared flow that has already been created for your workspace. These flows are visible to other workspaces and integrations. For existing flows with configs, you must map these configs to the integration when adding the flow.

Create a new flow

1. Open the feature you want to add a flow to.

2. In the Flows section, select Add Flow.

3. Select Create New and complete the following fields:

   1. • Enter a Name for the flow.

      • Select Next.

      • If you already have configurations set up for your integration, choose from the list.

      • Select Next.

      • Review and select Save.

      • Open the flow to start building it. For guidance, see Create a Flow.

4. Open the flow to access settings and make edits, if needed.

   1. • Select Edit. 

      • Flows default to Active on Sync, which means the flow will automatically switch to Active when the feature is set to Active. If you don’t want the flow to automatically activate, toggle this option off.

5. To make additional edits, go to your workspace and access the flow from the Flows page.

Add an existing flow

In the case that you do need to add an existing flow, complete the following steps.

1. Open the feature you want to add a flow to.

2. In the Flows section, select Add Flow.

3. Select Add Existing and choose a shared flow from the list.

4. For an existing flow with no associated configs, there won’t be any configuration mapping, so select Next.

For an existing flow with configs, map each existing flow config to an integration config. Choose or enter a New Config Title from the dropdown list. Repeat for all configs.

• If a flow config key matches an integration config key, App Xchange suggests a match. If you don’t want to use this match, you can choose a different config or enter a new one.

• You must map all configs before you can add the flow to the integration.

A mapped config looks like the following:

5. Review the details and select Save.

At this point, if you have set up an integration and added at least one feature with at least one service and flow, you can sync the integration definition to your development workspace for testing.

Or you can continue setting up components such as Integration Configurations.