You are here:
Connecting to an External System with a Connector
You can use MuleSoft for Flow: Integration connectors in any flow type to connect a flow's actions to an external system. To trigger a flow when an external system changes, select the External System Change-Triggered flow type.
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. |
Connect to an External System
You can reference a MuleSoft for Flow: Integration connector in two ways within your flow. To initiate a flow based on external system changes, use an External System Change-Triggered flow. This flow type uses the connector to poll the external system for matching triggers at your specified interval. Alternatively, add the connector's action to a new or existing flow to any new or existing flow to push changes to an external system.
External System Change-Triggered flows use a poller to fetch records on the selected schedule.
Polling Behavior and Deactivation
- Retries: When polling fails, the flow tries again up to 3 consecutive times.
- Automatic Deactivation: Happens after the third consecutive poller failure. This behavior applies to poller-level failures (for example, authentication or connectivity), but doesn't apply to individual record-level failures.
- Reactivation: If poller failure deactivates the flow, resolve the underlying issue and reactivate the flow manually.
Poller Limits and Exceptions
- Pre-execution Failures: If the poller fails before execution starts, no fault path is available at the Start element.
- Payload Limits: A poll response that exceeds 128,000 characters (including data and metadata) exceeds the payload limit.
For limits and full behavior details, see MuleSoft for Flow: Integration Limits & Considerations.
To create a flow that uses a connector as an action, 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
For an overview of how to set up MuleSoft for Flow: Integration and to create automated connections between systems, refer to Get Started with MuleSoft for Flow: Integration.
- Understand MuleSoft for Flow: Integration Features
Optimize and scale your business processes by using pre-built templates, automated versioning, and advanced trigger logic to manage MuleSoft for Flow: Integration flows. - Understand Value Maps in MuleSoft for Flow: Integration
Use value maps to translate source values to target values by using a reusable global resource across flows. - Get Started with MuleSoft for Flow: Integration
Use MuleSoft for Flow: Integration to create automated connections between systems, so you can keep data up-to-date, reduce manual work, and respond faster to business events. - Create a Flow with a Connector as a Trigger
To trigger a flow when a change happens in a third-party system, use an External System Change-Triggered flow. A poller checks for new records on a schedule and creates flow interviews when records are found. Create the flow from scratch or from a template. - 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. - Create and Manage Value Maps
Create, update, and delete value maps from the Global Flow Resources page to reuse mapping logic across flows. - Create, Evolve, and Summarize MuleSoft for Flow: Integration Flows with Agentforce (Beta)
Use natural language to generate AI-powered MuleSoft for Flow: Integration flows that connect your org to external systems and then edit or summarize existing flows by using Agentforce.
