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 startedDownload and install Mimeo, connect sending and media, and prepare your first audience.
• PeopleSearch and filter, the person page, unsubscribes, exports, and GDPR erase.
• CSV importColumn mapping, overwrite posture, tags, and migrating unsubscribes.
• Migrating from another email platformPreserve suppressions, transition over three newsletters, and cut over without duplicate sends.
• EmailsThe library, the markdown editor, Liquid variables, templates, and preview.
• Media libraryImages, PDFs and zips with alt text, inserted into any email from one library.
• SequencesA series of emails on set delays: on/off, draft steps, and repeat-run modes.
• FlowsEvent-triggered automation: steps, gates, conditions, versions, and dry runs.
• Scheduled queueEverything about to be sent, why anything is holding, and send windows.
• SegmentsLive rules over your list, trend lines, and watchdogs for states that shouldn't happen.
• BroadcastsOne-off sends against a segment — schedule, cancel, and two ways to deliver.
• Activity & eventsThe instance-wide event feed, and the registry of every event name with its payload shape and what listens for it.
• ReportingWhat every email, sequence, flow and broadcast actually did — and what's excluded.
• The dashboardList 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.
• GuardsSend-time checkpoints that pause, skip, cancel, or exit — and why.
• Sending & domainsProviders, 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.