---
sourceDocument: Brazil Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Supporting multiple connections

# Supporting multiple connections {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 minutes to read  
Support several connections to a single integration provider. Select connections for flows, subflows, and actions directly from a flow.

## Benefits {#support-multiple-connections__section_eyf_smh_plb}

Multiple connections support offers these benefits.

* Have more than one connection to the same integration provider. For example, you can establish connections to several different Jira environments.
* Select which connection you want to use in a flow. Override preset connections for flows, subflows, and actions directly through Workflow Studio.{#support-multiple-connections__flow-designer}
* When a flow is promoted to production, reestablish a connection to each account without needing to modify the flow.
{#support-multiple-connections__ul_mxc_xmh_plb}

To learn more about connections, see [Connections and
Credentials](https://www.servicenow.com/docs/access?context=r-credentials&version=brazil&pubname=brazil-platform-security&ft:locale=en-US).

## Connection and credential aliases {#support-multiple-connections__section_u3x_vfk_nlb}

Integration Hub uses aliases to manage connection information and credentials when integrating with external systems. Using an alias eliminates the need to configure multiple credentials and connection
information profiles when using multiple environments. Integration Hub only requires an alias, which then resolves to use the correct credentials and connection information during runtime.

With connection and credential aliases, you can also create additional aliases or connections called child aliases. Child aliases enable you to create multiple connections within the same application integration.
For more information, see [Create a Connection and Credential alias](https://www.servicenow.com/docs/access?context=connection-alias&version=brazil&pubname=brazil-platform-security&ft:locale=en-US).

## Flow-level connection selection {#support-multiple-connections__section_mv3_c5p_nlb}

You can choose a connection for a flow or subflow directly from the flow's main page. When you select a new connection, it overrides any preconfigured connection for that flow. To choose a connection, select the More Actions menu icon (![More Actions icon]()), and select the Configure connections option. This option opens the Configure Connections window, where you can select the connections for your flow. The Configure Connections window displays:

* All the aliases used in the flow.
* The icon and name for each alias.
* A list of the configured connections for each alias. The default connection is listed first. Other connections are listed alphabetically.
* An information icon for each alias. Selecting the icon opens the Connection \& Credential Aliases record for the default connection shown in the list.
* A Manage Connections option that opens the connections dashboard.
* Options to Cancel connection selection or Update your connection choice.
{#support-multiple-connections__ul_zk1_hvp_nlb}

Each alias has one entry in the Configure Connections window, regardless of how many
actions or subflows may use that alias. When you select a connection at the flow level, the
new connection applies to all the actions and subflows using that alias. For example, if a
flow has several actions that use a Slack service, changing the connection for the Slack
service changes the connection for all the Slack service actions within the flow.

You can see which parts of a flow a connection change affects by matching the alias icons
in the flow to the ones in the Configure Connections window. An action that impacts a Slack
service has a Slack icon next to the action in the flow. The Slack icon also appears next to
the alias name in the Configure Connections window.

The Configure Connections window is automatically updated whenever you add or delete a flow
component that has connections. When you add an action or subflow to a flow, the Configure
Connections window displays the connections for the action or subflow that you just added.
If you remove an action or subflow, the connection information is removed from the Configure
Connections window.

You can choose whether to display the Configure connections option
with the sn_flow_designer.connections_override_enabled system property.
Setting the property to true displays the Configure connections option, while setting it to false hides it.
If you delete the system property or it doesn't exist, the Configure connections option is displayed by default.

View which connection your flow ran with by examining the Step Configuration section of the
flow's execution details. The connection alias listed in the CONFIGURATION column is the
alias that the flow was originally designed to run with. The alias listed in the RUNTIME
VALUE column is the one that the flow actually ran with.  
Figure 1. Execution details page

## Action-level connection selection {#support-multiple-connections__section_unq_xfk_nlb}

You can select connections for individual integration actions within a flow. This functionality is useful if a flow must interact with multiple configurations of the same provider. For example, downloading a file from one
configuration of a file storage provider then uploading the file to a different configuration of the same file storage provider.

Integration actions have one or more connection fields in the Action Properties section where you can edit or configure a connection. If the connection alias is using a configuration template with a test action, you can also
test the connection from here. For details, see [Create a test action to test a connection alias from a configuration template](https://www.servicenow.com/docs/HjPW1VRVEgzXvj~kPId_hw "For connection aliases using a configuration template, you can create a test action that enables you to test the connection directly from the Action Properties section of actions contained in a flow in Workflow Studio.").

In the following example, the Create Remote Incident action has a connection field called ServiceNow Connection. The default connection hasn't been configured yet, so a Connection not configured message appears below the connection field. This message appears whenever the connection for the selected alias is not configured  
Figure 2. Example of a connection field in an integration action  
Use the gear icon (![gear icon]()) to create or configure an alias.

* For connections using a [configuration template](https://www.servicenow.com/docs/access?context=spoke-configuration-template&version=brazil&pubname=brazil-platform-security&ft:locale=en-US), the gear icon opens a window where you can create or configure a connection.
* For connections without a configuration template, the gear icon opens the platform form for [creating a connection and credential alias.](https://www.servicenow.com/docs/access?context=connection-alias&version=brazil&pubname=brazil-platform-security&ft:locale=en-US)
{#support-multiple-connections__ul_dzb_gls_rdc}

Use the plus icon () to add a new child connection alias.

The pencil icon (, not shown in the image) opens the Edit Connection window where you can edit the selected connection. If the connection is using a configuration template with a test action, you can test the connection by using the
Save and Test button.

## Dynamic inputs {#support-multiple-connections__section_yzd_mwp_nlb}

You can select connections for flows and subflows containing actions with dynamic inputs. When
a connection override is specified at the flow level, the dynamic action uses the flow-level
override. For example, in a flow with a data-gathering action, the action uses the flow's
override connection for the data-gathering step rather than the action's default connection. If
an override is specified at the action level, the dynamic action uses the action-level
override.

## Multiple overrides within a flow {#support-multiple-connections__section_qtp_zdk_nlb}

When there is more than one override in a flow, they're applied according to the following rules:

* Action-level overrides always apply.
* Subflow-level overrides always apply to the subflow. The override also applies to actions within the subflow that don't have their own overrides configured.
* Flow-level overrides apply to subflows and actions that don't have their own overrides configured.
{#support-multiple-connections__ul_eph_n2k_nlb}

## Flow promotion {#support-multiple-connections__section_ln5_lbj_plb}

When you move a flow to a production instance, the alias information is transferred with it,
but the underlying connection information is not. An alias functions as a type of container for
connections. The container moves with the flow, but the specific connection information doesn't.
Any connections associated with the alias become unconfigured and must be reconfigured before
you can use them in the new environment.  
You can configure connections without having to modify the flow because you already have the base alias set up. To configure a connection:

* If the alias has a configuration template, configure the connection through the Connections dashboard. See [Configure a connection in the Connections dashboard](https://www.servicenow.com/docs/pKkkusMX54q_lKWpGfV7Ug "Configure a connection through the Connections dashboard.") for instructions.
* If an alias doesn't have a configuration template, configure it through the platform user interface. For more information about configuring a connection without a template, see [Getting started with connections](https://www.servicenow.com/docs/access?context=connection-information&version=brazil&pubname=brazil-platform-security&ft:locale=en-US).
{#support-multiple-connections__ul_ezt_pcq_plb}