Workflows are directed graphs where nodes execute sequentially. Each node performs a specific action—sending messages, waiting for input, routing logic, or executing code.Documentation Index
Fetch the complete documentation index at: https://docs.kapso.ai/llms.txt
Use this file to discover all available pages before exploring further.
Node categories
Start node - Entry point- Triggers when a message arrives or API calls the workflow
- Every workflow has exactly one Start node
- Automatically advances to the first connected node
- Send messages (text, templates, interactive)
- Execute functions
- Call webhooks and connected app actions
- Set workflow variables
- Call other workflows
- Transfer to human agents (handoff)
- Execute immediately and advance to next node
- Halt workflow execution until user responds
- Store response in
{{last_user_input}}or custom variable - Resume execution when message arrives
- Branch workflow to different paths
- Use AI to interpret intent or custom function logic
- Return label determines which edge to follow
- Multi-turn conversations with tool access
- Can call webhooks, functions, and app integrations
- Maintains execution at node until
complete_tasktool is called - New user messages automatically injected during conversation
Execution flow
Workflows follow edges between nodes. Execution continues until:- Reaching a Wait node (pauses for user input)
- Reaching an Agent node (remains at node until agent calls
complete_task) - Reaching a Handoff node (stops, transfers to human)
- No more connected nodes (workflow completes)
Learn more
Step types
Action nodes, wait nodes, decide nodes, and agent nodes
Variables and context
Access user data and workflow state with template variables
Triggers
Start workflows from messages or API calls
Webhooks
Connect workflows to external services

