Sender Nodes
When Priya sends your business a WhatsApp message and your agent replies, something has to carry that reply back to her phone. That's what a sender node does.
There are five, listed under Actions › Messaging in the node picker: Email Sender, SMS Sender, WhatsApp Sender, Chat Sender (Telegram, Slack, Messenger, Instagram, Microsoft Teams, Discord, Google Chat and RCS) and Phone Caller. They're the only way an agent reaches someone on those channels.
Prerequisites: Trigger Nodes and AI Agent Node.
One node, two ways to wire it
The same sender node can sit in two places, and its settings are the same in both. (The Chat Sender is the exception: it only works on the Action port — see Chat Sender.)
| Wiring | Behaviour | Use it for |
|---|---|---|
| On the AI Agent's Action port | The agent can send whenever it decides to during the conversation, including its replies. | An agent that chats back and forth on WhatsApp, SMS or email. |
| On the canvas as a flow step (click + after a node) | It sends once, when the run reaches it. | A message at a fixed point: after a Condition, at the end of a scheduled or webhook flow. |
As a flow step with Message content set to Let the AI write it, the node sends the reply the AI Agent produced earlier in the run. It goes to the person in the conversation, or to the fixed number or address you set.
With Use a template or fixed text, a flow step fills the {{ variables }} in the body, subject and opening line itself from the run's data — a post-call Summary: {{call_summary}} message works this way — and a variable with no value is left empty rather than sent as braces.
If the recipient is a {{ variable }} that has no value in this run, nothing is sent: the step fails with a message naming the variable, so you can fix the step that should have set it.
Options

The Email, SMS and WhatsApp Senders and the Phone Caller share the same shape — Tool Name, Instruction, a "send from"/"send to" pair, and a message-content switch — but each names and fills in its own message fields.
Send to (Call on Phone Caller) starts on The person in this conversation, and a sender saved without a choice sends there too. To always reach someone else — a team inbox, a manager — pick A fixed address or A fixed number.
Email Sender
| Field | What it does | Options | Default | Shown when |
|---|---|---|---|---|
| Tool Name | How the AI refers to this tool. Blank → derived from the node label. | |||
| Instruction | Tell the AI WHEN to call this tool, WHAT inputs/payload to pass, and WHAT it returns — so it can decide whether and how to use the action. Blank → a generic default for the action. | |||
| Send from | Required — the business email address this is sent from. Pick one in Credentials if the list is empty. | |||
| Send to | Who receives this. Default: the person in this conversation — to always send elsewhere (a team inbox, a manager), pick a fixed address. |
What to send
| Field | What it does | Options | Default | Shown when |
|---|---|---|---|---|
| Message content | Default: the AI writes the message from context + your guidelines. Choose "Use a template" to provide fixed/templated content. | Let the AI write it · Use a template or fixed text | ai_decides | |
| Load saved template | Fill the fields below from a saved Message Template. You can still edit them after. | Message content is Use a template or fixed text | ||
| Subject | Use {{placeholders}}; empty → the AI writes the subject. | Message content is Use a template or fixed text | ||
| Body | {{placeholders}} are filled at send time. Empty → the AI writes the body from the guidelines. | Message content is Use a template or fixed text | ||
| Guidelines for the AI (optional) | Soft guidance the AI follows when it writes the message. Leave the content empty above to let the AI compose from these. | |||
| Attach a file the AI generated earlier |
SMS Sender
| Field | What it does | Options | Default | Shown when |
|---|---|---|---|---|
| Tool Name | How the AI refers to this tool. Blank → derived from the node label. | |||
| Instruction | Tell the AI WHEN to call this tool, WHAT inputs/payload to pass, and WHAT it returns — so it can decide whether and how to use the action. Blank → a generic default for the action. | |||
| Send from | Required — the business number this is sent from. Pick one in Credentials if the list is empty. | |||
| Send to | Who receives this. Default: the person in this conversation — to always send elsewhere (a team number, a manager), pick a fixed number. |
What to send
| Field | What it does | Options | Default | Shown when |
|---|---|---|---|---|
| Message content | Default: the AI writes the message from context + your guidelines. Choose "Use a template" to provide fixed/templated content. | Let the AI write it · Use a template or fixed text | ai_decides | |
| Load saved template | Fill the fields below from a saved Message Template. You can still edit them after. | Message content is Use a template or fixed text | ||
| Message | Use {{placeholders}}; empty → the AI writes it from the guidelines. Keep it short. | Message content is Use a template or fixed text | ||
| Guidelines for the AI (optional) | Soft guidance the AI follows when it writes the message. Leave the content empty above to let the AI compose from these. |
WhatsApp Sender
| Field | What it does | Options | Default | Shown when |
|---|---|---|---|---|
| Tool Name | How the AI refers to this tool. Blank → derived from the node label. | |||
| Instruction | Tell the AI WHEN to call this tool, WHAT inputs/payload to pass, and WHAT it returns — so it can decide whether and how to use the action. Blank → a generic default for the action. | |||
| Send from | Required — the business number this is sent from. Pick one in Credentials if the list is empty. | |||
| Send to | Who receives this. Default: the person in this conversation — to always send elsewhere (a team number, a manager), pick a fixed number. |
What to send
| Field | What it does | Options | Default | Shown when |
|---|---|---|---|---|
| Message content | Default: the AI writes the message from context + your guidelines. Choose "Use a template" to provide fixed/templated content. | Let the AI write it · Use a template or fixed text | ai_decides | |
| Load saved template | Fill the fields below from a saved Message Template. You can still edit them after. | Message content is Use a template or fixed text | ||
| Message | Use {{placeholders}}; empty → the AI writes it from the guidelines. Outside the 24-hour window WhatsApp requires an approved template. | Message content is Use a template or fixed text | ||
| Guidelines for the AI (optional) | Soft guidance the AI follows when it writes the message. Leave the content empty above to let the AI compose from these. |
Phone Caller
| Field | What it does | Options | Default | Shown when |
|---|---|---|---|---|
| Tool Name | How the AI refers to this tool. Blank → derived from the node label. | |||
| Instruction | Tell the AI WHEN to call this tool, WHAT inputs/payload to pass, and WHAT it returns — so it can decide whether and how to use the action. Blank → a generic default for the action. | |||
| Call from | Required — the business number this call shows as caller-ID. Pick one in Credentials if the list is empty. | |||
| Call | Who is called. Default: the person in this conversation — to always call someone else, pick a fixed number. |
What to do on the call
| Field | What it does | Options | Default | Shown when |
|---|---|---|---|---|
| Call objective | Default: the AI decides what to accomplish on the call from the conversation. Choose "I'll specify" to script it. | Let the AI decide the objective · I'll specify the objective | ai_decides | |
| Call objective | What the AI should accomplish on the call — this guides the live conversation. | Call objective is I'll specify the objective | ||
| Opening line (optional) | The first thing the AI says when the call connects. | Call objective is I'll specify the objective |
Chat Sender
| Field | What it does | Options | Default | Shown when |
|---|---|---|---|---|
| Tool Name | How the AI refers to this tool. Blank → derived from the node label. | |||
| Instruction | Tell the AI WHEN to call this tool, WHAT inputs/payload to pass, and WHAT it returns — so it can decide whether and how to use the action. Blank → a generic default for the action. | |||
| Messaging app | The app this agent replies on. The reply goes to the chat the customer wrote from, through the bot they wrote to. | Telegram · Slack · Messenger · Instagram · Microsoft Teams · Discord · Google Chat · RCS | telegram |
What to send
| Field | What it does | Options | Default | Shown when |
|---|---|---|---|---|
| Guidelines for the AI (optional) | Soft guidance the AI follows when it writes the message. Leave the content empty above to let the AI compose from these. |
The Chat Sender has no Send from or Send to: the reply goes to the chat the customer wrote from, through the bot they wrote to. Pick the app under Messaging app (default Telegram). One Chat Sender covers only the app it names — an agent that answers on Telegram and Slack needs one for each. It must be wired to the AI Agent's Action port; placed as a flow step it would never send, so Activate refuses it there. The trigger side is on Trigger Nodes; connecting each app is on Messaging Apps.
All message/body/text fields accept {{ variables }}. Email Sender has Attach a file the AI generated earlier for sending a PDF or spreadsheet the agent created in the same conversation.
"Send from" is mandatory on purpose
Choosing the sender explicitly means a scheduled or webhook-triggered send goes out from exactly the same number or address as a reply would.
There is no default sender
Every message leaves from the node's own Send from, through the connected account that owns it:
| Sender | "Send from" must be… |
|---|---|
| SMS Sender, Phone Caller | a number one of your connected Plivo accounts lists |
| WhatsApp Sender | a number one of your WhatsApp connections owns |
| Email Sender | an address one of your connected email accounts sends from (for AWS SES, any address or domain you verified there) |
A send from anything else is refused — nothing goes out from some other account instead. The refusal is logged and you get an in-app notification naming the channel, the sender and the fix (at most once a day for the same problem).
Before you activate, the builder warns you (amber, never a block) when:
- a Send from isn't owned by any connected account — every send from it will be refused;
- Send to is A fixed … but nothing is filled in;
- the Instruction names an email address or phone number but Send to isn't fixed to it — the warning says where the message will really go and how to fix it.
When a send is refused
A refused or failed send is reported back, not hidden. On the Action port, the agent is told "The email was not sent: <reason>. Do not retry; tell the person it could not be sent right now." — so it can tell the customer — and the call shows as failed in the run. As a flow step, the sender reports that it didn't send, its reason shows as the step's error (the run reads Completed with errors), and the steps after it still run.
Each sender covers its own channel only
A WhatsApp Sender lets the workflow send on WhatsApp. It says nothing about SMS or email — and a Chat Sender set to Telegram says nothing about Slack.
If an agent is triggered on WhatsApp, SMS, email or a messaging app and there's no matching sender on its Action port, the conversation still runs, but the agent's replies aren't sent. The AI Agent node shows a warning before you activate, for example The WhatsApp trigger will start this agent, but there is no WhatsApp Sender…. That's deliberate: a workflow that was never given a way to send shouldn't invent one.
Web and voice need no sender
On Web Chat and voice, the reply comes back through the widget or over the live call. There's no sender node to add.
How replies fit the inbound path
Every non-voice channel flows through one inbound path: the message is de-duplicated, the customer is identified, and the message is matched to a workflow.
De-duplication matters more than it sounds. Messaging providers re-deliver: a forwarded mailbox re-sends, a webhook is retried, a provider posts the same event twice. Because the check happens before anything else, the same message never produces two AI replies.
Worked example
Setup: Asha builds a support workflow for Acme Support: a WhatsApp trigger and an AI Agent, with a WhatsApp Sender on the agent's Action port. She sets Send from to Acme's connected WhatsApp number and Send to to The person in this conversation.
Action: Priya sends "What are your store hours?" to that number. The trigger fires, the agent drafts a reply, and the sender delivers it.
Result: Priya gets the reply on WhatsApp, from the number she messaged.
What just happened: Perfox matched the inbound number to Acme's workflow and sent the reply from the number Asha chose on the node. Had she left Send from empty, Activate would have told her so instead of letting it fail in front of a customer — and had she picked a number no connected account owns, the builder would have warned her that every send from it would be refused.
Next steps
- Trigger Nodes: the inbound side of a channel.
- Messaging Actions: more on the senders as agent actions.
- Channels Overview: connect an account so a sender has something to send from.