Documentation Index
Fetch the complete documentation index at: https://docs.tedro.io/llms.txt
Use this file to discover all available pages before exploring further.
Messenger Nodes
Messenger nodes handle communication with contacts through Facebook Messenger. Use them to send automated replies with buttons and escalate conversations to human agents. These nodes work exclusively with the Messenger channel.
Messenger supports text, buttons, and media with a 2,000 character limit. Unlike WhatsApp, Messenger does not support list menus or rich text formatting.
msg.send_message
Send a message via Facebook Messenger.
This node sends a text message back through Messenger. It supports dynamic variables from the workflow context for personalized responses.
Configuration
| Option | Type | Required | Description |
|---|
body | string | Yes | Message text. Supports context variables like {{contact.name}} and custom fields |
Variable Substitution
Use double curly braces to inject dynamic values:
Hi {{contact.name}}, thanks for messaging us on Facebook!
{{contact.name}} — The contact’s name{{contact.fields.*}} — Any custom fields set on the contact{{conversation.fields.*}} — Any custom fields set on the conversation
Outputs
| Output | Type | Description |
|---|
messageId | string | The Messenger message ID |
status | string | Delivery status (sent, delivered, read, failed) |
Connections
- Inputs: Single input handle from the previous node
- Outputs: Single output handle for chaining additional actions
Example Use Case
After an AI Agent handles a Messenger conversation, connect to a Messenger Send Message node to deliver the response. Messenger supports buttons, so you can include quick-reply options for common follow-up actions.
msg.handoff
Escalate the Messenger conversation to a human agent.
The Handoff node moves the Messenger conversation from automated processing to the human agent inbox. The conversation appears in the Inbox with a “handoff” status and a Messenger channel indicator (blue).
Configuration
| Option | Type | Required | Description |
|---|
reason | string | No | Optional note explaining why the handoff occurred (visible to agents in the inbox) |
Outputs
| Output | Type | Description |
|---|
handoff.status | string | Always handoff — the conversation is now in agent mode |
Connections
- Inputs: Single input handle from the previous node
- Outputs: Single output handle (typically connected to a
logic.end node or left unconnected)
Example Use Case
When a Facebook Messenger conversation needs human intervention — for example, order issues or account-specific questions — route to the Messenger Handoff node. The agent sees the conversation in their Inbox with the Messenger channel indicator.