Automate every conversation

Build WhatsApp automations on a visual canvas or in code, and hand off to a person when it matters.

AI at any step, on the model you pick

  • Choose the model for each node, from Anthropic, OpenAI, or OpenRouter. Runs use your project's AI credits.
  • Agent node: holds the conversation, calls your functions, webhooks, and MCP servers, and moves on when the task is done.
  • AI decide: reads the conversation and picks the branch that matches what the customer wants.
  • AI fields: write any message or value as a prompt, filled in at runtime with your variables.
  • Agents can work with function tools, webhook tools, streamable HTTP MCP servers, 2,700+ apps, a remote sandbox (beta) with GitHub repositories, rich WhatsApp replies, and built-in tools.

Add a step, connect it, done

  • Pick from 13 steps, drop them on the canvas, and connect them: Start, Send Text, Send Template, Send Interactive, Wait for Response, Decision, Webhook, App, AI Agent, Custom Function, Emit Event, Handoff, and Call Workflow.

Canvas or code. Same workflow.

  • @kapso/workflows: write workflows in JavaScript or TypeScript instead of dragging nodes.
  • Kapso CLI: pull workflows and functions into a repo, review changes in Git, and push them back.

Test before it talks to anyone

  • Chat like a customer: send mock messages and see exactly what the workflow replies.
  • See every step: flow events show which steps ran, in order, and which way each branch went.
  • Know what AI costs: see tokens and spend for every agent and AI decision in the run.

Start from anywhere

  • Inbound message: a customer messages one of your WhatsApp numbers.
  • API call: your backend starts a run with variables and context.
  • WhatsApp event: message and conversation events, like a failed send or an ended conversation.
  • Project event: custom events from your backend, your agents, or other workflows.

Frequently asked questions

What is a Kapso workflow?

A directed graph of nodes that run in order: send a message, wait for a reply, branch, run code, or hand off to a human. Workflows start from a trigger, most often an inbound WhatsApp message.

Can I build workflows in code?

Yes. The Kapso CLI pulls workflows into a local repo, where you edit them as JSON or in JavaScript or TypeScript with @kapso/workflows, then push them back. The canvas and code edit the same workflow.

How do I start a workflow from my app?

Give the workflow an API trigger and activate it, then call POST /platform/v1/workflows/{workflow_id}/executions with a phone number and optional variables. It returns 202 with an execution id and a tracking_id.

What happens when a workflow hands off?

The run stops and its status changes to handoff, so no more automated messages go out. A person on your team takes the conversation from there.