1. order.completedCustom event
  2. Wait 1 dayWait
  3. 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.

Quiet for 30 daysTrigger

Segment · 12,408 contacts

Send emailAction

We miss you: 20% off this week

It's been a while. Here's 20% off anything in the store.

Send SMSAction

Still there? Your 20% off at Marlow ends tonight.

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.

“Build a 3-email onboarding for new trials, spaced over a week.”
  1. Reads the block catalog
  2. Drafts the graph
  3. Validates it
  4. 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.

cart.abandonedPOST /v1/events
Call webhookacme.com/hooks200

The blocks

22 blocks.

The same catalog the builder and Unit use.

Starts when…10
  • 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.
Then do…6
  • 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).
And decide…6
  • 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?

Automations are in early access behind a launch flag: the builder, the run engine, Unit's authoring tools, and a beta API are built and running for early-access workspaces. Join the waitlist from this page and we'll turn it on for you as we widen the rollout. Everything else on the platform is available now: transactional sending, scheduled campaigns, contacts, topics, templates, inbound, and webhooks.

What can start an automation?

Your own backend events (POST /v1/events with a bare name like cart.abandoned), contact lifecycle (created, updated, joins or leaves a segment, subscribes or unsubscribes from a topic), and email activity (opened, clicked, bounced, replied, and more). Each automation has one trigger with an optional enrollment condition.

Will it send through my existing templates and domains?

Yes. A send block renders a published template and goes through the same sending gate as the API and campaigns: verified domain, suppression list, quota, tracking, webhooks. There is no second sending path. You choose per block whether an email is marketing (honors unsubscribe and topics, counts toward the daily cap) or transactional (always delivers).

How does the AI part work?

Ask Unit in the dashboard describes what it's building from the same block catalog the engine runs, drafts the graph in your workspace, validates it (wiring, cycles, consent, missing data), and shows you the result. Going live is always your click — Unit never publishes on its own. When the beta API opens, external agents get the same operations over MCP.

What happens when something goes wrong?

Every run is a ledger: each block records what it did, what it skipped and why, or what failed and where. A deleted template pauses dependent automations before a single run breaks; a broken block can trip a circuit breaker that pauses the automation for review. Pausing freezes runs in place and resuming continues them — nothing is lost mid-journey.

Can I build drips without automations in the meantime?

Yes: call POST /api/v1/email when your app decides someone should hear from you, with scheduled_at up to 90 days ahead, and subscribe a webhook to delivery and engagement events so your own job runner can decide the next step. Automations move that logic into a graph you can see and hand to Unit.

Tell us the first journey you'd run.

Early access is opening workspace by workspace.

Join the waitlist