Journeys. Flows that follow behaviour.
Multi-step lifecycle flows triggered by user events and conditions.
Follows a user, not a schedule.
Reaching the goal exits the journey, so no further steps are sent.
What moves a user forward.
Event-based entry
Journeys can begin from configured signup, behaviour, or product events.
Timed waits
Steps can pause for a defined period.
Conditional branches
Users can follow different paths according to attributes, activity, or audience membership.
Iftar-aware waits
A wait step can hold until iftar, not just a fixed duration, for Ramadan-sensitive timing.
Automatic completion
A user's enrollment is marked complete once they finish a journey's configured steps, so it never runs indefinitely.
From event model to first enrollment.
Connect the REST API
Connect the application through the REST API so it can send journey events and receive eligible actions.
Define the event model
Agree stable names and properties for the events that start, advance, pause, or end a journey.
Set journey guardrails
Configure entry conditions, exclusions, waiting periods, exit rules, and permitted actions.
Build and activate
Create the journey steps, attach approved content, test each path, and activate the journey.
Journeys teams have actually built.
Account Onboarding Journey
A Saudi bank could guide an applicant through missing onboarding steps after receiving status events from its systems.
Claim Follow-up Journey
An insurer could guide a policyholder from claim submission through document completion and assessment updates.
Seller Activation Journey
A marketplace could guide a new seller through identity checks, catalogue setup, and first-listing preparation.
Only as reliable as its events.
Event Quality Matters
Journey state can be incorrect when source events are missing, duplicated, delayed, or sent with inconsistent identifiers.
Not A Core Workflow
Journeys should not replace systems responsible for account opening, payments, underwriting, claims, or other core transactions.
Where it stops and Campaigns begins.
Do Journeys require Sensors?
No. Journeys can use events and attributes supplied through existing integrations, while Sensors offer an additional trigger source in preview.
How much engineering is required?
Engineering must provide the events, attributes, and channel connections used by a journey. Teams can then assemble flows from those configured inputs.
How do Journeys differ from Campaigns?
Campaigns manage a targeted deployment, while Journeys coordinate a sequence of actions that changes with user behaviour and timing.
Reads signals from Sensors.
Messaging Channels
Messaging Channels deliver the push, WhatsApp, SMS, popup, and in-app steps used within a journey.
Journeys is one of eight.
Production integration today uses the REST API. Native SDKs for React Native, iOS, Android and Web are in preview and are not generally available. The @contentflow/cli package is not published yet.