Journeys that survive
contact with reality.
17 step types, 500 nodes, durable execution — and a published version behind every enrollment.
Most automation breaks quietly.
A three-step drip is easy. What is hard is the flow that has been running for eight months: a step that failed once and dropped a contact, a definition someone edited mid-flight, a re-entry rule nobody remembers writing. The failure mode is silence.
Workflows publish to immutable, hash-verified versions, and enrollments run against a known definition. Steps execute on leased workers with retries and PII-safe error handling, and every step run is recorded — including the ones that failed.
Workflows, in detail.
17 step types
Trigger, condition, delay, wait-until, send email, webhook, add tag, remove tag, update field, add to list, remove from list, notify, branch, split test, goal, rate limit, and exit.
Room for real journeys
Up to 500 nodes, 1,000 edges, and 50 triggers in a single definition — a full lifecycle program fits in one flow.
Durable execution
Steps run on leased workers with retries and PII-safe error handling. A transient failure is retried and recorded, never silently dropped.
Versioned definitions
Publishing snapshots an immutable, hash-verified version. Editing the draft does not change what in-flight enrollments are executing.
Goals and re-entry control
Exit enrollments the moment a goal is achieved, and govern re-entry with cooldowns, per-contact limits, and enrollment windows.
Consent-bound
Send steps respect subscription topics, suppressions, and frequency caps. Automation is never a way around permission.
Execution, observed.
Enrollments and step runs are queryable records, which is what makes a long-running flow debuggable.
- Enrollment
- Workflow, contact, status, enrolled-at, completed-at
- Step run
- Enrollment, step key, status, scheduled-at, completed-at
- Limits
- 500 nodes · 1,000 edges · 50 triggers per definition
- Publishing
- Immutable, hash-verified version snapshot
- Failure handling
- Leased workers, retries, PII-safe error capture
- Re-entry
- Cooldowns, per-contact limits, and enrollment windows
Bring your provider.
Keep your brands distinct.
Start today.
Set up your first workspace, connect a provider, and publish a workflow — free, in test mode, before you pay a thing.