Channel Relay

The Channel Relay node sends the customer an email with a link to a web flow on the customer portal, then ends the current flow. When the customer clicks the link, the target web flow opens in their browser, with the original conversation's borrower identity and variables already in place (if already attained).

Some processes need more than email can offer. Filling out forms, uploading documents, verifying identity -- these require a browser. Channel Relay bridges that gap by moving the customer from email to a web flow without losing context. Note this node is exclusive to email flows.

Prerequisites

The flow must be an email flow with a configured email connector. The target web flow must already exist -- the dropdown only lists non-email flows, preventing circular relays.

Variables referenced in the email body should be set by earlier nodes. The recipient and subject line are determined automatically from the email conversation.

Configuration

You configure two things: where to send the customer, and what the email says

Target flow. Select the destination web flow from the dropdown. Only non-email flows appear. This is the flow that opens when the customer clicks the link.

Email body. Write the message the customer will receive. The editor supports variable insertion, an emoji picker, and AI assist -- just like the Message node. The key piece is {{web_flow_url}}: a special placeholder the system replaces with the actual link to the target web flow. Your body must include it, and the editor warns you if it is missing.

When you first place the node, the body contains only {{web_flow_url}}. Add context around it so the customer knows what the link is for:

Hello -- please continue your application by clicking the link below:

{{web_flow_url}}

This link will take you to a secure page where you can complete the remaining steps.

The subject line and recipient are not configurable. The node replies to the existing email thread, preserving the "Re:" prefix, and the recipient defaults to the address that started the conversation.

When to Use It

Email-to-web handoff. A customer sends an email to start a process, but completing it requires interactive steps -- form submissions, document uploads, identity verification. The Channel Relay sends them a link to pick up where the email left off, in a web flow that already knows who they are.

Cross-channel onboarding. An inbound email triggers a flow that identifies the customer and gathers initial context. The relay then directs them to a full web-based onboarding flow, carrying their borrower identity and any variables collected so far.

Output Handles

The Channel Relay node has no output handles. It ends the flow after sending the email -- there is no success path, no error path, and no way to continue within the same flow. The customer's next interaction happens entirely in the target web flow.

This makes it a natural endpoint. Place it at the end of an email flow branch, not in the middle.

Things to Keep in Mind

Context is copied, not linked. When the customer opens the web flow, their borrower identity and conversation variables are copied into the new conversation. Changes made in the web flow do not propagate back to the original email conversation -- the two are independent from that point on. If the original conversation no longer exists when the customer clicks the link, the web flow still starts, but without borrower identity or variables.

Avoid naming your own variables web_flow_url. The auto-generated link overwrites any existing variable with that name.