Emails that go out on their own when something happens
Somebody subscribes, reaches checkout, places an order. The action starts the automation and it runs on its own from there — you decide what it sends and how long it waits between steps.
A welcome automation in the editor: a two-day wait goes in, then an email chosen from your saved designs. Shown with a sample store.
A person’s action starts it, not a date
Subscribing, reaching checkout, placing an order, submitting one of your forms. You choose which one an automation listens for, and everyone who does that thing from then on begins a run of their own.
Waiting is a step like any other
A run moves one step at a time — wait two days, send this, wait a week, send that. You can add a step to a live automation without stopping the people already partway through it.
It sends through the same checks a campaign does
One place decides whether an email may go to a person, and every automation goes through it. Consent is read again in the moment before the message is handed over, not once at the start of the run.
Whatever started it, the products are theirs
A product block in any automation email can fill from that person’s own history on your store: what they looked at, added to their cart or purchased before. A shipping confirmation can show what they browsed and have not purchased since, beside the news that their order is on its way.
How it works
1. Choose what starts it
The thing a person does — subscribing, reaching checkout, placing an order, submitting a form — and, if you want, which people count.
2. Write the steps
Emails and the waits between them, in the order you want them, splitting down different paths where you need to. Each email is an ordinary email you built in the editor.
3. Publish it
From then on, everyone who does that thing starts a run. What each run has sent, and what it refused to send, is on the Analytics screens.