Let an AI agent run your email without accidental sends

Build it in Mimeo

1 Save a checkpoint before you edit a live flow

A change to a live flow applies as soon as you save it, so keep a version to return to.

On the flow's page, open Flow actions (the ⋯ button), choose Save a checkpoint…, give it a name and click Save checkpoint.

The checkpoint appears under the flow's Versions tab.

2 Change the step and read its checks

Mimeo checks a flow every time it changes and says what looks wrong on the flow's page.

Click the step's edit icon, change the field (here Tag, from lead-magnet to lead-magnet-guide) and click Save step.

After saving, the flow page flagged the step: the tag "doesn't exist yet. It will be created the first time this step runs — check the spelling." A typo would look exactly like this.

3 Rehearse the flow

A rehearsal shows what would happen to one real person if the flow's event arrived now.

Click Rehearse it (the play icon above the canvas). In the Rehearsal panel, pick a Person, check the Event, and click Run it.

Every check shows the value it saw, and every action is a "would". Nothing is written: in the first test, sends, queue, runs, tags and events matched before and after.

4 Roll back if it's wrong

A checkpoint is only useful if you know where the undo is.

Open the Versions tab, click ⋯ on the checkpoint and choose Roll back to it…. Mimeo re-checks the old definition before it goes live again.

5 Put a guard on emails that must never collide

A guard checks every email as it is about to send, so it catches what no review of one flow can see.

Open Automation → Guards, click New guard, and fill in When the person…, …then and Over which emails. This one keeps sales emails from people who already bought:

Skip & continue drops that one email and the person carries on. In the first test, a guard like this dropped a tagged person's email while an untagged person's sent.

6 Send a test, not a send

A test send delivers one email to one address, without mailing your list.

Open the email under Content, click Send test, choose an address under Send to, and click Send test.

A test moves nobody's sent status or sequence position, and a new address is added to People. Accepted by the provider doesn't mean delivered. Suppression still applies:

7 Keep Make it live your click

A new flow can't mail anyone until someone makes it live.

New flows start as a Draft. When the checks pass, click Make it live; it asks once more: "People will start entering it on matching events."

A flow with errors can't be made live at all.

Build it with your agent

1 Write your approval rules into the repo

Your agent reads the repo's instructions every session, so rules written there apply every time.

The rules are instructions to the agent, not settings in Mimeo; see the limits.

2 Ask for the change and read the diff first

A diff and a rehearsal show what a change will do before it reaches anyone.

A typo would trigger the same warning. Nothing on your Mimeo changed yet.

3 Approve the push

A push runs diff, validate, rehearse and apply in order and stops at the first that fails, so a bad change never half-applies.

When a check fails, the push is refused and nothing changes: in the first test, a flow pointed at a missing email was refused and kept its real one. To undo a pushed flow, its Versions tab in your Mimeo rolls it back.

4 Rehearse the flow

A rehearsal shows what would happen to one real person if the flow's event arrived now.

The rehearsal also caught a trigger that real events may never match, the kind of mistake that sends nothing at all.

5 Put a guard on emails that must never collide

A guard checks every email as it is about to send, so it catches what no review of one flow can see.

After a yes, the agent pushed it, and the guard appeared under Automation → Guards as "Trials skip pitches".

6 Send a test, not a send

A test send delivers one email to one address, without mailing your list, and your rules say whose address.

Asked to send it to the operator instead, the agent did, and said the provider accepted it, which doesn't confirm delivery. Mimeo itself refuses a test to an unsubscribed person, whoever asks.

7 Keep Make it live your click

A new flow can't mail anyone until someone makes it live, so keep that click for yourself.

Following the step 1 rules, the agent showed the diff and a rehearsal and asked before pushing. After a yes:

A push can't make a flow live, and a flow with errors can't be made live at all.