Journey Automations

When a lead arrives, you want to follow up immediately — but you also need to send a reminder 24 hours later, and perhaps another message the day after that. Before Journey Automations, each of those steps had to be managed manually or through separate tools outside Driftrock. Journey Automations lets you build multi-step follow-up sequences entirely within Driftrock, so the right messages go to the right leads at the right time, automatically.

Journey Automations is a feature that lets you create ordered, timed sequences of automation steps for leads. Each step can be an action (such as sending a WhatsApp message, an email, an internal notification, or a CRM delivery) or a wait period. Steps execute in order, and if one step fails, subsequent steps are blocked from running — preventing inconsistent or out-of-sequence outreach.

A Journey is attached to a capture and triggered automatically when a lead arrives. You define the steps once, and Driftrock handles execution for every lead that flows through.

Without sequenced automations, multi-step follow-up workflows require manual effort or external tools — neither of which scales well. Journey Automations removes that overhead by running timed, ordered outreach sequences autonomously. Leads receive timely follow-ups without anyone needing to track or trigger them manually.

For teams running WhatsApp qualification flows, Journey Automations is the backbone of the sequence: send an initial message, wait for a response window, send a reminder, then route the lead based on the outcome — all without human intervention. The result is higher response rates and more leads progressing through qualification.

A Journey is a sequence of steps that Driftrock executes in order for each lead. When you set up a Journey, you define each step as either an action (a WhatsApp message, email, notification, spreadsheet export, or CRM delivery) or a wait period (such as 1 minute, 24 hours, or any custom interval). Steps run one after another, respecting the wait times you configure.

If a step fails — for example, if a WhatsApp message cannot be delivered — subsequent steps are blocked. This prevents partial or out-of-order outreach. You can also define exit conditions: if a lead converts, replies, or a specific data field is updated, Driftrock marks the journey as complete and halts further steps automatically. Exit conditions are evaluated on every person data change, so journeys exit as soon as they are no longer needed.

Each lead's journey progress is visible in the People tab, where you can see a step summary for every person and drill into a full step log for detailed triage.

Prerequisites:

Journey Automations must be enabled for your account. Contact your Driftrock account manager to have the feature activated.

Any automation actions you want to use as steps (WhatsApp messages, autoresponder emails, CRM connections) must be created before building the Journey.

Open the relevant Capture in Driftrock and navigate to the Automate tab.

Create a new automation and select "Driftrock Journey" as the automation type.

Open the Journey builder. You will see three sections: Settings, Steps, and Automations.

In Settings, define your exit rules: the conditions under which a lead should be removed from the journey and no further steps should run (for example, if the lead has already converted or replied).

In Steps, add your steps in order. For each step, select the automation action to run, then set the wait time before the next step begins.

Repeat until your full sequence is built. There is no limit on the number of steps.

Save and activate the Journey. Driftrock will begin processing new leads through the sequence automatically.

Configure your exit conditions in Settings before building your steps. A well-defined exit rule means leads who qualify early are removed from the queue cleanly, so they do not receive unnecessary follow-up messages after they have already responded.

If a lead shows as "completed" in the People tab and you are unsure why, open the step detail modal. It shows the outcome of every step in sequence, making it easy to see whether the journey ended because all steps completed or because an exit condition was triggered.