Usage guides

How to run Mimeo from the web UI — the day-to-day work of managing subscribers, getting data in, writing email, and getting it delivered.

• Getting started First login through first test send, in order.
• People Search and filter, the person page, unsubscribes, exports, and GDPR erase.
• CSV import Column mapping, overwrite posture, tags, and migrating unsubscribes.
• Migrating your list Bring your unsubscribes, trim the cold tail, warm up your sending, and cut over cleanly.
• Emails The library, the markdown editor, Liquid variables, templates, and preview.
• Media library Images, PDFs and zips with alt text, inserted into any email from one library.
• Sequences A series of emails on set delays: on/off, draft steps, and repeat-run modes.
• Flows Event-triggered automation: steps, gates, conditions, versions, and dry runs.
• Scheduled queue Everything about to be sent, why anything is holding, and send windows.
• Segments Live rules over your list, trend lines, and watchdogs for states that shouldn't happen.
• Broadcasts One-off sends against a segment — schedule, cancel, and two ways to deliver.
• Activity & events The instance-wide event feed, and the registry of every event name with its payload shape and what listens for it.
• Reporting What every email, sequence, flow and broadcast actually did — and what's excluded.
• The dashboard List growth, what's about to send, and alerts only when there are any.
• Keyboard and search ⌘K, / to search, and running the whole console without a mouse.
• Guards Send-time checkpoints that pause, skip, cancel, or exit — and why.
• Sending & domains Providers, sending domains, and senders have their own section — start with the setup wizard.

If you'd rather drive it with an agent

Everything above can also be done by your coding agent. The manager repo holds your whole operation as files your agent edits and ships through the CLI; the MCP server on your Mimeo gives it the same reach as tools — questions, one-off changes, authoring included; and underneath both sits the same API your app POSTs events to. The map of how those fit: How it fits together.