Create Journey - Workflow

Once you've configured the trigger for your journey, the next step is to design the workflow—this is the visual path that defines what happens after someone enters your journey.

Think of it like a flowchart: the journey starts with a trigger and continues through a series of nodes, each of which acts, checks a condition, or controls the timing.

🔧 How to Add a Node

• Start with the trigger node (auto-created).

• Click the ➕ button on the line to add a new step.

• Choose a node type from the menu.

• Customize the settings for that node.

• Connect more nodes to build your workflow.

There are two types of nodes:

• Action Node: Action nodes perform tasks like sending messages or making API calls.

• Flow Control Node : These nodes manage the flow of the journey with conditions, wait times, and branching.

Action Node

• Send WhatsApp Template - Use this when you want to send a pre-approved WhatsApp message.

  • Add a node

  • Navigate to WhatsApp -> select Send WhatsApp template.

  • Setup WhatsApp template

    
  • Select a template from the approved templates list.

  • Add values for variables in the template

    1. You can add dynamic values for a personalized message with fallback (in case if the values fetch fails)

    
  • Select settings

    1. Choose the action to take when the recipient replies

       1. Here you can set up bots to engage when the recipient replies either with QuickReply buttons or any other text.

    2. Add UTM parameters (optional)

• API call - Use this when you need to send data to another system (like your CRM or backend server).

  • Set the endpoint URL.

  • Define headers and request body.

  • Use dynamic values from previous steps.

  • Specify which response codes count as success.

Flow Control Node

• Wait - Use this when you want to pause the journey before the next step.

  • Wait for X minutes/hours/days.

  • Wait until a specific time of day(s) (e.g., 9:00 AM).

• Conditional branching Node - Use this to create multiple paths based on user actions, events, or other conditions.

  • Add branches (min 1 conditional branch is required)

  • Configure filter conditions for each branch

  • User is directed to the default branch when no conditional branch matches

• Filter in Node - Use this when you want users to proceed through the journey only if they meet specific conditions.

  • Add filter condition groups using fields like:

    • Event data

    • Past journey data

  • Use logical operators between conditions and groups (AND/OR)

• A/B testing Node - Use this when you want to split users into different groups to test variations of a journey.

  • Add 2–5 branches

  • Set weight distribution (e.g., 50:50) in ratio.

  • Connect different messages/nodes under each branch

• Exit Node - Marks the end of a journey branch.

  • Added by default at the end of the journey branch

  • No configuration required

Delete a Node

To delete a node,

1. Navigate to the node you want to delete

2. Click on the three-dot button, and select delete node

Delete a Branching Node

To delete a branching type of node, like Conditional Branching, A/B testing, or Filter In,

If you’ve added more steps after one or more branches (e.g., sending messages, wait steps, filters), then you’ll be shown two options:

1. Delete all subsequent nodes

   • This will remove the Branching node and all subsequent nodes under all its branches.

   • Use this if you're redesigning this entire part of the journey.

2. Keep one path

   • You will be asked to choose one branch to keep.

   • All other branches and their steps will be deleted.

   • The selected path will now connect to the node that came before the Branching node