Skip to content
Zapito Docs

Node reference overview

Every node on the canvas is documented here: what it does, its config fields, and exactly how the runtime treats it.

Anatomy of a node

Section titled “Anatomy of a node”
  • Input port (left) — receives the conversation from the previous node.
  • Output ports (right) — where the conversation goes next. Most nodes have one; Confidence Check has two labeled branches.
  • Resource port (bottom of the AI Agent) — accepts dashed wires from Knowledge Base and Custom Tool nodes.

A turn starts at the trigger matching the channel the message came from, then follows wires node by node (up to 20 steps) until there’s nothing left to run.

Status labels

Section titled “Status labels”

Zapito’s canvas ships slightly ahead of its runtime, and these docs tell you exactly where the line is:

  • Live — the node (or field) does what it says in production today.
  • Config-only — the field is saved with your flow but the runtime doesn’t act on it yet; it will light up without you rebuilding anything.
  • Coming soon — the node can be placed and configured, but its channel or action isn’t wired to the engine yet.

The nodes

Section titled “The nodes”
NodeRoleStatus
WhatsApp TriggerStarts the flow on WhatsApp messagesLive (sandbox)
Telegram TriggerStarts the flow on Telegram messagesLive
Web Widget TriggerStarts the flow from the site chat bubbleLive
Instagram TriggerStarts the flow on Instagram DMsComing soon
Messenger TriggerStarts the flow on Facebook Page messagesComing soon
SMS / RCS TriggerStarts the flow on inbound SMSComing soon
AI AgentReads the message and writes the replyLive
Knowledge BaseReal content the agent answers from — pages, text, PDFsLive
Custom ToolCalls your API, response goes to the agentLive
Confidence CheckBranches on the agent’s confidenceLive
Send ReplyDelivers the agent’s answerLive
Human HandoffEscalates to a teammateLive
Log to CRMCreates a ticket from the transcriptComing soon
WaitPauses the flow a few secondsLive