Build automations

Automations are durable profile workflows. A published version defines entry, audience, re-entry, timing, steps, target apps, and conversion attribution.

Engage automation inventory with lifecycle, trigger, audience, entry, completion, conversion, and failure metrics — The automation inventory exposes both lifecycle state and the health of running journeys.

Entry triggers

Trigger	Input
Event	tracked event name and context
Screen view	tracked logical screen name
Audience entry	segment membership transition
API	server call with authored automation key and JSON context

An active automation evaluates its audience and target apps at entry. No event-triggered automation can run until the corresponding event is tracked.

Re-entry

Choose never, after exit, or after a configured delay. Re-entry is evaluated per profile and published automation. API retries do not bypass this policy.

Steps

Step	Behavior
Wait	schedule the run after minutes, hours, or days
Condition	continue or exit based on profile/context expression
Push	enqueue a push using current workflow context
In-app	create profile/app-scoped content with availability and expiry
Webhook	call an external POST/PUT endpoint with retry-safe execution
Update profile	set, remove, or increment an attribute
Exit	complete the run explicitly

Quiet hours can use profile or environment timezone. Start/end dates bound entry. Conversion goals match an event within a configured window.

Fullscreen Engage automation node editor with searchable node library, typed graph connections, canvas controls, minimap, and selected-node configuration — Fullscreen mode gives complex journeys room for branching while keeping the node library and validation-aware configuration inspector available.

Draft, simulate, publish

Draft edits create versions. Use simulation with a profile and context before publication; the timeline reports whether each step would wait, execute, or exit and whether the profile is ineligible, exits, or completes.

Publishing freezes the workflow version for new runs. Existing runs retain their automation version so a later edit does not rewrite a journey in progress.

Engage automation editor with setup, entry, audience, journey, review, and app targeting steps — Automation authoring separates entry and re-entry policy from audience eligibility and the versioned execution graph.

Runtime reliability

Runs have pending, waiting, processing, completed, exited, or failed status. Workers claim due runs, renew claims, and record each step execution as completed, waiting, failed, or skipped. Use run and step diagnostics rather than manually replaying a whole workflow.

Engage automation journey analytics graph with node entries, waits, failures, exits, delivery guardrails, and conversion metrics — The immutable execution graph is reused for node-level analytics, branch traversal, simulation, and run diagnostics.

API entry

For an API-triggered automation, use the environment access key and the automation’s authored API key. See Trigger automations.