Overview
Runtime Connection Switching allows a single automation to execute against different external service connections depending on which connection is specified when the automation is called. Instead of building one automation per connection, you build one automation and route each invocation to the appropriate connection at runtime.
A common use case is a multi-tenant integration: an inventory sync automation that must operate against 50 different Shopify stores, each with its own credentials, can be written once and called 50 times — each time passing a different store's connection ID — rather than duplicating the automation for every store.
Runtime connection switching configuration panel
Requirements
Runtime Connection Switching is only available on automations with a Callable trigger type. The feature cannot be enabled on automations triggered by scheduled, webhook, or event-based triggers.
Setup
Set a Callable trigger — Open the automation and configure the trigger as Callable. This makes the automation invocable by other automations or via the Call Another Automation node.Callable trigger selection on the automation trigger panel
Choose a default connection — In the automation's connection configuration, select the connection to use when no runtime override is provided. This acts as the fallback for any invocation that does not specify an override.
Enable Runtime user connections — Toggle on the "Runtime user connections" option in the automation's advanced settings. This activates the connection override capability for the automation.
Configure Connection overrides — Define the mapping between override identifiers and their target connections. Each override entry maps a runtime-provided connection ID to the specific connector configuration to use.Connection overrides configuration interface
Retrieving Connection IDs
To pass the correct connection ID at runtime, use the Standard Entities — Get Connection Details action in a parent automation to look up the connection ID for a given store, tenant, or account. The returned connection ID can then be passed as the override value when calling the child automation.
This pattern enables fully data-driven connection routing: store connection identifiers in a database or configuration record, retrieve them dynamically, and pass them to the automation — with no hardcoded connection references in the workflow logic.
Example: Multi-Store Inventory Sync
An e-commerce company manages inventory across 50 Shopify stores. The process:
A parent automation retrieves the list of all stores and their connection IDs from a Standard Entities record.
A Loop node iterates over the store list.
On each iteration, Call Another Automation invokes the inventory sync automation, passing the current store's connection ID as the runtime override.
The inventory sync automation executes against the specified store's Shopify connection, syncing stock levels and pricing.
Note: The automation must have a Callable trigger for runtime connection switching to work. Attempting to enable it on other trigger types will have no effect.