Email automations triggered by product events
Signup, trial, checkout, or your own event starts the automation. Your agent builds the steps, and every automation starts paused.
✓Free to start. Unlimited contacts on every tier.
A run you can inspect
When contact.created fires
No filter — every event enrolls.
Welcome email
Send
2 days
Wait
Activated?
Branch
[ 01 / 05 ]Build
How do I build an email automation?
Send an event from your app, then let your agent build the automation around it.
Send the event from your app
Any event name works. The automation listening for it enrols the contact.
Terminalcurl -X POST https://sendandretain.com/api/v1/events \ -H "Authorization: Bearer $AEM_KEY" \ -H "Content-Type: application/json" \ -d '{ "email": "[email protected]", "name": "signup" }'Build the automation
Ask your agent, or use the dashboard. Add emails, delays, branches, and exits. It's created paused.
Test every email
Render each template and send it to your own inbox.
Turn it on
The pre-launch check catches unpublished templates and broken branches. Then you confirm.
[ 02 / 05 ]Building blocks
What can an email automation do?
Start on an event
A product event, a scheduled sweep, or someone entering a segment.
Wait
Delays between steps, and send windows in each contact's time zone.
Branch
Route each person by event properties, attributes, or engagement.
Exit
Stop the automation when someone converts, so they don't get stale email.
A/B test
Split a step between template versions and compare results. On Pro and Scale.
Set priority
Make an automation exclusive so overlapping triggers don't send two emails at once.
[ 03 / 05 ]Safety
What stops an automation from sending the wrong email?
Every automation starts paused, and the checks that matter run again right before each email sends.
- Turning an automation on needs your explicit confirmation, whoever built it.
- The pre-launch check finds unpublished templates and broken branches first.
- Adding steps to a live automation never moves people already in it. Reordering needs a pause.
- Unsubscribes, bounces, the pause switch, and the daily cap are checked right before each send.
A run you can inspect
When contact.created fires
No filter — every event enrolls.
Welcome email
Send
2 days
Wait
Activated?
Branch
[ 04 / 05 ]Example prompts
What automations can your agent build?
Describe the automation in plain English. It builds it paused and shows you each email.
Welcome
“Build a welcome automation on the signup event, with a getting-started nudge three days later.”
Exit
“Add an exit to the welcome automation when the contact sends project_created.”
Branch
“After the first trial email, branch on whether they've connected a data source.”
Check
“Run the pre-launch check on every paused automation and tell me what's blocking each one.”
Questions people ask us
Build one automation around a real product event.
Start with signup, trial, or win-back. Nothing sends until you turn it on.