You are here:
Create a Flow with a Connector as an Action
To integrate your flow with an external system, add MuleSoft for Flow: Integration connectors as actions to all existing flow types. You can add connectors to flows that trigger external system changes, records, schedules, Data Cloud-triggered flows, or autolaunched flows.
Required Editions
| View supported editions. |
| This feature requires the MuleSoft for Flow: Integration add-on. Exceptions are segment-triggered flows, activation-triggered flows, and broadcast flows, which don't require the MuleSoft for Flow: Integration add-on. Professional Edition requires the API access add-on. To purchase an add-on, contact your Salesforce account executive. |
| MuleSoft for Flow: Integration features used with Agentforce require the Foundations or Agentforce 1 edition. To purchase these editions, contact your Salesforce account executive. |
Create a Flow from Scratch
Create a flow that uses an external system as an action.
- In the Automation app, select the Flows tab, and then click New.
-
Select one of these flow
types:
- Autolaunched Flow
- Contact Request Flow
- Individual-Object Linking Flow
- Platform Event-Triggered Flow
- Recommendation Strategy (Next Best Action NBA)
- Record Triggered Flow
- Schedule Triggered Flow
- Screen Flows
- User Provisioning Flow
The flow opens in Flow Builder. -
If necessary, configure the Start element or trigger.
If you selected Record-Triggered Flow, when you configure the Start element, turn on the Add Asynchronous Path option. Updating the record requires the user to have the Manage Integration Connections permission.
-
Add and configure the action.
-
Click
and then select Action.
- In the Search Actions panel, select Connectors.
- Select a third-party connector and choose from its actions.
- Fill out the required fields for that action.
-
Create a new connection or use an existing connection.
A connection test runs automatically.
-
Click
-
In Set Input Values for the Selected Action, select a value for
each field.
An input value can be a primitive data type or an object data type. If an input value is an object data type, you can configure any of the fields on the object. Required input fields are selected by default; however, you can select more fields to include in your input values.
- In the Body section, to select fields to map, click Select Fields. After you select the necessary fields to map, click Done.
-
Map the fields.
To create and manage reusable value maps, see Create and Manage Value Maps.
- For simple mappings, you can use Inline View by using the Friendly Resource Picker.
- Complex mappings, such as lists, requires the use of Transform View. Mappings from Inline View persist when you swap to Transform View. See Transform Data in Flow. To apply value mapping in Transform, see Use a Value Map in Transform.
TipTo make sure that the flow continues after a brief pause, add a Wait for Amount of Time element to your flow after a Create, Update, or Delete action. By selecting 1 Minute in the Amount of Time field, you make sure that the system processes changes before the third-party action proceeds.
- Optionally, select Show advanced options to see if a new version of the connector is available.
- Save, test, debug, and activate the flow.
Create a Flow from a Template
Use a pre-built template that uses an external system as an action.
-
Choose how to access the flow templates.
-
Select the Integrations tab and select a third-party connector from the Get Started with Connectors section.
-
Select the Flows tab, and then click New, and then click Triggered Automations.
-
- Select a template and click Next.
- Enter values for Label, API Name and Field API Name.
- Optionally, set custom fields.
-
Click OK.
The flow opens in Flow Builder. The template has a pre-built flow that offers a starting point with established logic and field mappings. Your flow has errors until you configure your connections. Customize the other elements in your template to your specific needs.
- Save, test, debug, and activate the flow.

