English
What is Mankomail
Mankomail is a workflow automation tool built entirely around email. You connect your mailboxes, draw workflows on a visual canvas, and each incoming email that matches a workflow runs through it: it gets categorised, filed, answered with a draft, logged in a table, sent to another tool, or put on hold for a human decision.
The problem Mankomail solves
Email is still the main work channel of most businesses: invoices, customer requests, applications, appointment requests, after-sales, reminders. A large part of this handling is repetitive, and language models can now read, classify and write well enough to take it on.
The usual options fit poorly:
- General-purpose automation tools are powerful but abstract. They have no notion of a mailbox, a thread, a recipient or a tone, and a non-technical colleague rarely manages alone.
- Consumer AI email assistants are closed boxes: no business logic, no connection to your internal tools, no governance, no self-hosting.
- Custom development is slow, expensive and hard for the business to maintain.
Mankomail takes the specialised route: the email is the object that flows through every workflow, and the results show up where people work — in the mailbox.
What Mankomail does
Connected mailboxes and the mirror. Each member connects Gmail, Microsoft 365 or any IMAP/SMTP mailbox. Mankomail keeps a complete, two-way synchronised copy of each mailbox — the mirror: folders and labels, threads, drafts, sent mail, read state and attachments. New mail arrives through push notifications where the provider offers them (Gmail, Microsoft Graph, IMAP IDLE), with periodic polling as a safety net. History is synchronised progressively, most recent first. See Mailboxes and the mirror.
Workflows. A workflow is a graph drawn on a canvas: a trigger, then nodes for conditions, AI, mail actions, data and outside services. One run corresponds to one email, so twelve emails make twelve independent runs, each with its own history and its own retries. A workflow is edited as a draft and runs only once you publish it. See Workflows, Runs and Versions.
Triggers. Most workflows start with Email received, filtered by declarative conditions on the sender, its domain, the recipients, the subject, attachments, folders and more. Workflows can also start from a webhook, a schedule, a manual run, a call from another workflow, the failure of another workflow, or an event in a connected service such as Airtable, Notion, Yousign or MyNotary. See Triggers and conditions.
AI nodes. Categorize (each category becomes an output of the node), Extract, Summarize, Compose (AI) and Free instruction (AI). Each AI node can use the instance's default model or a provider you link to it: Anthropic, OpenAI, Mistral, OpenRouter, Ollama or any OpenAI-compatible API. Drafts written by AI use the recipient's profile from the address book: formality, tone, language, signature and notes.
Actions on the mailbox. Move (add or remove folders and labels), Flag (read, flagged), Compose and Send — as a draft or sent directly, a choice made in each node. Changes go through the mirror and show up in the mailbox right away.
Integrations. Google Drive, Sheets and Calendar; Microsoft OneDrive, SharePoint, Excel and Outlook calendar; Notion, Airtable, Calendly, Yousign, MyNotary; and an HTTP request node for any other API. See Integrations.
Tables. Simple data tables your team maintains itself — a supplier list, a client directory, a follow-up log — that workflows can read and write. See Tables.
Review and approvals. An Approval node pauses a run until someone decides. The Morning review gathers the drafts workflows have prepared, ready to check and send. See Review and approvals.
The analyzer. Run on a mailbox, the analyzer groups what it receives into flows (invoices, appointment requests, notifications…) and proposes ready-made workflows instead of an empty canvas. See The analyzer.
Webmail. An optional mail client built on the mirror, where workflow results appear next to each message.
Safety and governance. A test run replays real emails with simulated effects, a scope keeps chosen senders and domains out of every workflow and every AI provider, and administrators control which nodes are allowed, sending limits and API keys. See Governance.
Who Mankomail is for
- Businesses, from freelancers to SMEs, whose teams spend hours on repetitive email.
- Business users who build their own automations without writing code.
- Administrators and IT teams, who connect the organisation's mail provider, configure AI providers and set the rules every workflow follows.
- Consultants and agencies who set up email automation for their clients.
An instance is one organisation. Each member has their own space — mailboxes, workflows, address book — and administrators have an Administration area on top.
Self-hosted or cloud
Mankomail comes in two forms of the same product, with the same features:
- Self-hosted: you run it on your own infrastructure with Docker Compose. It needs PostgreSQL and an S3-compatible object storage, nothing else. See Self-hosting.
- Cloud: a dedicated instance operated for you. See Cloud.
Licence
The source code of Mankomail is public and released under a fair-code (source-available) licence. You may install, use and modify it for your organisation's internal needs at no cost. Hosting or operating it for third parties requires a partner licence. A consultant or an agency may install and configure Mankomail for a client who then uses it for itself.