You are here:
Connect to an External System
Create a connection to an external system in the Automation app.
Required Editions
| Available in: Lightning Experience |
| 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. |
To make this app available to anyone with the permission to use it, select the Enable the Automation Lightning App process automation setting. To view connection version information, activate at least one connection.
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.
Create a Connection to an External System by Using a Standard Authentication Method
Create a connection to an external system by using the connector’s standard authentication method.
- Open the Automation app and select the Integrations tab.
-
Choose a method to create a connection.
- Select a third-party connector from the Get Started with Connectors section and then click Create Connection. If your connector isn’t available in the section, click View All Connectors, select a connector from the Browse Connectors window, and then click Next.
- Click New Connection, select an available third-party connector, and then click Next.
- In Authentication Protocol, select a standard authentication method.
-
Complete the connection information and authentication details for that connector.
ImportantIn the URL field, make sure that you enter the value in this format: http://<domain>. For example, https://thirdpartyconnector.com.
- Click Create.
Connect to an External System by Using Named Credentials
Select a named credential from Setup to use for your external system connections.
Prerequisites
Before connecting to your external system with a named credential, first create or use an existing authenticated named credential and external credential that is enabled for your users.
To ensure a successful connection for use in a flow, use only one principal for each named credential.
- Use the same name for the named credential and its related objects, such as the external credential and external authentication identity providers. Labels for these objects can differ.
- Assign the user creating the connection the required user permission for the principal. Without this permission, the connection test fails and the connection remains inactive.
When you create a connection with an existing named credential, note these behaviors:
- Manage the named credential’s read-only details in Setup, not the Integrations tab. On the Integrations tab, you can only edit the connection's Connection Name and Description.
- Perform reconnections for the named credential in Setup. The Reconnect button isn’t visible on the Details page.
- Delete associated named credentials in Setup. Deleting a connection doesn't remove the credential.
- Open the Automation app and select the Integrations tab.
-
Choose a method to create a connection.
- Select a third-party connector from the Get Started with Connectors section and then click Create Connection. If your connector isn’t available in the section, click View All Connectors, select a connector from the Browse Connectors window, and then click Next.
- Click New Connection, select an available third-party connector, and then click Next.
- In Authentication Protocol, select Named Credential, and then search for and select a named credential.
- Click Create.
Refresh an OAuth 2.0 Connection
If an expired refresh token interrupts a connection to an external system through OAuth 2.0 authentication, you can reconnect it.
- Select the connection to refresh.
- Click Reconnect.
- Complete the required steps to connect to the third-party system.
-
Save your work.
After refreshing the connection, the OAuth dance generates a new refresh token and reconnects the connection.
Edit a Connection
-
In the Automation app, on the Integrations tab, select the
connection to edit.
Flows that use the connection appear in the Flows Using Connection table on the Related tab. The table shows the name, version, status, and owner of each flow. To view a flow, click its name. For connection and authentication details, see the Details tab.
- Click Edit.
- Read the window, and click Edit.
- Edit the fields.
-
Save your work.
If errors appear after you save, the system doesn’t save your changes. Resolve the errors, and save again. A message indicates whether the connection test succeeded or failed. In the Integrations section, the Last Tested Date field and the Progress Status field in the Flows Using Connection table update to show your most recent test results.
Test a Connection
Opening or creating a flow that connects to an external system triggers a connection test and alerts you to any invalid connections. The system tests connections in these scenarios:
- When you create the connection
- When you select an existing connection to an external system to use as an action or a trigger
- When you reopen an existing flow containing a connection to an external system
You can also retest the connection manually.
- Select the connection that you want to test.
-
Click Test.
A message indicates the test result. In the Integrations section, in the Flows Using Connection table, the Last Tested Date and the Progress Status fields update with the latest test results.
Delete a Connection
-
Select the connection to delete.
Flows that use the connection appear in the Flows Using Connection table on the Related tab. The table shows the name, version, status, and owner of each flow. To view a flow, click its name. For connection and authentication details, see the Details tab.
- Click Delete.
-
Read the window, and click Close.
If your connection deletion is successful, a success message appears and you’re redirected to the Integrations tab. If the deletion fails, an error message appears.

