---
schema_version: "1"
id: 7b887e0986c38f4989d4c0440c220b5d7aed20ba524b4851599788fcbd9218c5
title: Integrations Limitations & Considerations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_flow_considerations_ala_connections.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_flow_considerations_ala_connections.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 71059312cf63be02ce3b198dd5e852e9ddd33c0d928e3a83168071c774ee4b58
description: When establishing connections to external systems, keep these limitations and considerations in mind.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Integrations Limitations & Considerations

When establishing connections to external systems, keep these limitations and considerations in mind.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=platform.flow_ref_supported_editions.htm&amp;release=264.0.0&amp;type=5" title="Learn about the editions and user interfaces that support Flow Builder. Some Flow Builder features integrate with other Salesforce products that require additional licenses.">View supported editions.</a></td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">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. <strong>Professional</strong> Edition requires the API access add-on. To purchase an add-on, contact your Salesforce account executive.</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">MuleSoft for Flow: Integration features used with Agentforce require the Foundations or Agentforce 1 edition. To purchase these editions, contact your Salesforce account executive.</td></tr></tbody></table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_note.png)

Note You can edit or delete connections only in the Automation app.

## 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](https://help.salesforce.com/s/articleView?id=xcloud.named_credentials_about.htm&language=en_US) 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](https://help.salesforce.com/s/articleView?id=platform.flow_distribute_security.htm&release=264.0.0&type=5 "Limit which users can run flows based on their user record, profile, or permission set. To apply more granular security to an individual flow, override the default behavior, then grant access to that specific flow based on user profile or permission set."). 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.