You are here:
Integrations Limitations & Considerations
When establishing connections to external systems, keep these limitations and considerations in mind.
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. |
General Limits
- The external system occasionally limits the number of OAuth connections with a single set of credentials. For example, the Salesforce developer account has five connections by default, with higher limits available for other types of orgs.
- A connection can fetch a total of 10,000 records in a single operation and the maximum payload size per call is 6 MB. For best results, limit the number of records in a single operation to 5,000 or less.
Managing Connection Access in Flows and Usage in Flows
Named Credentials created and managed by Salesforce power connections. Any user in the org with the Manage Integration Connections permission or the Customize Application permission can make callouts at run time. To apply tighter access control, restrict which users can run the flow.
Connections work across multiple flows. When you update credentials, the changes take effect in the next flow run. This update feature is useful for rotating passwords or switching from sandbox to production. You can’t delete a connection that a flow is using. To block access to your external system, edit the connection and provide incorrect credentials to make it invalid.
Agentforce Features: Dynamic Actions Limitations
Agentforce features in MuleSoft for Flow: Integration don’t support dynamic actions in third-party connectors. A flow can’t use Agentforce if it relies on dynamic metadata from these connectors: NetSuite, Salesforce, and Zendesk.
Controlling Flow Access with Profile and Permission Set Restrictions
With Profile and Permission Set Restrictions, you can manage who can access, edit, or run a flow. Salesforce enforces these restrictions across all entry points, including when a flow is called as a subflow. In this scenario, you can override default behaviors and apply granular security to individual flows. This security makes sure that only users with the required permissions can access and run them.
Managing Connections Created During a Pilot Release
If your org participated in the MuleSoft for Flow: Integration pilot, reusing connections from that release can cause errors. For example, flow actions that make callouts can fail due to missing authentication tokens. To ensure existing connections work, Salesforce admins must grant users access to the UserExternalCredential object.
