Home/Features/Flow Builder

Automation

No-Code WhatsApp Chatbot Flow Builder

Build WhatsApp chatbot conversations with a drag-and-drop flow builder. 17 node types, keyword and event triggers, branching logic, AI replies and human handoff.

By Chirag Darji · Updated 7 Nov 2026 · 13 min read

Plans: All plans. AI Reply nodes use AI credits (1,000 free each month, 10 per AI reply) on every plan.

On this page
  1. What you get
  2. How it works
  3. What node types can a flow use?
  4. How does the Delay node handle scheduling?
  5. How does the flow builder protect the 24-hour messaging window?
  6. What can the AI Reply node do that a scripted node can't?
  7. Can a flow call my own systems?
  8. How does per-node opt-out enforcement work?
  9. With VGraple CRM vs building a WhatsApp bot by hand
  10. Who uses it
  11. What Meta allows
  12. Plans and limits
  13. Recent improvements
Booking bot in the Flow Builder canvas: a trigger, a greeting, quick replies that lead to a booking message, an AI answer or a human handoff

In short

  • Drag-and-drop canvas with 17 working node types: messages, templates, buttons, conditions, delays, AI replies, human handoff, API calls and more
  • Triggers on a keyword, any inbound message, a tag, a segment, a form submission, a new lead or an appointment event
  • Every free-form send is guarded by WhatsApp's 24-hour service window automatically, so a flow never wastes a doomed API call
  • No version history yet: a flow has draft, active, paused and archived states and a live run counter, not a rollback list

A WhatsApp chatbot flow is a conversation you build once on a visual canvas and it runs automatically for every customer who triggers it: someone types "price" and gets an instant answer with buttons, someone books an appointment and gets a reminder three days later, someone fills a lead form and gets qualified before a human ever sees the chat. VGraple CRM's flow builder gives you 17 working node types, six trigger types, branching logic and the AI Reply and AI Agent nodes, all connected on a drag-and-drop canvas with no code.

What you get

  • A drag-and-drop canvas (built on the same graph engine as the mobile app's flow viewer) with connected nodes and named handles for true/false and timeout paths
  • 17 working node types covering messages, templates, buttons, carousels, forms, catalog products, conditions, delays, API calls, AI replies and human handoff
  • Trigger types: keyword, any inbound message, customer goes quiet, tag added, contact field changed, segment entry, form submitted, new lead arrives, and three appointment events
  • Automatic 24-hour window protection on every free-form send, so a delayed step never fires a message Meta will reject
  • Flow variables you set once and reuse anywhere with {{variable_name}} interpolation, including API responses and quiz answers
  • Opt-out and block checks enforced on every node, not just at the start of a run, so a mid-flow STOP stops the flow immediately

How it works

  1. Create the flow and set a trigger. From the Flow Builder page, name your flow and open the canvas. The trigger node starts as Keyword / Inbound Message; switch it to Contact enters a Segment, Contact receives a Tag, Form Submitted, New lead arrives, or one of the three appointment triggers from the dropdown grouped by category (Messaging, Tags, Appointments, Forms).

Flow Builder list in VGraple CRM with each flow's status, trigger and number of runs

  1. Add steps. Click Add step (or press N) and pick Send Message, Send Template, Quick Replies, Condition, Delay, AI Reply or any of the other 13 node types, or click the green + under a step to add the next one below it, already connected. Tidy up lines the whole flow up top to bottom in one click. Buttons and list messages, template variables, and delay durations are all edited in the settings panel that opens on the right when you click a node.

  2. Branch with conditions. A Condition node reads a flow variable (var.reply, var.selected_option) or a contact field (contact.name, contact.phone), compares it with equals, contains, starts with, is empty or is not empty, and routes to a true or false path. Use this to send a different reply depending on which quick-reply button someone tapped.

  3. Add an AI Reply or Human Handoff node where a script would break down. The AI Reply node answers freely using VGraple AI by default, or your own OpenAI, Anthropic or Groq key if you added one, with an optional system prompt, and an optional knowledge base. The Human Handoff node sends a configurable handoff message, ends the automation, marks the chat Needs a person and alerts your team.

  4. Activate and test on your own number. Flip the flow from draft to active, then message your connected WhatsApp number with the trigger keyword. There is no separate sandbox for flows; you are testing the exact node graph a customer will run.

  5. Watch it run and refine. Each flow shows its run count on the list page. Open the flow again to adjust wording, add a branch, or connect a new node; changes apply to every execution that starts after you save.

What node types can a flow use?

The Add step list has 17 working node types beyond the trigger and end nodes: Send Message, Send Template, CTA Button (send_cta_url), Image Carousel, Wait for Reply, Wait until quiet, Quick Replies, Request Location, Contact Card, WhatsApp Form (a Meta WhatsApp Flow), Send Product (from your Meta catalog), Condition, Delay, Human Handoff, API Call, AI Reply, and Action. The Action node itself has seven sub-types: Add Tag, Remove Tag, Mark Opted Out, Resolve Conversation, Enroll in sequence, Set chat stage and Send Meta CAPI event. Quick Replies switches automatically from WhatsApp's native buttons (up to 3) to a list message (up to 10 options) once you add a fourth option, matching what the WhatsApp API actually supports.

AI and flows settings in VGraple CRM with provider keys and the Cron secret

Example

A coaching institute uses a Quick Replies node to ask "Which course are you interested in?" with four options; each option feeds a Condition node that routes to a course-specific brochure sent with Send Template.

How does the Delay node handle scheduling?

A Delay node can wait a fixed duration (hours and minutes) or wait relative to the contact's next scheduled appointment, before or after it, by a number of days and hours. The relative mode is built for reminder flows: set it to "1 day before appointment" and the flow pauses until that offset from whatever appointment the contact currently has booked. If the contact has no upcoming appointment when the node is reached, the delay is skipped rather than waiting forever.

Example

A clinic sets a Delay node to "1 day before, 0 hours" after an Appointment Booked trigger, followed by a Send Template node that sends the approved reminder template.

How does the flow builder protect the 24-hour messaging window?

Every node that sends free-form content, meaning anything that is not a pre-approved template, is checked against the conversation's 24-hour service window before it fires. If the window is closed, the flow does not attempt the send at all. Instead it writes a visible message into the conversation thread reading "[Not sent: send_message]" with the reason "24-hour service window closed", and moves to the next node. This matters most for Delay-heavy flows: a Send Message node scheduled to fire two days after a keyword trigger would otherwise hit Meta's error 131047 on every single attempt.

Meta policy

WhatsApp's Business Messaging Policy limits free-form (non-template) replies to the 24 hours after a customer's last message. Outside that window, only an approved template can reach them. Use a Send Template node for anything a Delay node might push past the window.

What can the AI Reply node do that a scripted node can't?

The AI Reply node answers in natural language using VGraple AI by default, with no key to add, or your own key if you prefer: OpenAI's GPT-4o Mini, Anthropic's Claude Haiku, or Groq. You write a system prompt (or generate one with the built-in wizard), optionally turn on conversational mode for back-and-forth chat instead of a single reply, and optionally attach a knowledge base so answers stay grounded in your own content. This is the same underlying capability as the AI chatbot feature, exposed as one node inside a larger scripted flow rather than a whole conversation.

Example

A real-estate agency scripts the first three questions (budget, location, property type) with Quick Replies nodes for reliability, then hands off to an AI Reply node for open-ended questions about a specific listing.

Can a flow call my own systems?

Yes, with the API Call node. It sends the flow's current variables as either a JSON POST body or a GET query string to a URL you provide, and the response is saved into a flow variable (api_response by default) you can reference in any later node with {{api_response}}. Your endpoint must return JSON or plain text; if it returns JSON, the whole object is stored as a string, so extract the specific field you need before returning it. This is how a flow can check real-time stock, look up an order status, or push a lead straight into an external system mid-conversation.

How does per-node opt-out enforcement work?

Most chatbot builders check consent once, when a flow starts. VGraple CRM's executor checks opted_out_at and is_blocked on the contact before running every single node in the loop, including on resume after a Wait for Reply or Delay step. A customer who sends STOP while a multi-day flow is sitting in a delay never receives the next scheduled message; the run is marked cancelled the moment the executor wakes up and sees the flag. The same loop also enforces a maximum of one visit per node per execution, so a badly wired flow (a condition that loops back on itself) breaks the loop instead of hammering the WhatsApp API forever.

With VGraple CRM vs building a WhatsApp bot by hand

Building it yourself with the Cloud APIVGraple CRM flow builder
Setting up a keyword replyWrite webhook handler code, deploy it, handle retriesAdd a Send Message node under the trigger with the green +, save
Branching on a customer's answerBuild your own state machine and variable storageCondition node with a dropdown of operators
Respecting the 24-hour windowTrack window_opened_at yourself, check it before every sendChecked automatically on every free-form node
Handling STOP mid-conversationPoll or webhook on opt-out events, cancel your own jobsChecked before every node, including on resume
Calling an AI modelWire up your own API client, prompt, and error handlingDrop in an AI Reply node, pick a provider
Handing off to a personBuild your own inbox and assignment logicHuman Handoff node routes into the team inbox
Testing a changeStage a test environment or risk breaking productionMessage your own connected number directly

Who uses it

Salons and clinics use flows for booking confirmations, pre-visit intake questions, and appointment reminders tied to the Delay node's relative-to-appointment mode. See WhatsApp automation for healthcare.

Coaching institutes run keyword-triggered flows that route a prospective student through a Quick Replies course picker into a course-specific brochure and a Human Handoff to a counselor. See WhatsApp automation for education and coaching.

D2C stores trigger a flow from Send Product nodes tied to their Meta catalog, letting a customer browse and order without leaving WhatsApp. See WhatsApp automation for ecommerce.

Real-estate agencies use AI Reply nodes for open-ended listing questions after a scripted qualification sequence collects budget and location. See WhatsApp automation for real estate.

What Meta allows

Meta policy

Meta's Business Messaging Policy requires free-form replies to stay inside the 24-hour customer service window that opens each time a customer messages you. Outside that window, only a pre-approved template can be sent. It also requires that an opt-out (STOP and equivalents) stop business-initiated messaging immediately.

The flow builder enforces both automatically: the 24-hour window guard blocks free-form sends and logs a visible failure instead of calling the API, and the opt-out check runs before every node executes, not only at flow start. Template-sending nodes (Send Template, WhatsApp Form) are unaffected by the window guard, because a template is exactly what Meta expects outside it.

Plans and limits

Flow Builder itself is available on every plan, including Free, with no cap on the number of flows or nodes you can build. What a plan sets is agent seats and stored contacts, from the Free plan (1 agent, 5,000 contacts, unlimited conversations) up through Starter and Growth to unlimited seats and contacts on Scale. Conversations are unlimited on every plan, so no flow is ever paused by conversation volume. The AI Reply node works on every plan and uses AI credits: 1,000 are free each month, and an AI reply costs 10.

Recent improvements

  • 2026-10: Added two ways to follow up on silence: a Wait until quiet step inside any flow (keyword, reply, wait 15 quiet minutes, follow up) and a Customer goes quiet trigger for every chat on a number. The timer restarts on every new message, and a customer gets one follow-up per message however many flows ran. Wait for Reply now takes hours and minutes and has its own No reply path. See following up when a customer goes quiet.
  • 2026-08: Channel routing fixed on every send inside a flow execution, so a reply from a multi-number org always goes out on the WhatsApp number the conversation is actually on, not a default fallback.
  • 2026-08: Wait for Reply timeouts are now enforced end to end, and the opt-out/block check runs before every node rather than only at flow start.
  • 2026-07: Fixed a crash in the flow editor when opening flows that were created by the sequence builder and had no saved node position.
  • 2026-07: Added the 24-hour service window guard on free-form send nodes, replacing silent Meta API failures with a visible logged message.
  • 2026-06: Fixed an N+1 query pattern in the cron jobs that check segment-entry and appointment-based flow triggers, cutting the per-tick database load.
  • 2026-06: Added the Send Product node, letting a flow send a single product from a connected Meta catalog with an optional message.

Frequently asked questions

What node types does the WhatsApp flow builder support?
17 working node types plus the trigger and end nodes. Send Message, Send Template, CTA Button, Image Carousel, Wait for Reply, Wait until quiet, Quick Replies, Request Location, Contact Card, WhatsApp Form, Send Product, Condition, Delay, Human Handoff, API Call, AI Reply and Action (tag or opt-out).
Can a WhatsApp flow trigger on something other than a keyword?
Yes. A flow's trigger node can fire on a keyword or any inbound message, a contact entering a segment, a contact receiving a tag, a form submission, a new lead arriving, or an appointment being booked, reminded, or completed.
Does the flow builder support branching logic?
Yes, with the Condition node. It compares a flow variable (like var.reply) or a contact field (contact.name, contact.phone) against a value using equals, not equals, contains, starts with, is empty or is not empty, then routes down a true or false path.
Can a WhatsApp flow send a message outside the 24-hour window?
Not a free-form one. Any node that sends free-form content (not a pre-approved template) is checked against the conversation's 24-hour service window before it fires. If the window is closed, the flow logs a visible failed message and moves on instead of calling the Meta API and getting rejected.
Does the flow builder have version history?
Not yet. A flow has draft, active, paused and archived states and a run counter on the flows list, but there is no saved history of past versions or a rollback button. Duplicate a flow before a risky edit if you want a fallback copy.
How do I test a WhatsApp flow before customers see it?
Save the flow as active, then message the connected WhatsApp number yourself with the trigger keyword. There is no separate sandbox environment for flows; the live number is the test environment, which also means you are exercising the exact code path a customer will hit.
Can a flow hand a conversation to a human agent?
Yes, with the Human Handoff node. It sends a configurable message ("Connecting you with a support agent..."), ends the automated run, marks the chat Needs a person, stops the AI in that chat and alerts your team. The AI Agent step, and an AI Reply step in conversational mode, also hand the chat to a person on their own when a customer asks for one.
What AI models can the AI Reply node use?
VGraple AI by default, with no key to add. On Starter and above you can also add your own key in Settings, AI for OpenAI (GPT-4o Mini), Anthropic (Claude Haiku) or Groq, which makes each action cost one fifth of the credits. If more than one is configured you choose per node; the node also supports a conversational back-and-forth mode and an optional knowledge base attachment.
Can a flow call an external API or webhook?
Yes, with the API Call node. It sends flow variables as a JSON body (POST) or query string (GET) to your endpoint and saves the response into a flow variable you can use in later messages with {{variable_name}}.
Is there a limit to how many WhatsApp flows I can build?
No plan-based cap on flow count. The limits that do apply are the org-wide agent seats and stored contacts on your plan, and conversations are unlimited on every plan; a flow itself has no node-count ceiling in the product today.
What happens if a customer opts out mid-flow?
The executor checks opted_out_at and is_blocked before running every single node, not only at the start. A STOP received while a flow sits in a Wait for Reply or Delay step cancels the run immediately rather than letting it finish sending.
Do WhatsApp drip sequences use the same flow builder?
Sequences are Flows with an internal is_sequence flag, so they share the same node engine and execution history described here. The dedicated sequences page covers the enrollment and timing side.

Run your WhatsApp on VGraple CRM

Free forever plan, official Meta WhatsApp Business API, set up in 15 minutes. No card needed.