How to Build an AI Email Assistant That Drafts but Never Sends Without You

A step-by-step recipe for an AI email assistant that reads new email, writes a reply draft in Gmail, and never sends anything on its own — using Zapier, n8n or a ready-made assistant.

Short answer

To build an AI email assistant that never sends on its own, connect your inbox to an automation tool, add one AI step that writes a reply, and make the final action 'Create Draft Reply' instead of 'Send.' Don't give the workflow any send permission. Zapier and n8n both offer Gmail draft actions, and ready-made assistants like Lindy say they wait for approval before sending.

The most common thing small-business owners want from an AI agent is help with email. The most common fear is that it will send something wrong to a customer. You can have the first without the second: build an assistant that writes drafts and never sends. You read, edit and hit Send yourself.

This is a researched recipe based on each tool’s documentation. We describe the exact actions that exist; we’ll add screenshots and real numbers after we run it ourselves.

Why “draft, don’t send” is the right design

Owners who’ve worked with AI-agent builders keep asking for the same thing: the agent proposes, a human approves with one tap (r/AI_Agents). IBM’s guidance on agents agrees that actions like “sending mass emails” should require human confirmation (IBM). And accuracy is the top concern of small-business owners considering agents (Bluehost/ListenLabs, PDF).

A draft is the perfect approval step because it lives where you already work: in your Drafts folder, threaded under the original email.

Three ways to build it

Zapiern8nReady-made (Lindy)
EffortLowMediumLowest
Draft action“Create Draft Reply” / “Create Draft”Gmail node: Draft → CreateBuilt in (“drafts replies in your voice”)
How sending is preventedYou never add a send stepYou never add a send operation“Waits for approval” on outside actions
Pricing unitTasks per successful stepExecutions per full runCredits per user
Entry priceFree (100 tasks); Pro from $19.99/mo annualStarter €20/mo annual; self-host free$49.99/user/mo after free credits
SourcesZapier Gmail, pricingn8n Gmail docs, pricingLindy pricing

Before you start: 15 minutes of prep

  1. Write a “reply guide.” One page: your tone, your sign-off, hours, prices you’re allowed to quote, things the assistant must never promise (refunds, delivery dates, medical advice). The AI step will use this as its instructions.
  2. Collect five good past replies. Real examples teach tone better than adjectives.
  3. Pick the scope. Start with one address (e.g., info@) or one Gmail label, not your whole inbox.
  4. Create a Gmail label called AI-draft so you can find what the assistant made.

If your answers live in your head rather than in documents, do our data readiness checklist first.

Recipe A: Zapier (easiest)

Step 1 — Trigger. Choose Gmail → New Email (or New Email Matching Search, e.g. to:info@yourbusiness.com -category:promotions). Triggers don’t count as tasks (Zapier pricing).

Step 2 — Filter (optional). Add Filter by Zapier to skip newsletters and no-reply senders. Built-in tools like Filter don’t use tasks (Zapier pricing). Note: Filters require a paid plan; Free allows only two-step Zaps.

Step 3 — AI step. Add AI by Zapier (available on Professional and above) with a prompt like:

You are the email assistant for [Business]. Using the reply guide below, write a reply to this email. If the email asks for something not covered by the guide, write a short holding reply and start the draft with “[NEEDS SAM]”. Never promise refunds, dates or prices not in the guide. Reply guide: [paste] Email from {{sender}}: {{body}}

Step 4 — Draft, not send. Add Gmail → Create Draft Reply (“Create a draft reply to an existing email”). Map the thread from step 1 and the body from step 3. If you use Create Draft instead, the required fields are Subject and Body, with optional To, CC, BCC and “Label or mailbox” — set the label to AI-draft (Zapier Gmail integration).

Step 5 — Check for send steps. Read your Zap from top to bottom. There should be no Send Email or Reply to Email action anywhere — those actions exist in the same Gmail integration, so it’s easy to pick the wrong one (Zapier help).

Cost estimate: roughly 2 tasks per email (AI step + draft step), more if the AI step’s model tier costs extra. At 300 emails a month that’s around 600+ tasks — inside the 750-task Pro tier ($19.99/month annual). This is an estimate from the published billing rules, not a measured bill.

Recipe B: n8n (more control, per-run pricing)

Step 1 — Trigger. Add the Gmail Trigger node (n8n Gmail docs).

Step 2 — AI step. Add an AI step or the AI Agent node with your reply guide as the system instructions. n8n’s Starter plan includes “AI models without API keys” (n8n pricing).

Step 3 — Draft. Add a Gmail node with Resource Draft, Operation Create. The Gmail node supports creating, getting and deleting drafts, plus labeling messages (n8n Gmail docs).

Step 4 — Label the original. Add a Gmail node: Message → Add Label → AI-draft.

If you use the AI Agent node with tools: the Gmail node “can be used as an AI tool” (n8n Gmail docs). Only give the agent the create draft operation — never send or reply — and turn on n8n’s “human approval for tool calls” (n8n pricing).

Cost: each incoming email is one execution, however many steps it runs.

Recipe C: a ready-made assistant

If you’d rather not build anything, Lindy advertises inbox management and “drafts replies in your voice,” and states: “Anything with outside impact waits for approval such as sending an email” (Lindy pricing). It costs $49.99 per active user per month after a 7-day, $50 free-credit trial.

Test it safely

  1. Send yourself three test emails from a personal account: a simple question, a complaint, and something outside your guide.
  2. Confirm all three produced drafts, none were sent, and the out-of-scope one is flagged [NEEDS SAM].
  3. Check your Sent folder. It should be untouched.
  4. Run it for a week. Count drafts used as-is, used with edits, and discarded.

Keep it working

People often build an agent and walk away from it, or remove human review too fast (r/Solopreneur). Put a 10-minute weekly check on your calendar:

  • Update the reply guide with any answer you had to fix twice.
  • Look at the workflow’s error/run history.
  • Check your usage against your plan’s limit (Zapier tasks, n8n executions).

Privacy notes

  • Scope: trigger on one address or label, not the whole inbox.
  • Sensitive data: if your email contains patient, legal or financial information, confirm the tools involved sign the agreements your industry needs. For example, Lindy offers HIPAA with a signed BAA only on Enterprise (Lindy pricing).
  • Self-hosting: n8n Community Edition keeps data on your own server (n8n pricing).

The bottom line

An email assistant that only drafts is one of the safest, most useful first agents you can build. It saves the typing, keeps you in control, and fails gracefully: the worst case is a bad draft you delete.

Verdict: Worth it if you answer 10+ similar emails a week. Skip the build and use a ready-made assistant if you don’t want to maintain a workflow.

Frequently asked questions

Can an AI write email drafts in Gmail automatically?

Yes. Zapier's Gmail integration includes 'Create Draft' and 'Create Draft Reply' actions, and n8n's Gmail node can create drafts. Combine either with an AI step that writes the reply text.

How do I make sure the AI never sends an email?

Use only draft actions in your workflow, never 'Send Email' or 'Reply to Email.' Test with a dummy message, label drafts so you can find them, and review the workflow whenever you edit it.

What does an AI email assistant cost?

On Zapier, a workflow with a trigger, one AI step and a draft step uses roughly two tasks per email plus any extra for the AI step; Zapier Pro starts at $19.99/month billed annually for 750 tasks. n8n Starter is €20/month billed annually and bills per workflow run. Lindy is $49.99 per user per month.

Is it safe to let AI read my email?

It depends on the tool's data policy and your industry. Limit the workflow to a label or a specific address, avoid sending patient or financial data unless the vendor signs the agreements your industry requires, and check each tool's training and retention settings.

Should I use Zapier, n8n or a ready-made assistant?

Use a ready-made assistant like Lindy if you want minimal setup. Use Zapier for the easiest do-it-yourself build. Use n8n if you want per-run pricing or to self-host for privacy.

Prices and features change often. We checked every linked source on the date above; confirm on the vendor's page before you buy. Some links may be affiliate links — see our disclosure.