Building a journey

Journeys are node graphs: a trigger node feeds into send, delay, wait_event, branch, split, update_contact, goal and exit nodes.

Node types

Type	What it does
send	Send a message on any channel
delay	Wait a fixed number of minutes
wait_event	Wait for an event, with a timeout that branches separately
branch	If/else based on segment membership
split	A/B split by weight
update_contact	Write a field back to the contact
goal	Marks the journey as converted (terminal)
exit	Ends the journey without a goal (terminal)

Trigger types

event (any tracked event), segment_enter (a contact enters a segment), or manual (added by hand or via API).

Start from a real template

Three templates ship with the platform and can be installed as a starting point rather than built from scratch:

• Welcome Journey — triggers on signup; sends a welcome email, waits 48 hours, then waits up to 72 hours for a purchase event before sending a follow-up SMS.
• Abandoned Cart Recovery — triggers on add_to_cart; waits 60 minutes, then A/B splits 50/50 between an email and an SMS reminder.
• Win-back Lapsed Customers — triggers on entering a "lapsed" segment; sends a discount email, waits up to 168 hours (7 days) for a purchase, then sends a last-chance SMS.

curl https://api.wezend.com/v1/journeys/templates \
  -H "Authorization: Bearer $WEZEND_JWT"

Test before you launch

Every journey supports .../test-enroll to run one real profile through the graph and see exactly which path it takes, before you .../activate it for everyone matching the trigger.