Visual Workflow Designer
Two designers on one canvas: workflows automate the back office, and playbooks design the conversation your customer actually has. Triggers, conditions, branching and live-agent handoff, without writing a single line of code.
Example: Smart Agent Assignment
Automatically route WhatsApp messages to the right sales agent
Industry Use Cases
Automated workflows tailored for your business
Appointment Reminders
Automatically send appointment confirmations 24h before, with option to reschedule via WhatsApp.
Abandoned Cart Recovery
Detect abandoned carts and send personalized WhatsApp messages with discount codes.
Guest Experience
Welcome guests via WhatsApp with check-in details, room preferences, and concierge support.
Tour Updates
Send real-time updates about tour times, meeting points, and weather alerts to all participants.
Smart Routing
Route incoming messages to available agents based on skills, workload, and customer history.
Payment Reminders
Automatic payment reminders 3 days before due date with instant payment link via WhatsApp.
Every node, configured visually
Purpose-built editors for each step — no scripting, no JSON.
Triggers
Start on a new message or event — or run a flow on demand.
Conditions
Continue only when your rules match a contact, tag or variable.
Branch & switch
Route down multiple labelled paths from a single decision node.
Actions
Create contacts, assign agents, add tags and send messages.
Manual input
Collect structured input fields when a human starts a run.
Webhooks & REST API
Trigger from any tool and call your own stack via our open API.
Four ways a workflow starts
A workflow does not have to wait for somebody to send a message.
On an event
Something happens in the platform — a message arrives, a conversation changes, a contact is updated — and the flow runs.
On a schedule
A cron schedule in the time zone you actually work in, for the nightly job and the Monday-morning one.
Run now, by hand
Start a flow yourself and fill in the fields it asks for before it goes.
From an inbound webhook
Another system posts to a URL with a secret header, and your workflow takes it from there.
Every node in the back-office designer
Timing, data and lookups, actions and notifications — each configured in its own panel instead of in code.
Run it, watch it, fix it
Automation you cannot inspect is automation you cannot trust.
Execution history
Every run is kept, with the output of each step and how long that step took.
Retry from where it broke
Fix the cause, then retry the failed step — or start the whole run again from the top.
Turn it off without losing it
Disable a workflow, duplicate it to try a variation, and enable it again when you are happy.
The second designer: the conversation itself
Workflows run in the back office. Playbooks are what the customer talks to — the same drag-and-drop canvas, pointed at the chat.
Ask, and keep the answer
Questions with the right keyboard and the right validation, so the answer is usable instead of approximate.
- Text, email, phone, date and rating questions
- Single choice, multi-select, and forms that validate
- Every answer becomes a variable the next step can use
Rich replies, per platform
Buttons, lists, carousels, link buttons and YouTube — each rendered the way the platform the customer is on actually supports it.
- Buttons, lists and carousels
- Link buttons and YouTube
- Adapts to what each platform allows
Logic, code and sub-playbooks
Branch on an answer, loop, call an endpoint, set a tag or a field — and where a flow needs real logic, run a sandboxed piece of JavaScript.
- Branching, loops and variables
- A sandboxed JavaScript step
- HTTP requests, tags and contact fields
- Sub-playbooks, so a long flow stays readable
AI, and a handoff that works
Add an AI agent or a simple auto-reply, and keep a guaranteed route to a person. Move a website visitor onto WhatsApp as the same contact.
- An AI agent, or AI auto-reply
- A guaranteed human handoff that notifies the team
- Cross-channel handoff keeps one contact
- An end-of-automation message, so nobody is left hanging
The parts you only notice when they fail
Replay a run on the canvas
Pick a recent run and watch it again on the designer, step by step — including the AI trace where a model was used.
Events that do not get lost
Events are written down before they are delivered, delivered once, parked when they fail, and replayable afterwards.
Automate outside Kalagh too
A community node package for your own self-hosted n8n, so automation you already run can drive the platform.
Automate the work nobody enjoys
Build one workflow and one playbook on the free trial, and watch the repetitive half of the day disappear.