Workflows that run when your users act.
Build time-based, event-driven, and condition-based automations on top of your own provider stack. Every step respects quota rules, suppression, and compliance — the same engine that powers manual sends.
- Delayed & scheduled
- TimeDelayed & scheduled
- API & webhook triggers
- EventAPI & webhook triggers
- Conditions & branches
- LogicConditions & branches
- Per workspace & domain
- ScopedPer workspace & domain
Three building blocks, every workflow you need.
Combine time, events, and conditions to build onboarding sequences, lifecycle workflows, and outbound cadences without bolt-on tools.
Time-based
Send after fixed delays, on specific dates, or at recurring intervals. Ideal for onboarding drips and follow-up cadences.
- Day-1 welcome
- Day-3 feature intro
- Day-7 activation nudge
- Quarterly re-engagement
Event-based
Trigger on form submission, list join, API call, or webhook. Real-time workflows tied to what happens in your app.
- Signup complete
- Trial started
- API event received
- Form submitted
Condition-based
Branch on tags, segments, opens, clicks, and custom properties. Subscribers follow the path that fits their state.
- If opened last email
- If tag = 'paid'
- If segment = agency
- If custom field set
What a lifecycle workflow looks like in Mailers.io.
Each step is visible, measurable, and governed by the same routing and suppression rules as the rest of your platform.
- Trigger · Form submissionA prospect submits a signup form. The API webhook fires the automation immediately.
- Step 1 · Wait 15 minutesShort delay so downstream account-provisioning events can complete before the first email.
- Step 2 · Welcome emailDispatched through the routing engine. Quota-aware provider selection, suppression check, full event tracking.
- Step 3 · Branch on openedIf opened within 48h, move to onboarding path. If not, move to re-engagement path.
- Step 4a · Onboarding path (3 emails)Feature walkthrough cadence over 7 days. Each step respects suppression and quota caps.
- Step 4b · Re-engagement path (1 email)Lighter touch for unengaged contacts. Exits automation if still no engagement.
- Exit · Goal reachedSubscriber hits the success event (activated). The automation completes and logs the outcome.
Automations that actually run in production.
Segment entry rules
Gate automation entry by list, tag, segment, or property. Only the right subscribers get in.
API + webhook triggers
Fire automations from your product in real time. No manual imports needed.
Business-hour delays
Constrain sending to working hours and days to respect recipient time zones.
Goals & exits
Define success events so subscribers exit cleanly when they convert or complete a workflow.
Suppression-safe
Every step checks global unsubscribe, bounce, complaint, and DNC lists before dispatch.
Branching logic
Multi-path branches on conditions, with re-merge points so workflows stay readable at scale.
What teams ask before they wire it in.
Turn user events into outbound workflows that actually ship.
Build once, route automatically, observe every step. Automations inherit your provider pool, your quotas, and your compliance controls.