iemails
Pricing
Log inGet started
Get started
AutomationsTriggered by your events

Emails that
send themselves

Turn what happens in your product into perfectly timed emails. Send an event, and a flow you designed on a visual canvas takes it from there — waiting, branching and sending on its own.

Start sending free Read the guide
Visual flow builderWait, branch and delayEvery run logged
Automations /Abandoned cartLive
Triggercart.abandonedEvent received
Wait for eventorder.completedTime out after 2 hours
Event received
ExitPurchasedNothing more to send
Timed out
Send emailYour cart is waitingTemplate · cart-reminder
Delay1 dayThen continue
Send email10% off, today onlyTemplate · cart-discount
Run logWaiting for event
POST /events { "name": "cart.abandoned", "contact": "[email protected]", "properties": { "total": 128 } }
Your eventsStart flows from anything your app reports with one API call.
Wait for anythingPause until an event arrives, with a timeout for when it does not.
Branch on dataRoute people by plan, country, cart size or any property.
Every run loggedSee each step a contact took, with its input and output.
Custom events

Trigger flows from
what your app knows

Your product already knows when someone signs up, abandons a cart or misses a payment. Send that moment to iemails as an event, and every automation listening for it starts on its own.

Or start fromEvent receivedContact createdContact updatedEmail openedEmail clicked
track.tsPOST /events
1await mail.events.send({
2 name: 'user.signed_up',
3 contact: '[email protected]',
4 properties: {
5 plan: 'free',
6 source: 'google',
7 },
8});
202 RecordedStarted “Welcome series” for [email protected]
Control the flow

Orchestrate
every step

Decide when each email goes out, who gets it and what happens next. Drag steps onto the canvas, connect them, and the flow runs itself.

Wait for eventStep settings
Event
email.sent
Time out after
7 days
If it arrives
Continue
If it times out
Send “Need a hand?”
Events from POST /events resume any run waiting for them.
Observability

See every run,
step by step

Every time a flow runs for a contact, we keep the record: what triggered it, which path it took, what each step received and returned, and where it stopped.

app.iemails.co/automations/abandoned-cart/runs
Runs2,608 this month
[email protected]Completed
Trigger payload
{ "event": "cart.abandoned", "items": 3, "total": 128 }
Steps
  1. Trigger · cart.abandonedEvent received14:02:11
  2. Wait for event · order.completedTimed out after 2 h16:02:11
  3. Send email · Your cart is waitingem_4Lm8Ra2cT · 212 ms16:02:12
  4. Delay · 1 dayResumed on scheduleThu 16:02
  5. Send email · 10% off, today onlyem_9Pq1Vb7nK · 188 msThu 16:02
Quillstack
“Our onboarding emails used to live in a cron job nobody wanted to touch. Now it is one event and a flow the whole team can read — and the run log tells us exactly who got what.”
MO
Marcus Osei
Head of Growth, Quillstack
Easy to start

Start from a
ready-made flow

Pick a starting point, swap in your own emails and events, and publish. Each template is a normal automation you can change any way you like.

Welcome series

Greet new sign-ups, then follow up with tips while they settle in.

  1. Triggeruser.signed_up
  2. Delay10 minutes
  3. Send emailWelcome
  4. Delay3 days
  5. Send emailTips for week one
Use this template

Abandoned cart

Remind shoppers about the cart they left, and stop when they buy.

  1. Triggercart.abandoned
  2. Wait for eventorder.completed · 2 h
  3. Send emailYour cart is waiting
  4. Delay1 day
  5. Send email10% off
Use this template

Trial conversion

Show the value of upgrading in the last days of a trial.

  1. Triggertrial.ending
  2. Conditionplan is free
  3. Send emailThree days left
  4. Delay2 days
  5. Send emailLast day
Use this template
Built for production

Test it first.
Then forget about it.

No queues to host, no workers to babysit. Fire a test event, watch it walk the flow, publish — and the runs take care of themselves.

  • Runs pause and resume on our servers, so a deploy or a restart on your side never loses a step.
  • Fire a test event from the builder and watch it walk the flow before you publish.
  • Automation emails use the same delivery pipeline as everything else, so unsubscribes and suppressions are respected.
Get startedSee plans
Send a test eventDraft
Event
user.signed_up
Contact
[email protected]
Properties
1{
2 "plan": "free",
3 "source": "google"
4}
Run started · Welcome series · step 2 of 5
FAQ

Questions
about Automations

Not sure how to model your flow? Tell us what you want to send and when, and an engineer will help you sketch it.

Talk to an engineer

A custom event your app sends with POST /events, a contact being created or updated, or a contact opening or clicking an email. Each automation has one trigger, and you can have as many automations as you like.

Call POST /events (or mail.events.send in the SDK) with an event name, the contact’s id or email address, and any properties you want to use later. Every automation listening for that name starts or resumes for that contact.

Send email, time delay (minutes, hours or days), wait for event with an optional timeout, conditional paths, and exit. Combine them in any order on the visual canvas.

Yes. Contact fields, contact properties and the trigger event’s properties are all available as template variables, so {{first_name}} and {{cart_url}} just work.

A condition checks contact properties or event data with operators like is, contains, greater than or is set, grouped as “all of” or “any of”. The run follows the yes or no path. Conditions are data, never code, so nothing in them can execute.

Yes. Send a test event from the builder with your own properties and watch the run step by step. Publish only when the flow does what you expect.

The run stops at that step and is marked failed, with the error in its log, so you can see exactly what went wrong. Other runs keep going.

Automations are part of the Scale plan, alongside segments, topics and A/B subject tests. You can explore the builder on any plan.

Your first automation
is one event away

Send an event from your app, drop a few steps on the canvas and publish. Your emails go out at the right moment, every time.

Sign up for free See pricing
iemails

Email infrastructure for teams who would rather read a trace than a support ticket.

Keizersgracht 241
1016 EA Amsterdam, NL

All systems operational·Status
Features
Email APISMTP relayAutomationsAudiencesBroadcastsInboundTemplatesWebhooksDedicated IPs
Resources
ChangelogPricingEnterpriseSecuritySOC 2GDPRBrand
Company
AboutBlogCareersCustomersPhilosophy
Help
SupportStatusMigrateKnowledge baseLegal
Community
EventsOpen sourceInsidersWallpapers
SOC 2 Type IIGDPR readyISO 2700199.99% uptime SLA
© 2026 iemails, Inc. Built in Amsterdam and Bengaluru.
PrivacyTermsDPASecurityCookies