Shared App Connections

in some circumstances it may be desirable to share a single app connection across multiple user accounts this can happen when lots of automations need to access the same app connection, where connecting dozens or hundreds of user accounts all to the same app with the same credentials is not practical or desirable the system performs the following logic to lookup a connection when an automation executes if the account running the automation has the connection, use it if the connection has "(shared from system setup)" in its name, it is supposed to be in the system's "setup" account if so use it, otherwise a connection not found runtime error occurs if the connection has "\[shared from parent]" in its name, it is supposed to be in the linked parent account if so use it, otherwise a connection not found runtime error occurs if the account is a child account, check the linked parent account if that account has the connection, use it check the system's "setup" account for the connection if that account has the connection, use it otherwise a connection not found runtime error occurs the system's connection sharing logic combines two approaches explicitly shared connections and inherited shared connections explicitly shared connections dedicated systems have a special "setup" account that can be used to create shared app connections in this account, create app connections as usual (see app connections docid\ oxu zjxq6hiljwyoetphf ) now other accounts in the system will see these connections listed when actions and triggers are edited in a similar manner, linked child accounts can use connections shared by their linked parent account the only difference is that when building the child automation, shared connections appear with "\[shared from parent]" in their names connections in the system setup account are shared by default connections in linked parent accounts must be explicitly shared in order to be made available to linked child accounts see sharing connections with linked child accounts docid\ qbk 8xw8tbqrtqkrzivwg the presence of either "(shared from system setup)" or "\[shared from parent]" in the connection name means that it is an explicitly shared connection if the connection is not found at runtime in either the setup or parent account, a connection not found runtime error occurs inherited shared connections if the connection name does not have either "(shared from system setup)" or "\[shared from parent]" in it, then if the account running the automation does not have the named connection the system will check to see if either the account's linked parent (if it is a child account) has the connection, or if the system's "setup" account has it the checks are done in that order (self, linked parent, system setup), which forms an inheritance the only requirement for a match is the connection name choosing a connection sharing approach when building general purpose automation templates (see automation templates docid\ df3wqj3uz1y0lgzb8crw2 ), it is generally best to rely on inherited shared connections this allows the templates to be deployed in either standalone accounts or in linked child accounts and still be able to utilize connections that may be shared from either the system's "setup" account or from a linked parent account explicitely shared connections are generally not useful for generalized automation templates a template built for a child account that is configured to use a "\[shared]" connection from its parent account will always fail to run in a standalone account that has no linked parent the delineation of explicit vs inherited connection sharing is provided because there are cases where automations or templates need to be built specifically for child accounts such that they will fail at runtime if the linked parent account doesn't have the shared connection available explicitly shared connections ensure the scope of the shared connection