Automations
Event-triggered email workflows. Fire any event from your app and Sendry runs an automation per contact: multi-step sequences with sends, waits, conditional branches, and A/B splits. One event, an entire journey.
Why use Sendry Automations
- Compose welcome series, drips, win-backs, and onboarding from a single visual flow.
- Triggered the moment your event arrives, no polling, no cron.
- Branch on contact properties or event payload to personalize the path.
- Wait steps support any duration: minutes, days, or weeks.
- Re-entry policies prevent spam: once-per-contact, cooldown, or always re-fire.
- Also triggers from segment membership changes, perfect for behavioral journeys.
Capabilities
- Trigger automations from any event in your app via POST /v1/events.
- Multi-step flows with sends, waits, branches, and A/B splits.
- Re-entry policies: once_per_contact, cooldown (min seconds), or always.
- Branch on contact properties or fields from the event payload.
- A/B split traffic between two variants to test subject lines or content.
- Trigger on contact_added_to_segment for behavioral journeys.
- Per-automation stats: total runs, active runs, completed, failed.
- Manage and inspect every run from the dashboard at /automations.
Step types
Compose flows from four primitives. Chain them however you like.
send_email
Send a templated email to the contact
wait
Pause the run for any duration before continuing
branch
Conditional split on contact property or event payload
ab_split
Split traffic between two variants for testing
Re-entry policies
Decide what happens when the same contact triggers an automation more than once.
once_per_contact
Each contact enters the automation a single time. Re-triggers are ignored.
cooldown
Re-trigger only after a minimum number of seconds since the last run.
always
Every matching event starts a new run, no matter how recent the last one was.
Common use cases
Anything that starts with an event ends with the right email.
Welcome drip series
user.signed_up → email 1 → wait 2d → email 2 → wait 5d → email 3
Cart abandonment
cart.abandoned → wait 1h → reminder → wait 24h → discount offer
Post-purchase follow-up
order.placed → receipt → wait 7d → review request
Onboarding by behavior
Branch by feature_used events to teach the next best thing
Re-engagement / win-back
contact_added_to_segment 'inactive_30d' → win-back flow
A/B subject testing
ab_split → variant A or B → measure opens & clicks per branch
Fire an event from your app
Any automation listening for user.signed_up kicks off the moment this request lands.
curl -X POST https://api.sendry.online/v1/events \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"user.signed_up","contact_email":"jane@acme.com","properties":{"plan":"pro"}}'Properties are available in branch conditions. For example, event.plan == "pro" sends a different welcome path than the free tier.
Total runs
Lifetime triggers per automation
Active
Runs in flight right now
Completed
Reached the end of the flow
Failed
Errored mid-run with reason
Ready to wire up your first automation?
Automations are available on Pro, Business, and Enterprise plans. Build flows in minutes from the dashboard.