Overriding a message's recipient connection

By default, a Slack step delivers to the channel data stored on the recipient. A recipient connection override lets a single message template deliver somewhere else — a fixed channel, a specific user, or an incoming webhook — regardless of the recipient's stored connections.

This is useful when a message should go somewhere other than the recipient's configured destination: an alerts channel, an internal operations channel, or a dynamic destination you compute per-recipient with Liquid.

In the workflow builder, open the Slack step's template, then open Template settings (the gear icon) and set the Recipient connection field.

The override is stored on the message template, so it travels with the workflow when you commit and promote it across environments.

The override replaces the recipient's connections for this message: exactly one message is delivered, to the connection you specify. If the value is empty or renders to invalid JSON at send time, the message is left undelivered with failure details you can inspect on the message.

The override is a JSON object in one of two shapes.

Post to one fixed Slack incoming webhook URL:

Send to a channel (channel_id) or a user's direct message (user_id), authenticated with a bot token:

You can leave out access_token and let it come from the access token stored on the tenant you trigger the workflow with. In that case, provide only the destination:

The value is Liquid-capable and rendered at send time, so you can route each message dynamically from workflow or recipient data: