Turn product events into lifecycle email flows. Launch only when the path is ready.
Start from signup, trial, checkout, renewal, or your own event. Your agent builds the delays, branches, exits, and messages; Send & Retain runs a separate path for every contact.
✓Every new flow starts paused.
A journey you can inspect
When contact.created fires
No filter — every event enrolls.
Welcome email
Send
2 days
Wait
Activated?
Branch
[ 01 / 04 ]Control
Every decision stays visible.
Start from a product event
Enrol a contact when signup, checkout, renewal, or your own event occurs.
Branch on current data
Route each run from event properties and contact attributes.
Launch deliberately
Every new flow starts paused and needs an explicit confirmation to go live.
[ 02 / 04 ]Why it holds up
A canvas is not the runtime.
The visible journey must match the machinery that enrols, waits, branches, exits, and sends for every contact.
- Stable step identifiers protect contacts already moving through a live flow.
- Preflight checks find unpublished templates and invalid branches before launch.
- Every new flow remains paused until an operator enables it.
A journey you can inspect
When contact.created fires
No filter — every event enrolls.
Welcome email
Send
2 days
Wait
Activated?
Branch
[ 03 / 04 ]From draft to live
Inspect the whole path before it sends.
Choose the trigger
Name the event and the exact properties the flow expects.
Build the path
Add messages, delays, branches, exits, and send windows.
Test the messages
Render every template and send it to a real inbox.
Enable the flow
Run pre-launch checks, then confirm the go-live decision.
What keeps running
- Per-contact runs and event history
- Timezone-aware send windows
- Delays, branches, exits, and A/B splits
- Suppression and send controls checked at dispatch
Questions people ask us
Build one complete journey around a real product event.
Start with signup, trial, or win-back and inspect the full path before it sends.