# n8n, Zapier or a ready-made inbox for your email agent

> n8n and Zapier build email agents from parts, and you set up approvals and limits yourself. Command Mail is an inbox for your agent with fixed sending rules.

Updated: 2026-10-29 · Fact-checked: 2026-10-29 · Canonical: https://commandmail.app/en/compare/n8n-zapier-email-agent · Deutsch: https://commandmail.app/de/vergleich/n8n-zapier-oder-fertiges-postfach.md

Pick n8n or Zapier when your email agent is one part of a larger automation: you assemble the trigger, the AI step, the approval and the limits yourself, and you can connect email to a CRM, spreadsheets or chat along the way.[^6][^12] Command Mail is a ready-made inbox for your agent, where permissions, approval and sending limits are enforced by the server instead of being rebuilt in each workflow.[^17]

So the real question is whether you want to wire the safety logic yourself or have it built in. Both platforms now ship approval steps of their own: n8n for an AI agent's tool calls, Zapier as a Human in the Loop step inside a Zap.[^6][^16] Where those steps apply is up to you.

Command Mail is our product. Everything said here about n8n and Zapier comes from their pricing pages, help articles, documentation and license, checked on 2026-10-29; we did not test either platform for this page.[^1][^11] The Command Mail details come from its llms.txt, its documentation and the app code at commit d9ab36c.

Last updated: 2026-10-29

## Build it yourself or use something ready-made

With n8n or Zapier, an email agent is a chain of building blocks. A trigger picks up new mail, an AI step reads it and writes a reply, Gmail actions send, reply or file, and you can put review steps, filters and other apps anywhere in between.[^3][^5][^15]

Command Mail works the other way round. You forward your addresses into a hosted inbox, and your agent, for example Claude, ChatGPT or Codex, connects through MCP, the ChatGPT plugin or the CLI.[^17][^18] Permissions per connection set which operations it can use, and an autonomy level per mailbox limits what it changes and sends there.[^17]

n8n and Zapier do far more than Command Mail because they can chain email with almost any other app.[^12][^3] This comparison therefore looks only at the email safety logic: who approves, what can happen without approval, and what limits apply when an agent sends.

## n8n, Zapier and Command Mail at a glance

| Question | n8n | Zapier | Command Mail |
|---|---|---|---|
| Price (checked 2026-10-29) | Cloud Starter €20, Pro €50 per month billed yearly; Business €667, self-hosted only; Community edition free[^1][^2] | Free $0 with 100 tasks; Professional from $19.99, Team from $69 per month billed yearly[^11] | Free €0 with one mailbox, the last 90 days and no sending; Pro €19 per month for the first 100 paying Pro accounts while the subscription runs, €29 after that; Team €39 per person[^17] |
| What you pay for | workflow executions, with unlimited steps[^1] | tasks, usually one per successful action, with exceptions; a successful Zapier MCP call uses two, a failed one none[^14] | monthly or yearly subscription, Team per person[^17] |
| Email connection | Gmail node and Gmail Trigger with a polling interval you choose[^3][^5] | Gmail triggers and actions, polling every 15, 2 or 1 minutes depending on plan[^15][^11] | any address, by forwarding[^18] |
| Approval before sending | human review per AI agent tool, through chat, Slack, Gmail, Outlook and other channels[^6] | Human in the Loop “Request Approval” step in a Zap, paid account[^16] | only a person in the browser approves the exact draft revision[^17][^18] |
| Limits on autonomous sending | you build them | you build them | daily limit (default 50), at most 20 recipients, a send key per email, no agent mail to detected automated senders[^17][^18] |
| Agent access | MCP Server Trigger and MCP Client Tool[^8][^9] | Zapier MCP with 9,000+ apps[^12] | hosted MCP server with OAuth, ChatGPT plugin, Claude directory, CLI[^17] |

## What n8n does well

In n8n you define every step yourself and can also run the whole thing on your own infrastructure.[^2] Its Gmail node creates drafts, sends, replies, labels and works with threads, and you can attach it to an AI agent as a tool whose parameters the model fills in.[^3] The Gmail Trigger polls the mailbox at an interval you set and fetches 10 emails per poll by default, 50 at most, queuing the rest for the next cycle.[^5]

Tool approval in n8n is well thought out. When a tool sits behind a human review step, the workflow pauses before the agent calls it, and a reviewer sees the tool name and parameters and approves or denies.[^6] What gets approved is exactly what the AI put into those parameters; a denied call never runs, and the agent is told it was rejected.[^6] The approval request can travel through a different channel from the conversation, such as Slack, Telegram, Teams, Gmail or Outlook.[^6]

For simpler flows without AI, the Gmail node also has a Send and Wait for Approval operation. It emails an approve button, optionally a decline button too, and holds the workflow until the recipient responds.[^4]

n8n charges per workflow execution, however many steps the workflow has.[^1] Starter is €20 a month billed yearly for 2,500 executions and Pro is €50 for 10,000, and human approval for tool calls is part of every cloud plan.[^1] The Community edition is free to run on your own infrastructure with almost the full feature set.[^2] With the MCP Server Trigger you can offer your own workflows as tools to Claude or other MCP clients, and the MCP Client Tool brings outside MCP servers into an n8n agent.[^8][^9]

## Where n8n falls short

In n8n, approval exists only where you put it. You can place the review step in front of all of an agent's tools or just some of them, and a Gmail tool that is not attached to it runs without asking.[^6] The docs also tell you to describe in the system prompt which tools need approval and how the agent should handle a denial.[^6]

The Gmail node documentation does not describe a daily cap, a recipient limit or a block on replying to automated or no-reply senders; you build such limits yourself with extra workflow steps.[^4] Be careful with the Delete operation, which removes a message immediately and permanently; for deletions you can undo, the docs point to the thread Trash operation.[^4]

Self-hosting moves the work elsewhere. Managed Sign in with Google, without any setup in the Google Cloud Console, is available only on n8n Cloud; on a self-hosted instance you register your own OAuth app with Google.[^7] The license permits use and modification for your own internal business purposes or for non-commercial or personal use, and distribution only free of charge for non-commercial purposes.[^10] An agency that wants to sell client workflows running on its own n8n instance should check that with n8n first.

## What Zapier does well

Zapier connects email to a very large number of other apps and manages those connections for you.[^12] For Gmail it offers triggers such as New Email and New Attachment, and actions such as Send Email, Reply to Email, Create Draft, Create Draft Reply, Archive Email and Add Label to Email; Delete Email moves a message to the trash.[^15] Zapier MCP makes these actions available to Claude, ChatGPT or Cursor alongside more than 9,000 other apps, while Zapier takes care of logins, credentials and rate limits.[^12]

Zaps come with a built-in approval step. Human in the Loop's Request Approval action pauses the Zap, notifies reviewers by email, Slack or another Zap, and lets them approve, decline or, if you allow it, edit the content before the run continues.[^16] Reviewers need a Zapier account and access to the shared Zap. On what the help article calls a Pro account, requests can only go to yourself; on Team and Enterprise, reviewers must sign in as one of the Zapier users you selected.[^16]

Zapier MCP runs on whatever plan you already have, with no separate billing; each successful tool call uses two tasks and a failed one uses none.[^12] You can let the agent enable tools during the conversation or pick a fixed set, and the History view records every MCP action.[^12][^13] If your team already runs on Zapier, MCP access is already part of your plan.[^13]

## Where Zapier falls short

Zapier's approval is a step in the Zap, and you decide how it behaves. When a reviewer declines, the Zap either continues or stops depending on your setting, and on timeout it either skips the review and carries on or ends the run.[^16] If you choose “Continue run” or “Skip and continue” and put Send Email after it, the email goes out without anyone agreeing. The prerequisites for Human in the Loop list a paid Zapier account.[^16]

For Zapier MCP, neither the help article nor the product page describes an approval step of its own before a tool call.[^12][^13] When your agent calls Send Email, Zapier runs it; whether you get asked first depends on your AI client. The way to keep access tight is a fixed tool set without a sending action.[^12]

Costs grow with use. A successful standard action in a Zap usually uses one task; some built-in steps are free and others have their own rates.[^14] An agent that repeats an action many times over MCP uses proportionally more of your allowance.[^12] The free plan is limited to two-step Zaps and checks Gmail every 15 minutes; Professional checks every 2 minutes and Team and Enterprise every minute.[^11]

## How Command Mail sets the limits

In Command Mail, the email limits are in place before you build anything. When you connect an agent you pick its permissions: mail:read to read and sort, mail:draft for drafts that never send, mail:send-approved to send exactly the draft revision a person approved, and mail:send to send without approval.[^17] You can untick any permission while connecting, and sending without approval starts switched off.[^17]

On top of the permissions, each mailbox has an autonomy level. At read the agent changes nothing and sends nothing. At suggest and rules, the agent's direct sorting calls such as archiving, marking as spam and moving to the trash become suggestions, permanent deletion by the agent is blocked, and it sends only approved drafts.[^18] According to our app code, rules you turn on act on their own at rules, and deletion schedules that are already active keep running at both levels.

An agent sends directly only from a mailbox set to auto, and only with mail:send.[^17] The level limits changes and sending; according to our app code it does not separate read access by mailbox, because mail:read applies account-wide within what your plan makes visible.

Direct sending of this kind has limits that no workflow setting can switch off. Each email needs its own send key so a retry cannot send twice, a daily limit applies (50 by default), and one message can have at most 20 recipients.[^17][^18] The agent does not write on its own to detected automated senders, mailing lists or no-reply addresses.[^17] According to our app code, the server refuses such sends and also refuses to save an agent's reply draft to detected machine mail; you can still reply yourself in the app.

Approving drafts, deciding on suggestions and changing the autonomy level are things only a person can do in the browser.[^18] According to our app code, the approval route rejects any call that does not come from a signed-in browser session, so an agent key cannot approve its own draft.

## Example: replying to customer inquiries with approval

Say hello@ at your domain runs on Google Workspace, customer inquiries arrive there, and you want an agent to prepare replies without anything going out before you have looked at it.

In n8n, the workflow starts with the Gmail Trigger, an AI Agent node reads the message, and the Gmail Reply operation is attached as a tool behind a human review step in Slack.[^5][^3][^6] In Slack you see the tool and its parameters, including the reply text, and approve or deny.[^6] If you also want the inquiry logged in a spreadsheet or CRM, you add another node, which is exactly what n8n is for.

In Zapier, New Email starts the Zap, an AI step writes the reply, Request Approval sends it to you for review, and Reply to Email runs only after that.[^15][^16] Set “Action if reviewer declines” to “Stop run” and “On timeout” to “End run”; otherwise the reply can go out without your consent.[^16]

In Command Mail, you forward hello@, and your agent reads with mail:read and writes drafts with mail:draft.[^17] You approve the draft in the app, and with mail:send-approved the agent sends exactly that revision.[^17] Command Mail does not log anything in your CRM; your agent would need its own tools for that.

## When n8n or Zapier is the better choice

Choose n8n or Zapier when email is one link in a longer chain. If a new inquiry should land in the CRM, create a task, show up in team chat and get a reply, an automation platform builds that across apps in one go.[^12][^3] Command Mail is built for email only and does not connect other apps.

n8n is the better choice if you want to self-host or control every step of the agent. The Community edition costs nothing, workflows can be offered as MCP tools, and per-tool approval ties consent to the concrete parameters.[^2][^8][^6]

Zapier is the better choice if you want to start quickly without code and your team already works in Zapier. Zapier MCP brings your existing connections straight into Claude or ChatGPT, and Human in the Loop even lets reviewers edit the content before the Zap moves on.[^12][^16]

## When Command Mail fits

Command Mail fits when your agent mainly works in email and you would rather not build and maintain sending limits yourself. Without mail:send, any connected agent can only send the approved revision, and an agent allowed to send directly is bound by the daily limit, the recipient cap, send keys and the block on automated senders, whether or not a workflow plans for them.[^17][^18]

It also fits when your addresses sit with different providers. Anything you can forward ends up in one inbox, whether it comes from Gmail, Outlook or a web host, and Pro handles up to ten mailboxes.[^18][^17] The free plan covers one mailbox with the last 90 days for reading, sorting and drafting.[^17]

## Who Command Mail is not for

If your automations chain email with many other apps, use n8n or Zapier. If everything must run on your own servers, n8n is the option; the Command Mail docs do not describe a self-hosted version.[^2][^18]

Command Mail does not replace your existing mailbox. Mail arrives by forwarding, and changes in Command Mail do not sync back to the original mailbox.[^18] Sending starts with Pro; the operator is FYN Labs LLC in the US, and attachments are stored in Cloudflare's EU region.[^17][^19]

## Switching and setup

For n8n: start an n8n Cloud trial or install the Community edition.[^2] Create the Google credential, with Sign in with Google on Cloud or your own OAuth app when self-hosting, then build the Gmail Trigger, the AI Agent and the Gmail tool.[^7][^5][^3] Open the Tools panel on the AI Agent node, pick a channel under Human review and attach every tool that sends or deletes.[^6]

For Zapier: create a server for your AI client at mcp.zapier.com and choose a fixed tool set without sending actions for as long as you do not trust the agent to send.[^12] For fixed workflows, build a Zap with Request Approval before every sending action and set both decline and timeout to stop the run.[^16]

For Command Mail: connect each address in the app and set up forwarding at your current provider to the private inbound address it shows you.[^18] Then connect your agent, in Claude Code with `claude mcp add --transport http commandmail https://commandmail.app/mcp`, and start with mail:read and mail:draft.[^17]

## Further reading

- [Human in the loop for email agents](https://commandmail.app/en/learn/human-in-the-loop-email)
- [What is an MCP server?](https://commandmail.app/en/learn/what-is-an-mcp-server)
- [AI email support with a daily limit](https://commandmail.app/en/guides/ai-email-support)
- [Permissions and autonomy in Command Mail](https://commandmail.app/en/docs/permissions-and-autonomy)

You can start Command Mail for free and let your agent read and draft before it sends anything.

## Frequently asked questions

### Can an n8n agent send email without approval?

Yes, if you wire it that way. The Gmail node can send and reply as a tool of an AI agent. Approval applies only to tools you attach to a human review step; a person then sees the tool and its parameters and approves or denies the call.

### How much does an email agent on Zapier MCP cost?

Zapier MCP is included in every Zapier plan. Each successful tool call uses two tasks, and failed calls use none. The free plan has 100 tasks a month, and Professional starts at $19.99 a month billed yearly (checked 2026-10-29).

### Can I self-host n8n for free?

The Community edition is free and runs on your own infrastructure. Its license allows use and modification for your own internal business purposes or for non-commercial or personal use, and passing it on to others only free of charge for non-commercial purposes. Sign in with Google without your own Google Cloud app is available only on n8n Cloud.

### Does Command Mail replace n8n or Zapier?

Only for the email part. Command Mail does not connect other apps, build workflows or offer triggers for a CRM, spreadsheets or chat. If your automations chain email with many other tools, keep an automation platform for that.

### Can I connect n8n to Command Mail?

Command Mail does not document a ready-made n8n or Zapier integration. Its docs list a hosted MCP server with OAuth, a local MCP server, the CLI and REST, and n8n's MCP Client Tool supports OAuth2 among other methods. We have not tested this combination.

## Sources

1. [n8n: Pricing](https://n8n.io/pricing/), accessed 2026-10-29
2. [n8n docs: Choose how to use n8n (cloud, self-hosting, editions)](https://docs.n8n.io/choose-how-to-use-n8n), accessed 2026-10-29
3. [n8n docs: Gmail node](https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.gmail/), accessed 2026-10-29
4. [n8n docs: Gmail node, message operations](https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.gmail/message-operations/), accessed 2026-10-29
5. [n8n docs: Gmail Trigger](https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.gmailtrigger/), accessed 2026-10-29
6. [n8n docs: Human-in-the-loop for tools](https://docs.n8n.io/build/integrate-ai/ai-examples/human-in-the-loop-for-tools), accessed 2026-10-29
7. [n8n docs: Google credentials](https://docs.n8n.io/integrations/builtin/credentials/google), accessed 2026-10-29
8. [n8n docs: MCP Server Trigger](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-langchain.mcptrigger/), accessed 2026-10-29
9. [n8n docs: MCP Client Tool](https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.toolmcp), accessed 2026-10-29
10. [n8n: LICENSE.md (Sustainable Use License, GitHub)](https://github.com/n8n-io/n8n/blob/master/LICENSE.md), accessed 2026-10-29
11. [Zapier: Pricing](https://zapier.com/pricing), accessed 2026-10-29
12. [Zapier Help: What is Zapier MCP?](https://help.zapier.com/hc/en-us/articles/48308034391821-What-is-Zapier-MCP), accessed 2026-10-29
13. [Zapier: Zapier MCP (product page and FAQ)](https://zapier.com/mcp), accessed 2026-10-29
14. [Zapier Help: How is task usage measured in Zapier?](https://help.zapier.com/hc/en-us/articles/8496196837261-How-is-task-usage-measured-in-Zapier), accessed 2026-10-29
15. [Zapier: Gmail integration (triggers and actions)](https://zapier.com/apps/gmail/integrations), accessed 2026-10-29
16. [Zapier Help: Request approval with Human in the Loop](https://help.zapier.com/hc/en-us/articles/38731463206029-Request-approval-to-keep-your-workflow-running-with-Human-in-the-Loop), accessed 2026-10-29
17. [Command Mail: llms.txt (pricing, permissions, connection)](https://commandmail.app/llms.txt), accessed 2026-10-29
18. [Command Mail: Documentation](https://commandmail.app/en/docs.md), accessed 2026-10-29
19. [Command Mail: Privacy, operator and hosting](https://commandmail.app/privacy), accessed 2026-10-29

[^1]: [n8n: Pricing](https://n8n.io/pricing/), accessed 2026-10-29
[^2]: [n8n docs: Choose how to use n8n (cloud, self-hosting, editions)](https://docs.n8n.io/choose-how-to-use-n8n), accessed 2026-10-29
[^3]: [n8n docs: Gmail node](https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.gmail/), accessed 2026-10-29
[^4]: [n8n docs: Gmail node, message operations](https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.gmail/message-operations/), accessed 2026-10-29
[^5]: [n8n docs: Gmail Trigger](https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.gmailtrigger/), accessed 2026-10-29
[^6]: [n8n docs: Human-in-the-loop for tools](https://docs.n8n.io/build/integrate-ai/ai-examples/human-in-the-loop-for-tools), accessed 2026-10-29
[^7]: [n8n docs: Google credentials](https://docs.n8n.io/integrations/builtin/credentials/google), accessed 2026-10-29
[^8]: [n8n docs: MCP Server Trigger](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-langchain.mcptrigger/), accessed 2026-10-29
[^9]: [n8n docs: MCP Client Tool](https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.toolmcp), accessed 2026-10-29
[^10]: [n8n: LICENSE.md (Sustainable Use License, GitHub)](https://github.com/n8n-io/n8n/blob/master/LICENSE.md), accessed 2026-10-29
[^11]: [Zapier: Pricing](https://zapier.com/pricing), accessed 2026-10-29
[^12]: [Zapier Help: What is Zapier MCP?](https://help.zapier.com/hc/en-us/articles/48308034391821-What-is-Zapier-MCP), accessed 2026-10-29
[^13]: [Zapier: Zapier MCP (product page and FAQ)](https://zapier.com/mcp), accessed 2026-10-29
[^14]: [Zapier Help: How is task usage measured in Zapier?](https://help.zapier.com/hc/en-us/articles/8496196837261-How-is-task-usage-measured-in-Zapier), accessed 2026-10-29
[^15]: [Zapier: Gmail integration (triggers and actions)](https://zapier.com/apps/gmail/integrations), accessed 2026-10-29
[^16]: [Zapier Help: Request approval with Human in the Loop](https://help.zapier.com/hc/en-us/articles/38731463206029-Request-approval-to-keep-your-workflow-running-with-Human-in-the-Loop), accessed 2026-10-29
[^17]: [Command Mail: llms.txt (pricing, permissions, connection)](https://commandmail.app/llms.txt), accessed 2026-10-29
[^18]: [Command Mail: Documentation](https://commandmail.app/en/docs.md), accessed 2026-10-29
[^19]: [Command Mail: Privacy, operator and hosting](https://commandmail.app/privacy), accessed 2026-10-29

---

Command Mail: one inbox for you and your AI agent. Start free: https://commandmail.app/login?signup=1 · Connect your agent: https://commandmail.app/en/agents · MCP: https://commandmail.app/mcp