Skip to Content
WorkflowBuilderSequences & Campaigns

Sequences & Campaigns

Sequences are automated series of messages (drip campaigns) sent over time. This page explains how to enroll users into these campaigns and the rules for managing them.

The “One Sequence” Rule

To ensure a good user experience and prevent spam, our system enforces a strict rule regarding active campaigns.

Limit: A single contact can only be active in one sequence at a time per business number.

  • Scheduling a new sequence automatically cancels any previous sequence the user was in.
  • Canceling simply stops the currently active sequence.

1. The Account Switch (Required)

Before you can schedule a sequence, you must place the Account Switch node.

Why is this needed? Journeys depend on WhatsApp Templates, which are unique to each WhatsApp Business Account (WABA). This node helps the builder understand which account context to use so it can load the correct list of sequences for you.

  • How to use: Simply drag and drop the Account Switch node from the menu. It is pre-configured to check the global $$whatsappBusinessAccountId variable automatically.
  • Connection: You must connect your Schedule Sequence node to one of the paths coming out of this switch.

Critical: If you do not place this node first, the “Sequence ID” dropdown in the next step will remain empty because the system cannot verify which account allows which templates.

2. Schedule Sequence

Use this block to enroll the user into a drip campaign.

Schedule Sequence Node UI Configuration

  • Prerequisite: Must be connected after an Account Switch node.
  • Sequence ID: Select the specific campaign from the dropdown list.
  • Behavior: Enrollment is immediate. If the user was in a different sequence, they are removed from it and started fresh here.

3. Cancel Sequence

Use this block to stop a campaign. This is commonly used when a user achieves a goal (like “Purchase”) or asks to “Stop.”

Cancel Sequence Node UI Configuration

  • Action: Immediately removes the user from their active sequence.
  • Reason: You can optionally record a reason (e.g., “User Opt-ed Out”) for analytics.
Logic & Flow ControlStarting the Flow