You are here:
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.
Required Editions
| View supported editions. |
| This feature requires the MuleSoft for Flow: Integration add-on. Professional Edition requires the API access add-on. To purchase, 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. |
Use MuleSoft for Flow: Integration Templates
You can access pre-built templates for specific MuleSoft for Flow: Integration connectors. Use these templates to setup flows quickly with pre-configured logic and field mappings for your connector. You can use templates and then make your own connections. This approach makes it faster to set up connections while still letting you change the integration to fit your needs.
AI Pre-Built Flows use Agentforce AI to generate integration automations based on curated prompts. After you select a use-case-specific prompt and configure connections in the wizard, Agentforce AI builds the flow on the Flow Builder canvas. This approach streamlines the setup and deployment of complex integrations.
Use Connector Versioning
MuleSoft for Flow: Integration connectors are designed to maintain their currency through a structured update process. Automatic updates are applied for minor and patch versions, which helps make sure that integrations remain secure and compliant. To maintain control and stability, manually upgrade your major versions. As they become available, new connector versions appear in Show advanced options, where you can select specific action or trigger versions.
Use Conditional Triggers
Define conditions on trigger fields for some connectors to ensure your flows run only when necessary, reducing API calls and improving efficiency. Select fields and use AND, OR, or custom logic to customize the automation to your business processes.
Manage Input Values
Manage input values efficiently with support for static and non-string value providers. Dynamic type providers for Apex fields improve integration with external APIs, and selected values appear as readable labels.
Return Records with Get Records and Get Issues
Use actions like Get Records or Get Issues to return records from external systems based on custom filter logic and specified conditions.
In the Set Input Values for the Selected Action section, click Select Fields to add filter conditions. These actions define the queried object, specify operators, provide field selection and sorting, and provide metadata for formatting.
Map Custom Fields
Map custom fields for unique data Access and map custom fields from third-party connectors to include custom data in your integration logic.
To map custom fields, add an Assignment element to your flow, and map the fields under Set Variable Values.
Trigger Flows on File Events
The Automation Event-Triggered Flow type with the File Attach event automatically starts a flow when a file that matches your criteria is attached to a record. Configure the event to trigger based on criteria such as file type, extension, name, or the Created By field. Record-Triggered Flows also support file attachments when triggered by a new record or an updated existing record.
To configure, create the flow, go to the Start node, click Select Event, select File Attach, and select an event.
Use File Attach Actions
MuleSoft for Flow: Integration file actions support binary file transfers up to 15 MB, enabling your flow to upload and return files, such as email attachments or documents, from an external system. The actions provide a file as a reusable object variable for subsequent flow actions, such as sending a file to an external system.
For files retrieved or created during a flow run, the actions use standard Salesforce file capabilities by using the ContentDocument object for temporary storage. The actions provide the file as an output variable for use in subsequent flow steps. This feature also provides the Create Records element to add a file attachment to newly created records.
Connector-driven file operations create files. Delete files after they’re no longer needed. Delete files after flow use by adding a Delete element to the flow, or manually delete files from the Files tab.
Control Polling Frequency
Increase the speed at which your External System Change-Triggered flows respond to changes by polling triggers more frequently.
To configure polling frequency, open the flow's Start node and select the polling frequency under Set Input Values for the Selected Event.
