- order.completedCustom event
- Wait 1 dayWait
- How was your order?Send email
Agent workflows
The jobs that used to take a sprint.
Start with an event or just ask. Approve once, and it runs on every channel.
Win back customers who've gone quiet. Email them, then text whoever doesn't open.
Segment · 12,408 contacts
We miss you: 20% off this week
It's been a while. Here's 20% off anything in the store.
AI-native
You approve it. Then it runs.
Unit drafts the graph. Nothing goes live until you publish.
Drafts stay drafts
Publish, resume, and cancel all ask first.
It checks its own work
Wiring, consent, and missing data come back as something it can fix.
Ask why a run skipped
Unit reads the ledger and names the block.
- Reads the block catalog
- Drafts the graph
- Validates it
- Asks you to publishPublish
Fits your stack
Your events in. Your systems out.
Your app posts an event. The journey sends, or calls your API.
POST /v1/events
A name like cart.abandoned, with an idempotency key.
Same sending gate
Your templates, domains, and suppression list.
Signed webhooks out
A block can POST the run back to you.
The blocks
22 blocks.
The same catalog the builder and Unit use.
- Contact createdStarts when a new contact is added to the workspace — including one added automatically because a marketing email was sent to a new address.
- Contact updatedStarts when a contact's fields change (optionally only specific fields).
- Joined segmentStarts when a contact enters the segment.
- Left segmentStarts when a contact leaves the segment.
- Subscribed to topicStarts when a contact subscribes to the topic.
- Unsubscribed from topicStarts when a contact unsubscribes from the topic.
- Email activityStarts on email events (opened, clicked, bounced, …), optionally scoped to a campaign or template.
- Text receivedStarts when someone texts one of your numbers, optionally only for a keyword (JOIN) or text that contains a word. STOP and HELP texts never start a run.
- Custom eventStarts when your backend sends a named event via POST /v1/events (e.g. cart.updated).
- Manual enrollmentStarts only when explicitly enrolled via the UI, API, or Unit AI.
- Send emailRenders a template and sends it to the run's contact (or a fixed address), through the full sending gate.
- Send SMSSends a text message to the run's contact through the full SMS send path (consent, suppression, sender reach, review). Marketing needs prior consent on record; without it the contact is skipped.
- Update contactSets or clears contact fields (built-in and custom).
- Change topic subscriptionSubscribes or unsubscribes the contact from a topic.
- Add/remove from segmentAdds or removes the contact from a static segment.
- Call webhookSends a signed POST with the run context to your URL (SSRF-guarded, retried).
- WaitPauses the run for a fixed duration (hours, days, weeks).
- Wait untilPauses until a day and time comes round: the next Monday 09:00, the next 18:00, or one fixed date, in a set time zone or each contact's own.
- Wait for event2 pathsPauses until a matching event arrives for this contact, or the timeout elapses.
- If / else2 pathsRoutes the run by a condition on contact, event, or step data.
- Multi-branchn pathsRoutes down the first branch whose condition matches, else the fallback.
- Exitends the runEnds the run immediately (with an optional reason).
Guardrails
It won't loop or double-send.
No loops
A journey only runs forward.
Consent on the send
Marketing honors unsubscribe. Transactional always delivers.
One cap per person
Extra marketing sends that day are skipped.
Pause holds the run
Resume continues from the same step.
Runs keep their version
Edits apply to people who start after you publish.
Re-entry is a setting
Once, on a timer, or every time.
Questions
Common questions
Can I use automations today?
What can start an automation?
Will it send through my existing templates and domains?
How does the AI part work?
What happens when something goes wrong?
Can I build drips without automations in the meantime?
Tell us the first journey you'd run.
Early access is opening workspace by workspace.
Join the waitlist