Skip to main content
An automation is a flow that watches your data and messages contacts when something happens — a row changes, a trial ends, a payment fails, a contact enters a segment. Because Minimo reads your database directly, the triggers are your real application state, not a copy.

Build an automation from a template and publish it, narrated. Press play to follow along.

What you can build

  • Onboarding — welcome a new signup, then follow up over the next days if they haven’t finished setup.
  • Trial conversion — nudge trial users as the trial-end date approaches; stop when they upgrade.
  • Win-back — re-engage contacts who went inactive.
  • Operational — receipts, renewal reminders, payment-failed dunning.
Each step can send email, WhatsApp or SMS, wait, branch on a condition, or check a goal (did the contact do the thing you wanted?).

Build a flow

1

Start from a template or scratch

In Automations → Create new automation, name it and build your own, or pick a pre-built template (Welcome Series, Re-engagement, Onboarding Drip) to start from a working flow.
The Create new automation dialog with pre-built templates
2

Shape the flow

In the visual builder, set the trigger (a new contact, a field that changed — like plan or trial_ends_at — a tag added or removed, a list subscription, an email opened or clicked, or a new row in one of your tables), then add message steps, waits and conditions.
The automation builder: trigger, wait, then send an email
3

Edit a step

Click any step to edit it. A message step opens its settings and a preview of the email that will go out.
4

Set a goal

Define the outcome (e.g. “plan = paid”). Contacts who reach the goal exit the flow, and you can measure conversion against it.
5

Save and publish

Activate the automation with Save and publish. It goes live and runs continuously against your real data.
A published, active automation with the email step selected

Reminders before a date

To message a contact a set time before (or after) one of their dates, such as 6 hours and 1 hour before an event they registered to, use a wait Based on a contact date. See Reminders before a date.

Already sending these messages from code?

If your application already sends reminders or follow-ups from its own backend (a cron job, a queue worker), consider moving that flow into a Minimo automation and turning the code path off:
  • Edit without deploying — copy, timing and steps change in the visual builder, not in a release.
  • See what happens — every step reports delivered / opened / clicked, and the automation reports conversions against its goal. A hardcoded sender is a black box in comparison.
  • Pause in one click — stop or resume the whole flow instantly, no rollback.
  • One home for lifecycle — contacts, consent, opt-outs and message history live in one place.
Run one sender at a time. When the automation goes live, disable the code path that sent the same message — otherwise contacts receive both.
Describe the flow in one sentence and let Mo build the whole automation — trigger, steps and emails — then review it in the builder. See Build with Mo.

Measure it

Each automation reports how many contacts entered, where they are, and goal conversion, per node. Your connected agent can answer questions like “how is the trial-conversion flow performing?” — see Connect your agent.
Automations rely on the fields Minimo can see. Make sure the data you trigger on (dates, plan, status) is synced — see Data sync.