Skip to main content
A Channel gambit sends a WhatsApp template message from a connected account. It is how a flow reaches someone rather than replying to them.

When to use it

Pair it with a Trigger gambit: the trigger starts the flow from your system’s event, and the Channel gambit delivers the first message. Use it mid-flow to message the end user, or another number, on WhatsApp. For sending to many end users at once, use a campaign rather than a flow.

The gambit and its editor

Every page in this section shows the same demo flow: Start, a Welcome message, the gambit this page covers, then End. The gambit sits third, selected, with its editor open on the right. The rest of the screen is dimmed.

Configuration

The editor opens with a Workflow Mode switch, described as executing a specific action as a workflow step. It is on by default, and the settings below belong to that mode. When the chosen template carries placeholders, a Template Parameters editor lists one field per placeholder. Each field takes fixed text or a captured value, inserted by typing @. Which templates exist, and when one is required, are covered in WhatsApp templates.

Agent tool mode

Turning Workflow Mode off switches the gambit to agent tool mode. The gambit then becomes a tool an AI Agent gambit can call, rather than a step the flow walks through. The editor swaps the wait and retry settings for Tool name and Description. Once the template has placeholders, Agent-fillable parameters lists them. Checked parameters are filled by the AI agent at run time, and unchecked ones keep the value you set here.

Branching on delivery

The handles depend on Wait for reply.
A send that still fails after the retries routes to Failure. Wire that handle rather than leaving it open, or a failed send strands the conversation.

Before you can use it

The gambit needs a connected WhatsApp account. Connecting one is covered in Connect WhatsApp.