FlowsBeta
Flows
Design structured, multi-step chat conversations on a visual canvas, with tools, HTTP calls and handoffs as nodes.
When to use a flow
Most chat agents need only a prompt and tools. Use a flow when a conversation must follow a defined path, for example an intake form, a qualification script, or a support triage tree where each branch calls a different system.
| Use a prompt-only agent when | Use a flow when |
|---|---|
| The conversation is open-ended | The steps and their order matter |
| One set of rules covers every case | Different answers lead to different paths |
| Tools are optional helpers | Specific steps must call specific systems |
How flows work
- You build the flow on a canvas from nodes and connections. Start from one of the templates or a blank canvas.
- Every edit is saved as a draft version. Publishing creates an immutable version.
- A chat agent is switched to Flow mode and pointed at a published flow. Deploying the agent compiles the flow and runs it on the flow engine.
- Tool and handoff nodes run through a signed bridge scoped to the session, the run and the node, so a flow can't call a tool it wasn't given.
- HTTP nodes call public HTTPS URLs only. Internal and private addresses are refused.
Note
Flows are in Beta and are enabled per workspace. Flows power chat agents today; voice support will follow. Ask support@katexs.com to enable flows for your workspace.
Build and publish a flowStep by step from template to live agent.Chat agentsThe agents flows run inside.
Last updated November 2026 · Found a problem? Email support@katexs.com
