Build workflows without writing code.
Trigger, condition, action. Drag the steps into place and the repetitive work runs itself — greetings, routing, qualification, after-hours cover and everything you currently do by hand.
- No code required
- Test before you publish
- Free plan available
3 parts
Every workflow is a trigger, a condition and an action
No code
Built on a canvas — the API is optional, not required
Any channel
Rules run on website chat, WhatsApp, Instagram and email
Test first
Run a flow against yourself before a customer ever sees it
Trigger. Condition. Action.
Three ideas, and that is the whole model. When this happens, if this is true, do that. Everything else is a variation on it.
Trigger
When this happens
- Visitor lands on a page you choose —
/pricing,/checkout - Time on page passes 30 seconds
- Scroll depth reaches 70%, or exit intent is detected
- Cart value goes above a threshold you set
- Return visit, or a first visit from a paid campaign
- An inbound message contains a keyword like
refund - A conversation goes unanswered for 10 minutes
- Working hours start, or end
Condition
If this is true
- Visitor is on a specific page, path or domain
- Customer is known, or has ordered before
- Plan, company size or lifetime value
- Browser language is
es— or anything else - Inside or outside your working hours
- Conversation already has a tag, priority or owner
- AI confidence is below the threshold you set
- At least one agent is online in a given team
Action
Do that
- Send a message, or open the widget
- Show a menu of FAQ answers to pick from
- Capture an email, a phone number or a custom field
- Assign to an agent, a team, or round robin
- Add a tag, set a priority, change the status
- Hand over to a human with a summary attached
- Create a ticket, or push a contact to your CRM
- Notify a Slack channel, or call a webhook
Steps can be chained, branched and delayed. A flow can wait 10 seconds, check a condition again, and take a different path the second time.
See the whole path before a customer does.
The builder is a canvas, not a settings page. You can read a flow top to bottom and know exactly what a visitor will experience — which is the only reliable way to catch a bad one.
- Branch on anything — customer data, conversation data or AI confidence.
- Delays and re-checks so a flow can wait, look again, then decide.
- Test mode runs the flow against your own session, step by step.
- Publish, pause, duplicate — and see a log of every run with its outcome.
Four workflows you can copy on your first afternoon.
Each of these ships as a template. Open it, change the numbers and the wording to match your business, then publish.
Catch the checkout that stalls
Someone with a full cart who stops moving is usually stuck on one thing: delivery time, sizing or a payment method. Ask before they close the tab.
- Only fires above a cart value you choose
- Asks once, then stops if there is no reply
- Hands to a human the moment they answer
// POST to your endpoint, signed with your webhook secretPOST https://your-app.com/hooks/chatdrill{ "event": "conversation.tagged", "conversation_id": "cv_8241", "tag": "refund-request", "channel": "whatsapp", "customer": { "email": "sarah@example.com", "orders": 4 }, "occurred_at": "2026-03-04T09:12:44Z"}When the last step lives in your own stack.
Some actions belong in your systems, not ours. A webhook action posts a signed JSON payload wherever you want it, and the REST API lets your app drive Chatdrill in return.
- Events for what matters — created, assigned, tagged, closed, lead captured.
- Signed requests with a shared secret, so you can verify what you receive.
- Retries and logs, including the response your endpoint returned.
- No-code alternatives through Zapier and Make when you'd rather not build.
Automation your customers don't resent.
Automated chat gets a bad name for a reason: it interrupts, it repeats itself, and it hides the way out. Every flow you build in Chatdrill has limits on all three.
- Ask once — frequency caps per session, per visitor, per page.
- Stop on reply so a real conversation is never interrupted by a rule.
- A human exit in every flow — asking for a person always works.
- Quiet by default where it should be: mobile, checkout, existing customers.
Your brandEverything you can automate out of the box.
Start from a template, or start from an empty canvas. Both end up in the same builder.
Visual builder
Drag steps onto a canvas, branch them, and see the whole path before anyone else does.
Smart triggers
Page, time, scroll, exit intent, cart value, campaign, keyword or working hours.
Conditions and branching
Split a flow on customer data, conversation data or AI confidence — as deep as you need.
Routing rules
Send conversations to the right team by topic, language, plan or availability.
Auto assignment
Round robin across who is actually online, with fallback to the shared queue.
Welcome messages
Different greetings per page, per language and per audience — new visitor or returning customer.
After-hours workflow
AI first, then email capture with a real reply time, then a queued ticket for the morning.
Lead qualification
Ask the two questions that matter, score the answer, and route or book a meeting.
Human escalation
Every flow has an exit to a person — by keyword, by confidence, or because they asked.
Before you automate anything.
No. Flows are built by dragging triggers, conditions and actions onto a canvas and filling in plain-language fields. Webhooks and the REST API are there for teams who want to connect their own systems, but nothing in the builder requires code or a technical review.
Visitor behaviour (page, time on page, scroll depth, exit intent, cart value, referrer, return visit), inbound messages on any channel including keyword matches, conversation state such as unanswered for ten minutes, and time-based events like working hours starting or ending. You can combine several conditions on top of any trigger.
Only if you configure it badly, and the defaults make that hard. Every proactive flow has frequency caps, a once-per-session option, an exclusion list of pages, and a stop-on-reply rule so a customer who answers is never interrupted again by automation. You can also exclude known customers or anyone with an open conversation.
You add an escalation step, and most templates already include one. The conversation goes to a person or a team with the transcript and a summary attached, or — outside working hours — it captures an email address and states when someone will reply. A flow should never be a dead end.
Yes. Test mode runs the flow against your own session so you can see each step fire without touching real visitors. Flows can be published, paused and duplicated, and every run is logged, so you can see where people dropped out and fix that step specifically.
Pick the events you care about — conversation created, tagged, assigned, closed, lead captured — and Chatdrill sends a signed JSON payload to your endpoint. Failed deliveries are retried with backoff, and every attempt is logged with the response you returned, so debugging does not require guesswork.
Automate the work nobody enjoys doing twice.
Build your first workflow in Chatdrill this afternoon.
No credit card required.