Flows that reach
the right person
Build lifecycle journeys on a visual canvas. Enter people from any event or segment, split on what you know about them, and send on the channel they prefer.
A canvas
that stays structured
Journeys read top to bottom, like the logic they encode. Every step is explicit, every branch is readable, and publishing is a deliberate act with versions you can roll back.
Start from any signal
Track events, form submissions, segment entry or a schedule. Anything your sources emit can open a journey for the right person.
Branches, waits, sends
Condition splits on traits and behavior, timed and event-based waits, and message steps that render your own templates per channel.
Consent and quiet hours
Delivery respects each profile’s consent and your quiet-hour windows by default. The journey decides what; the guardrails decide whether and when.
Every message,
in their words
Merge any trait or event into your templates: first name, plan, the last thing they looked at. Preview exactly what each person sees, and catch missing values before they reach a real inbox.
Amara’s flow is an illustrative walkthrough, not a customer case study.
Every run,
on the record
Activity and version history live inside the builder. See who entered, what each step did, and which published version made the call. When something looks off, you read the run, not the logs.
How versioning works
origamyBuilt for the people
who own the lifecycle
Journeys is for the marketer who is tired of filing a ticket to send a message, and the engineer who is tired of the tickets. Design the flow, see exactly who it touched, and change it without a deploy.
Build your first journey
in an afternoon
Runs in our cloud or your VPC