You can have multiple accounts connected to each application or API. You can also rename your App Connect accounts for ease of identification, update the credentials for your accounts when necessary, and remove accounts that you no longer need.
The ability to connect to multiple accounts enables you to create flows that use different accounts to connect to different instances of an application; for example test and production instances, or instances in two different sites or geographies. So, for example, you might create a flow that pushes data from a test to a production instance, or that synchronizes data across two instances in different locations. Or, if youâ€™ve configured more than one set of user credentials or generated more than one API key for an API (for example, to accommodate different rate limits or access levels), you can create an account for each set of credentials or API key.
You can manage accounts for an application or API as follows:
- Add another account: From the Applications or APIs tab on the Catalog page or from the flow editor, click the drop-down arrow for accounts and click Add a new account.
Then, specify a new set of account details for the application or API. The new account is added to the drop-down list.
- Choose which account to use: If you are connected to multiple accounts, you can, while within the flow editor, indicate which application instance to trigger an event from, and which application or API instance an action is applied to. You can select the account while adding the event or action.
You can also switch to a different account after adding the event or action. To do so, select the application or API node and then select the required account from the drop-down list.
Tip: If you are using multiple accounts for an application, the set of fields that are displayed when you select an action for that app might vary based on the selected account. In the flow editor, some applications always provide a curated set of static fields for an action, whereas others use dynamic discovery to retrieve the set of fields that are configured on the instance you’re connected to. For example, if you have two accounts for two separate instances of an app, the first account might use the out-of-the-box settings for the app, whereas the second account might have additional custom fields configured.
- Update the connection details of an account: The update option provides a way for you to re-authorize your connection if your access to an application or API has expired or been revoked, or if your credentials have changed for the API or source application that you are connected to. You’ll also find this option useful if you want to use different credentials for an account that is used in one or more of your existing flows.
To update an account for an app or API, go to the Applications or APIs tab on the Catalog page, and select the relevant account from the Account drop-down list for that app or API. Then, open the options menu (⋮) for the account and click the Update Account option to specify different connection details.
Note: You cannot update the account for an application if that account is being used in a running flow; to update an account, you must stop all flows that are using that account. With an API account, you don’t need to stop running flows before updating the account.
- Remove an account: From the Applications or APIs tab on the Catalog page, open the options menu (⋮) for the relevant account and then click the Remove Account option to delete the connection to that account. Before you remove an account, delete all the flows that use that account, or edit the flows to either remove the nodes using that account or to switch to a different account.
- Update the account name: From the Applications or APIs tab on the Catalog page, open the options menu (⋮) for the relevant account and then click the Rename Account option to specify a different account name. Account names must be unique for an app or API.
Note: You cannot rename the account for an application if that account is currently being used in a flow; so it’s best to rename accounts before you use them in a flow. You can rename the account for an API regardless of whether the account is used in a flow.