Integrations Tab of the Automation App

Available in: Lightning Experience

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.

A connection is a configuration that uses a connector and associated user or system credentials to connect to an external system. Use connections at different steps in your flow to connect to systems, check for triggers, and return or manipulate data.

A connection enables you to connect to external systems. Connections configure access and fetch API or object metadata, such as input and output fields, from the connected external system. You can use and reference these fields in flows for your connection and automation needs. You can use the same connection multiple times in the same flow or in different flows that you create.

Creating a connection automatically generates the required named credentials and external credentials behind the scenes saving you from creating them in Setup.

Flow Builder uses various authentication types to create connections. The fields required to authenticate a connection are standard, but they can vary by external system. Some authentication types are:

ApiKey

ApiKey authentication connects to apps without explicitly defining a user. Add this key to all requests, and the cloud app identifies the origin of the request and completes the authorization.

Basic

Basic authentication enables the user to provide a username and password when logging in to an external system.

Bearer

Bearer authentication sends a header named Authorization with a value of Bearer and a token with every request.

OAuth2BrowserFlow

OAuth2BrowserFlow authentication includes features that extend OAuth 2.0 protocol functionality and security.

OAuth2ClientCredentials

OAuth2ClientCredentials authentication obtains an access token from a user-defined path.

Token-Based Authentication

Token-based authentication generates an encrypted access token to an external system. Connect Flow Builder to the external system with your unique, external system-generated Token ID and Token Secret fields.

Named Credential Authentication

Named credential authentication uses a pre-existing named credential with external credentials from Setup to connect to external systems.

For more information about the fields required to connect to a specific external system, see the associated MuleSoft for Flow: Integration Connectors Reference page.

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.

• Accelerate Integrations with Templates and AI Pre-Built Flows
  Use a MuleSoft for Flow: Integration template to configure connectors or use AI pre-built flows to build your flow logic. These tools eliminate starting from scratch, so you can accelerate integration and customize automation for your business.
• Integrations Limitations & Considerations
  When establishing connections to external systems, keep these limitations and considerations in mind.