AlgorithmX
Campaigns4 min read

Workflow Journeys

Build automated customer journeys with a visual drag-and-drop workflow editor.

Workflow Journeys lets you build automated customer journeys by connecting triggers, waits, actions, and decision logic on a visual canvas. Use it to automate follow-up communication across email and WhatsApp according to an event or a time-based schedule.

[!NOTE] This module is under active development. Available blocks and automation capabilities may expand in future releases.

Understand the workflow editor

The builder has a block library on the left and a dotted canvas for designing the journey. Drag a block from the library onto the canvas, configure it, and connect it to the next block to define the journey sequence.

The editor also includes vertical and horizontal layout controls, zoom controls, a minimap, and a Done action. These tools help keep larger flows readable while you work.

Drag blocks from the library onto the canvas, then arrange and connect them to build the journey.
Workflow editor with the block library, dotted canvas, layout controls, and Done action

Drag blocks from the library onto the canvas, then arrange and connect them to build the journey.

Manage workflow journeys

From a journey's actions menu, you can open it, edit its configuration, activate it when it is ready to run, or delete it when it is no longer needed.

Use the actions menu to view, edit, activate, or delete a workflow journey.
Workflow journey actions menu with View, Edit, Activate, and Delete actions

Use the actions menu to view, edit, activate, or delete a workflow journey.

Available workflow blocks

The block library is organized by purpose.

Trigger

Start a journey with one of these events:

  • Time for a time-based start.
  • Recurring for a repeated schedule.
  • Event for a customer or system event.

Configure a time trigger

Choose the exact date and time to run the journey, then optionally limit the trigger to a segment or contact list.

Set the one-time start date and time, then optionally filter the audience.
Time Trigger settings with run date, segment, and contact list fields

Set the one-time start date and time, then optionally filter the audience.

Configure a recurring trigger

Choose the start date, frequency, hour, and minute for repeating journeys. The generated cron expression reflects the selected schedule; you can also limit the recurring trigger to a segment or contact list.

Set a recurring schedule and optionally restrict it to a selected audience.
Recurring Trigger settings with start date, frequency, schedule time, cron expression, segment, and contact list

Set a recurring schedule and optionally restrict it to a selected audience.

Wait

Use a wait block to control when the next step happens:

  • Relative Delay.
  • Absolute Delay.
  • Time Slot Delay.
  • Wait for Event.

Relative Delay

Set a numeric delay and choose Minutes, Hours, Days, or Weeks before the next step can run.

Pause the journey for a specified amount of time before continuing.
Relative Delay wait settings with delay value and unit selector

Pause the journey for a specified amount of time before continuing.

Absolute Delay

Use an absolute delay when the journey should wait until one specific date and time.

Pause the journey until the selected date and time.
Absolute Delay wait settings with date and time selector

Pause the journey until the selected date and time.

Time Slot Delay

Choose a daily or weekly time slot to hold the journey until an appropriate sending window.

Use a time slot to continue the journey only during an allowed daily or weekly window.
Time Slot Delay settings with Daily and Weekly frequency choices

Use a time slot to continue the journey only during an allowed daily or weekly window.

Optimization

Use A/B Test when the journey needs to compare alternate paths or messaging approaches.

Set the split percentage to route users between the green and red paths.
A/B Test settings with a split percentage control

Set the split percentage to route users between the green and red paths.

Action

Use actions to communicate with the customer:

  • Send Email.
  • Send WhatsApp.

Send Email

Select the email template and sender, then provide the subject used for the email action.

Configure the template, sender identity, and subject before adding the email action to the journey.
Send Email action settings with template, sender, and subject fields

Configure the template, sender identity, and subject before adding the email action to the journey.

Send WhatsApp

Select the approved WhatsApp template and the sender number that will deliver the message.

Choose the WhatsApp template and sender number for the message action.
Send WhatsApp action settings with template and sender number selectors

Choose the WhatsApp template and sender number for the message action.

Flow

Use Exit to end the journey deliberately.

Add Exit to finish a branch of the workflow intentionally.
Exit workflow node with no configuration settings

Add Exit to finish a branch of the workflow intentionally.

Build a journey

A typical journey begins with a trigger, waits for a condition or elapsed time, sends one or more messages, and then exits. The illustrated flow, for example, starts with a Time Trigger, waits using an Absolute Delay, and branches into email and WhatsApp actions before later wait conditions and exits.

Build your own journey in this order:

  1. Drag the starting trigger to the canvas.
  2. Add a wait block when timing or a customer action must occur before the next step.
  3. Add Send Email or Send WhatsApp actions.
  4. Insert an A/B Test when you need alternate paths.
  5. Connect each block in the desired sequence and finish each branch with Exit.

Configure Wait for Event

The Wait for Event configuration panel lets the journey pause until a selected communication event occurs. The event list includes options such as:

  • Email Delivered, Email Undelivered, Email Open, Email Click, and Email Unsubscribe.
  • WhatsApp Sent, WhatsApp Delivered, WhatsApp Undelivered, and WhatsApp Open.

Set the Max Wait Time and choose its unit: Minutes, Hours, Days, or Weeks. This establishes how long the journey should wait for the selected event before following the next configured logic.

Use this block for follow-ups that should happen only after, or after waiting for, a meaningful delivery or engagement signal.

Choose the event and maximum wait time; the journey continues when the event occurs or the time limit expires.
Wait for Event settings with event selector, maximum wait time, and unit

Choose the event and maximum wait time; the journey continues when the event occurs or the time limit expires.

Review before activating

Before finishing a journey, review every connection and block configuration. Confirm that each branch has a clear next step or exit, that message actions use the intended content, and that wait durations are appropriate for the customer experience you want to deliver.