Chatbot Nodes
Chatbots help make customer communication faster, easier, and more personalized. In WappCloud, you can create chatbots without coding using a simple drag-and-drop builder.
The widget panel in the Flow Builder groups nodes into five categories — Trigger, Action, Interactive, Advanced, and Message. This page gives a quick summary of every node; click through for the full guide on each.
Trigger
Keyword Node
Starts a chatbot flow when a contact sends a matching trigger word. See Keyword Node for trigger words, match type, session expiry, and on-mismatch behavior for Interactive Button/List nodes.
Ad Welcome Sequence Node
Starts a chatbot flow when a customer taps a suggested reply or FAQ from a Click-to-WhatsApp ad’s welcome sequence, instead of typing a keyword. See Ad Welcome Sequence Node for how to connect a sequence and choose which phrases start the flow.
Webhook Node
Starts a chatbot flow when an external system (your backend, Shopify, Zapier, Make, n8n, etc.) posts data to a generated URL. See Webhook Node for setting up the URL, secret, and phone number mapping.
New Contact Trigger Node
Automatically starts the flow the moment a completely new contact is added to WappCloud — whether they message you for the first time, or you add them manually or import them. There’s no keyword to set up for this one; it fires on its own. This node has no field to configure other than its Enrollment Rules (see below).
New Message Trigger Node
Automatically starts the flow the first time a contact sends you a WhatsApp message — even if that contact already existed in WappCloud before (for example, added manually or imported) but had never actually messaged you. This is different from the New Contact trigger, which only fires when the contact record itself is first created. This node also has no field to configure other than its Enrollment Rules.
Lead Stage Changed Trigger Node
Starts the flow automatically the moment any contact’s CRM stage is changed to a stage you pick (for example “Qualified” or “Demo Booked”) — the contact doesn’t need to reply to a message first. Choose the stage from a dropdown, then set up Enrollment Rules.
Attribute Changed Trigger Node
Starts the flow automatically the moment a piece of contact information you track (an “Attribute” — for example “Budget” or “City”) is added or updated on a contact. Choose the attribute from a dropdown, then set up Enrollment Rules.
Enrollment Rules (Eligibility, Suppression, and Re-entry)
Each of the four trigger nodes above (and the Lead Stage / Attribute Changed triggers in particular) includes an Enrollment Rules panel to control exactly who is allowed to start the flow:
- Eligibility — add one or more conditions that must ALL match for a contact to be enrolled. Leave this empty to allow anyone.
- Suppression — add one or more conditions where, if ANY of them match, the contact is never enrolled — even if they matched the Eligibility conditions above.
- Allow re-entry (Lead Stage Changed and Attribute Changed triggers only) — a checkbox labeled “Allow the same contact to go through this flow more than once.” Off (the default) means once a contact finishes or is stopped in the flow, they won’t start it again even if the trigger condition happens again later. Turning it on lets them go through the flow again every time the condition is met. This checkbox isn’t shown for the New Contact and New Message triggers, since those events can only happen once per contact anyway.
Note: A flow can only start from one trigger. If you place more than one trigger node (for example a Keyword node and a New Contact node) on the same flow’s canvas, only one of them will actually be used to start the flow — remove the others so it’s clear which one is active.
Action
Question Node
Asks a question with a fixed set of options and branches based on the reply. See Question Node.
Input Node
Collects free-text information from the contact — a name, email, or any custom reply — and saves it for reuse later in the flow. See Input Node.
Interactive
Custom Template (Interactive Button) Node
Sends an interactive message with up to 3 tappable buttons. See Custom Template Node.
CTA URL Node
Sends a message with a button that opens an external link — a website, form, or payment page. See CTA URL Node.
List Node
Displays multiple options grouped into sections, for when you need more choices than 3 buttons allow. See List Node.
Advanced
API Node
Connects to an external system to send, receive, or process data dynamically. See API Node for setting up requests, testing, and routing based on the response.
Google Sheet Node
Pushes the flow’s report data into a Google Sheet you own. See Google Sheet Node.
Assign Tag Node
Applies an existing tag to the contact for segmentation. See Assign Tag Node.
Lead Stage Node
Moves the contact into a CRM lead stage. See Lead Stage Node.
Round Robin Node
Hands the conversation over to a live agent, distributing contacts evenly across your team. See Round Robin Node.
Condition Node
Branches the flow into true/false paths based on a contact attribute, webhook field, or earlier flow value. See Condition Node.
Set/Remove Attribute Node
Sets or clears a custom contact attribute from within the flow. See Set/Remove Attribute Node.
Time Delay Node
Pauses the flow for a set duration before continuing. See Time Delay Node.
Message
Text Message Node
Sends a plain text message and auto-advances. See Text Message Node.
Image Message Node
Sends an image and auto-advances. See Image Message Node.
Video Message Node
Sends a video and auto-advances. See Video Message Node.
Audio Message Node
Sends an audio clip and auto-advances. See Audio Message Node.
Document Message Node
Sends a file (PDF, spreadsheet, etc.) and auto-advances. See Document Message Node.
Template Node
Sends a pre-approved WhatsApp message template, with optional button-based branching. See Template Node.