Rheo documentation
User GuideEngage

Automations

Build branching workflows with email, webhook, and push steps, plus delays, branches, waits, and A/B splits.

What an automation is

An Automation is a branching workflow. People enter from an audience, an app event, or a manual enrollment, then move through delays, messages, branches, waits, and exits. Sequences as a separate product object are retired. Use Automations instead.

Open Engage → Automations.

Grow+ (Advanced Engage): marketing topics, quiet hours deferral, canvas A/B split, and conversion goals in Settings require Grow or above. Indie can still run basic automations. See Plans & entitlements.

Canvas steps

StepWhat it does
EntryHow people start: audience, SDK event, or manual / API enrollment
DelayWait before the next step. A delay of 0 is No wait
EmailSend an email (blank or from an email template). Insert content blocks as needed
WebhookPOST a JSON payload (blank or from a webhook template)
PushNotify registered devices (blank or from a push template)
BranchSplit by attributes or rules. Paths can include Is in segment. Unmatched people follow Everyone else
Wait untilContinue when a chosen event happens (or follow the timeout path)
A/B splitGrow+. Split contacts by percentage across arms
ExitEnd of the automation

Email, webhook, and push steps use the same composers and merge tags as broadcasts. Use a template copies a starter of that channel. Send test on a step previews that step's draft and does not enroll the contact.

Each send step is checked on its own:

  • Email needs an address, granted marketing consent, and a clear suppression check. It also follows the app frequency cap unless the automation is exempt.
  • Webhook needs granted marketing consent and a complete endpoint. It can send when the customer has no email address, unless topics mode is on.
  • Push needs granted marketing consent and an active device subscription. It does not use the email frequency cap.

Denied consent ends the journey at that send step.

Entry

Open the Entry step and choose Edit entry. The Entry page has four sections:

SectionWhat you set
WhenOnce at activation, daily or weekly in the app default timezone, up to five events, or API enrollment
WhoAll subscribed customers, or segments, plus exclusions and extra filters. Checked for every schedule
Re-enrollmentOnce ever, once while not already in it, or every time with a cooldown. Optional lifetime limit
ExitException events that end the enrollment immediately, including during a delay

A later publish does not enroll the once schedule again. Use Enroll matching customers on the Entry page for another snapshot. A recurring schedule enrolls on each cadence from the latest published version.

An event trigger picks a source:

SourceWhat it matches
AnalyticslogEvent, screen views, and web page views already on the Analytics chart. Session start, first open, and first visit are not offered as triggers. A screen or page needs the screen name or path.
ConvertFlow events such as a completion or a surface outcome.
Emailengage_email_opened once per send, and engage_email_clicked once per send per link.

The same groups are available on a segment rule and on Wait until. Someone has to already be a Customer with marketing consent granted when the event matches. A later consent grant does not replay the earlier event. Unsubscribe ends journeys that are still active. It is not itself a trigger. A filter can require a property to equal or contain a value. It cannot yet require a property to differ, so a journey cannot exclude its own email by automation id.

When marketing topics mode is on, assign one topic in Settings so every send respects topic consent. Topic checks on email sends also require an email address on the customer.

Lifecycle

ActionWhat happens
ActivatePublishes the first version and starts enrollment
Publish changesAfter Activate, further edits stay in the draft until you publish. Publishing creates a new version
PauseStops new people from entering
ResumeOpens entry again
ArchiveRetires an automation that is draft, paused, or completed

People already in an automation stay on the version they entered. New entrants use the latest published version after you publish.

Published vN opens version history. Restoring a version copies it into the draft and does not publish by itself.

Analytics shows lifetime totals for the published version.

Re-enrollment and optional lifetime entry limit are on the Entry page. Topic (Grow+), frequency cap, conversion goal (Grow+), and internal notes are in Settings. The conversion goal measures a result. It does not end the enrollment. Frequency cap exemption applies to email only. When the goal is a purchase, revenue is net webhook gross in that window, including renewals and refunds.

From the terminal

Create, publish, pause, resume, and enroll people with rheo engage automations in the CLI. Publishing a new version follows the same draft-until-publish rule as the canvas.

  • Set up Engage — Consent, topics, frequency cap, push credentials
  • Broadcasts — One-shot sends and the composers
  • Customers — Segments used by Entry and Branch
  • CLI — rheo engage automations