Campaign Nodes

This page explains each node type available in the Campaign Builder in detail.

1. START Node

The START node is the entry point of every campaign. It defines how and when the campaign begins.

Trigger types

Trigger	Description	Additional settings
Manual	You start the campaign manually	No extra settings
Schedule	Campaign starts at a specific date and time	Scheduled date/time picker

Schedule settings:

Date must be at least 5 minutes in the future
Maximum 12 months ahead

📸

Screenshot: START node configuration showing trigger type selection

start-node-config.png

1. Click on the START node in the Campaign Builder
2. Show the trigger type dropdown with all options
3. Capture the configuration panel
Save to: static/img/screenshots/drip-campaigns/nodes/start-node-config.png

2. MESSAGE Node

The MESSAGE node sends a message to the enrolled contact. This is the core building block of every drip campaign. The message configuration depends on the campaign's channel.

WhatsApp campaigns

For WhatsApp campaigns, the MESSAGE node sends an approved template message.

Setting	Description
Template	Select an approved WhatsApp template
Parameters	Map template variables to values (static text or contact data)
Step Name	Optional display name for this step (up to 255 characters)

A slide-in preview panel shows how the template will look on the customer's phone.

Why templates only for WhatsApp?

Drip campaigns send messages over days or weeks, which means contacts are almost certainly outside the 24-hour messaging window. WhatsApp requires approved templates for messages sent outside this window.

Messenger and Instagram campaigns

For Messenger and Instagram campaigns, the MESSAGE node lets you compose a message directly — no template approval is required.

Message Type	Description
Text Message	Free-text message (up to 2,000 characters) with an optional media URL attachment
Button Message	Structured message with text body and up to 3 buttons
Card Message	Generic template / carousel card with image, title, subtitle, and buttons

📸

Screenshot: MESSAGE node configuration showing template selection and parameter mapping

message-node-config.png

1. Add a MESSAGE node to the campaign
2. Select an approved template (WhatsApp) or compose a message (Messenger/Instagram)
3. Map any template parameters
4. Capture the configuration panel
Save to: static/img/screenshots/drip-campaigns/nodes/message-node-config.png

3. DELAY Node

The DELAY node controls when the next step happens. It pauses the campaign for a specified amount of time before continuing.

Delay types

Type	How it works	Example
Send Immediately	No delay — the next step runs right away	First message in a campaign
After X days at specific time	Wait a number of days, then send at a specific time	"After 3 days at 10:00 AM"
On specific date and time	Send on an exact date and time	"On Feb 15, 2025 at 2:00 PM"
Based on message status	Wait until the previous message reaches a specific status	"After message is read" or "After 48 hours if not read"

📸

Screenshot: DELAY node configuration showing delay type options

delay-node-config.png

1. Add a DELAY node to the campaign
2. Show the delay type dropdown with all options
3. Capture the configuration panel
Save to: static/img/screenshots/drip-campaigns/nodes/delay-node-config.png

After X days at specific time

Setting	Description
Days	Number of days to wait
Time	What time to send (e.g., 10:00 AM)

Example: "Wait 3 days, then send at 10:00 AM" — If the previous message was sent on Monday, the next message goes out on Thursday at 10:00 AM.

On specific date and time

Setting	Description
Date and time	The exact date and time to send

Example: "Send on February 15, 2025 at 2:00 PM" — Useful for event-based campaigns.

Based on message status

Setting	Description
Wait for status	The message status to wait for (channel-dependent — see below)
Timeout	How long to wait before giving up (1–168 hours)

The available statuses depend on the campaign channel:

Status	WhatsApp	Messenger / Instagram
Delivered	Yes	—
Read	Yes	Yes
Replied	Yes	Yes

Example: "Wait until the message is read, timeout after 48 hours" — If the contact reads the message within 48 hours, continue. If not, the timeout triggers and you can branch to a different path.

info

Messenger and Instagram do not provide delivery receipts, so the "Delivered" status is not available for those channels.

Timing best practices

Morning messages (9:00–11:00 AM) typically get higher open rates
Space messages 1–3 days apart for nurturing campaigns
Avoid weekends for business communications
Use status-based delays for engagement-driven campaigns

4. BRANCH Node

The BRANCH node splits the campaign into different paths based on how the contact interacted with the previous message.

Branch paths

The available branch paths depend on the campaign channel:

Path	When it triggers	WhatsApp	Messenger / Instagram
Replied	Contact replied to the message	Yes	Yes
Read	Contact read the message (but didn't reply)	Yes	Yes
Delivered	Message was delivered (but not read)	Yes	—
Timeout	None of the above happened within the timeout period	Yes	Yes

The Timeout path is always required and cannot be removed. Each path has a configurable wait time (minutes to wait after the status is achieved before executing that branch's steps).

📸

Screenshot: BRANCH node configuration showing path options

branch-node-config.png

1. Add a BRANCH node after a MESSAGE node
2. Configure the branch paths and timeout
3. Capture the configuration showing multiple paths
Save to: static/img/screenshots/drip-campaigns/nodes/branch-node-config.png

How branching works

After a message is sent, the system waits for the contact to interact:

Message Sent
     │
     ├── Contact replied? ──────▶ REPLIED path
     │
     ├── Contact read it? ──────▶ READ path
     │
     ├── Message delivered? ────▶ DELIVERED path
     │
     └── Timeout reached? ─────▶ TIMEOUT path

Evaluation order: The system checks in the order shown above. The first matching condition wins. So if a contact both read and replied, the "Replied" path is taken because it's checked first.

Use case: Engagement-based routing

Step 1: Send promotional message
     ↓
BRANCH
  ├── Replied → Thank them, assign to sales agent
  ├── Read → Send a follow-up reminder after 1 day
  └── Timeout → Send a different message with a stronger call-to-action

5. CHATBOT Node

The CHATBOT node hands off the contact to a Chatbot Flow. Once the handoff happens, the drip campaign ends for that contact and the chatbot takes over.

Setting	Description
Chatbot Flow	Select an existing chatbot flow to hand off to

Important: The Chatbot node is always a terminal step — no steps can come after it. The contact's enrollment status changes to "Chatbot Handoff".

Use case: After 3 days of nurturing messages, hand the contact off to an interactive product recommendation chatbot for a personalized experience.

6. END Node

The END node marks the end of a campaign path. When a contact reaches an END node, their enrollment is marked as complete.

Every path in the campaign must end with an END node. If you have branches, each branch needs its own END node.

Node summary

Node	What it does	Key settings	Terminal?
START	Entry point, defines trigger	Trigger type, schedule	No
MESSAGE	Sends a template message	Template, parameters	No
DELAY	Waits before next step	Delay type, duration, time	No
BRANCH	Splits based on message status	Paths, timeout	No
CHATBOT	Hands off to chatbot flow	Chatbot flow selection	Yes
END	Marks campaign completion	None	Yes

1. START Node​

Trigger types​

2. MESSAGE Node​

WhatsApp campaigns​

Messenger and Instagram campaigns​

3. DELAY Node​

Delay types​

After X days at specific time​

On specific date and time​

Based on message status​

4. BRANCH Node​

Branch paths​

How branching works​

5. CHATBOT Node​

6. END Node​

Node summary​