Build an AI Reply Assistant for Gmail
Automate the prep work of replying to email — AI drafts a reply, you review and send it yourself. Never fully automatic.
What You're Building
By the end of this guide, labeling an email "Needs Reply" in Gmail will make AI draft a reply for you — sitting in your Drafts folder, waiting for your review. It will never send automatically. You read it, fix anything wrong, and click Send yourself. If you've completed Build Your First AI Automation, some of this Zapier interface will look familiar — but this guide stands on its own, and teaches a different, equally important pattern: automating preparation, not judgment.
Why We're Keeping a Human in the Loop
Not every automation should act on its own
Build Your First AI Automation taught a fully automatic pattern: trigger, AI, done. This guide teaches a different one, just as valuable: trigger, AI drafts, a human reviews, then acts. Some tasks are safe to fully automate. Sending an email in your name usually isn't.
Automate preparation, not judgment
AI is good at producing a reasonable first draft quickly. It's not good at knowing what you'd actually want to promise, commit to, or leave out. Let it do the first part. Keep the second part yours.
Why a draft is the right output here
A draft costs you almost nothing if it's wrong — you just edit or delete it. A sent email you didn't mean to send can cost you a lot more. That asymmetry is why this automation stops at "ready to review," not "sent."
Get Your Accounts Ready
Confirm your Google and Zapier accounts
Make sure you have a Google account (Gmail) and a Zapier account. If you completed Build Your First AI Automation, you can reuse the same accounts here.
This guide uses the same two accounts as the automation guide — Gmail for email, Zapier to connect it to AI.
You can sign in to both mail.google.com and zapier.com.
Stuck?
If you don't have a Zapier account yet, sign up free at zapier.com — new accounts get an automatic 14-day trial with no credit card required, which is enough to build and test this guide.
A quick note on Zapier's free plan
Like the first automation guide, this one uses more than two steps, which needs the multi-step access included in Zapier's 14-day trial (or a paid plan afterward). The permanently free plan alone only allows one trigger and one action.
How the Workflow Works
Before opening Zapier, see the shape of what you're building — and the two loops working together.
Trigger: you flag an email
Labeling an email "Needs Reply" in Gmail is the signal that starts everything — a deliberate action you take, not something that happens on its own.
AI Draft: a reply gets prepared
Zapier reads the email and asks AI to draft a reply — real text, ready to look at, not yet sent anywhere.
Human Review: you check it
This is the step that makes the automation safe. You open the draft, confirm it's right, and fix anything that isn't.
Send: only you do this
Nothing in this automation ever clicks Send. That action stays entirely yours, every time.
Create the "Needs Reply" Gmail Label
Create the label in Gmail
In Gmail, create a new label called "Needs Reply" (look for "+" next to Labels in the sidebar, or Settings → Labels).
A label is just a tag you can apply to any email — it doesn't move or change the email, it just marks it. Zapier can only watch for a label that already exists, so this has to happen first.
"Needs Reply" appears in your Gmail label list, and you can apply it to an email.
Stuck?
If you build the Zapier trigger first and don't see this label as an option there, come back here and create it — Zapier can't select a label that doesn't exist yet.
Apply it to a real email
Find a real email in your inbox and apply the "Needs Reply" label to it.
You'll need at least one labeled email so Zapier has something real to test against.
The email now shows the "Needs Reply" label in Gmail.
Build the Gmail Trigger
Create a new Zap
In Zapier, click Create, then Zap.
A Zap is one automation — a trigger plus one or more actions.
You're on a blank Zap editor with an empty trigger step.
Choose Gmail and the New Labeled Email event
Search for and select Gmail as the trigger app, then choose "New Labeled Email" as the trigger event.
This exact event fires whenever an email gets the label you choose — not just any new email.
The trigger step shows "New Labeled Email."
Connect your account and select the label
Connect your Gmail account if asked, then set "Label or mailbox" to "Needs Reply."
This is the same label you created earlier — Zapier can only offer labels that already exist in your account.
"Needs Reply" appears selected in the Label or mailbox field.
Stuck?
The label may show up in lowercase in Zapier's list even though it's capitalized in Gmail — that's normal, just pick the one that matches your label.
Test the trigger
Click Test trigger.
Zapier needs a real labeled email to learn what data is available — sender, subject, body.
The test returns a real email with sender, subject, and body — you may be able to choose from a few recent matches.
Stuck?
If you see "No labeled email found," this is genuinely common — Gmail-to-Zapier sync isn't instant. Wait a minute or two after labeling an email, then click Test trigger again.
Add the AI Reply Step
Add an action step
Click the + button below your trigger.
This is where AI drafts the reply, using the real email data from your trigger.
A new, empty action step appears.
Choose AI by Zapier
Search for and select "AI by Zapier" as the action.
This is Zapier's built-in AI — no separate OpenAI account or API key needed.
AI by Zapier appears as your action, with an empty Prompt field.
Write the prompt
In the Prompt field, type this, leaving your cursor after each label so you can insert the matching dynamic field next:
This prompt gives the AI the full context it needs and explicit rules against inventing information — the same safety rules you'd want from any assistant drafting on your behalf.
The Prompt field contains this text with each label ("Sender:", "Subject:", "Email body:") still empty after it, ready for a dynamic field.
Stuck?
Typing "/" opens a picker of real data from earlier steps — always insert the field from that picker. If you type the field name as plain text instead, the AI will only ever see those literal words, not the real email.
You are drafting a reply to an email. Sender: Subject: Email body: Write a short, professional draft reply based on the email above. Rules: - Do not invent facts, dates, prices, or commitments that aren't in the original email. - If a needed detail is unclear or missing, leave a clearly marked placeholder like [confirm this] instead of guessing. - Keep the reply concise — a few sentences, not a full essay. - Tone: professional but warm. - This is a draft only. It will be reviewed by a human before anything is sent.
Insert the dynamic fields
Click right after "Sender:" and insert Step 1's From Name. Do the same for "Subject:" → Subject, and "Email body:" → Body Plain.
Each of these is real data from the email that triggered the Zap — the AI sees the actual sender, subject, and message every time it runs, not fixed text.
Each spot shows a small labeled token naming Step 1, not plain typed text.
Add the Output Field
Under Output Fields, create exactly one field: name it "Reply", set the type to Text, and turn Required on.
This tells the AI step exactly what to hand to the next step — the finished reply text, and nothing else.
Exactly one output field exists, named Reply.
Stuck?
AI by Zapier can auto-generate extra output fields on its own based on your prompt (for example, "Sender Name" or "Email Subject"). If that happens, delete any fields you didn't intentionally create and keep only Reply.
Test the step
Click Continue, then test the step.
This runs the AI for real, using your test email, so you can check the actual output before connecting Gmail.
You see a real, coherent draft reply in the Reply output, generated from your actual test email.
Create the Gmail Draft
Add the Create Draft Reply action
Click + to add another action. Search for and select Gmail, then choose "Create Draft Reply" — not the generic "Create Draft."
"Create Draft Reply" is built specifically to reply inside an existing conversation, instead of starting a new, disconnected email.
Gmail "Create Draft Reply" appears as your third step.
Map the Thread field correctly
Click the small ⋮ menu next to the Thread field, switch it from "Static" to "Custom," then insert Step 1's Thread Id.
By default this field expects you to pick one specific, fixed thread from a list — the opposite of what you want, since every labeled email has a different thread. Custom lets you insert the real thread ID dynamically, so it's correct every time the Zap runs.
The Thread field shows a token like "1. Thread Id" rather than one hardcoded value chosen from a dropdown.
Stuck?
Do not pick a specific thread from the static list. If you do, this action will always try to reply inside that one email's conversation, no matter which email was actually labeled.
Map To and Body
Set To to Step 1's From Email. Set Body to Step 2's Reply output.
There's no Subject field here at all — that's expected. Because this is a genuine reply action, Gmail handles the subject automatically as part of replying inside the thread.
To and Body both show inserted tokens, not typed text.
Test this step
Click Continue, then test the step.
This creates one real draft in your Gmail account, inside the actual thread of your test email.
The test succeeds and shows a Thread Id matching your original test email's thread, and a Label Ids value of DRAFT.
Stuck?
If To or Body show plain typed text instead of a small token, go back and re-insert them from the dynamic-data picker.
Review Your Test Draft Critically
Open the test draft in Gmail
Go to Gmail and find the draft the test just created.
Seeing it in Gmail itself, not just in Zapier's test panel, is the real proof it landed correctly.
You can see the actual draft, inside the correct email thread.
Check it for invented information
Read the draft carefully. Does it state any fact, date, price, or commitment that wasn't actually in the original email?
AI can sound confident while being wrong. This review step is exactly what makes the automation safe to use.
You've either confirmed the draft only uses real information, or found something to fix.
Stuck?
If the AI invented or assumed something, that's not a failure of the automation — it's exactly why review exists. You can reinforce the "do not invent facts" rule in your prompt and retest, but always plan to read every draft before sending, regardless.
What a good draft looks like
Here's a realistic example: an email asking about scheduling, and a draft that handles it well. It answers the actual question, stays concise, doesn't invent a specific time the sender never confirmed, keeps an appropriate tone, and leaves the actual decision to the human reviewing it.
Incoming email Subject: Meeting next week Hi Patrick, Are you available next Tuesday afternoon to go over the proposal together? Let me know what works for you. Best, Sarah ---------- AI-drafted reply Hi Sarah, Thanks for reaching out. Tuesday afternoon could work for me. What time were you thinking? Best, Patrick
What a bad draft looks like
Now compare that to what the same email could have produced if the AI guessed instead of asking. This version invents a specific time nobody agreed to, and commits to it as though it were already confirmed — exactly the kind of mistake this review step exists to catch before anything gets sent.
Hi Sarah, Tuesday at 14:00 works perfectly. I'll see you then. Best, Patrick
Delete this test draft
Since this was just a test, delete it from your Gmail Drafts folder.
This keeps your Drafts folder clean and makes sure a test draft never gets accidentally sent later.
The test draft no longer appears in your Drafts folder.
Turn It On and Use It For Real
Name your Zap
Give your Zap a clear name, like "Needs Reply to AI Draft."
A clear name matters once you have more than one Zap — it's the only thing you'll see in your dashboard.
The name appears at the top of the editor instead of "Untitled Zap."
Publish and turn it on
Click Publish, then confirm the on/off toggle is set to On.
A Zap only runs automatically once it's published and turned on — building and testing it doesn't do that for you.
The toggle shows On, and the Zap appears as Published in your Zaps list.
Stuck?
If everything worked while testing but nothing happens later, this is almost always the reason — confirm the toggle is On, not just that you clicked Publish once.
Try it with a real email
Go to Gmail and label a different, real email "Needs Reply." Then wait a few minutes and check your Drafts folder.
The label trigger checks periodically rather than instantly — a couple of minutes' delay is normal, not a sign something's wrong.
A new draft appears, inside the correct conversation, replying to that specific email.
What You Learned + Where to Go Next
The pattern behind this automation
Trigger, AI draft, human review, send. AI prepares; you decide. That's a genuinely different lesson from Build Your First AI Automation's fully-automatic pattern — and just as reusable, anywhere a task benefits from speed but shouldn't skip judgment.
Ideas to try next
Try labeling different kinds of emails with different rules in the prompt (e.g. a shorter, more formal tone for one label, warmer for another), or add a second label for emails that should be archived instead of replied to.
When full automation is the better choice
Not every task needs a human step — logging, summarizing, and organizing data (like in Build Your First AI Automation) are usually safe to fully automate. The judgment call is whether a wrong output would actually cost you something. When it would, keep a human in the loop, the way this guide does.
Apply "Needs Reply" to a real email, wait for Zapier to run, then open Gmail and find the generated draft inside the correct conversation. Confirm the recipient is correct and the draft actually responds to that email — then send it yourself, only after reviewing it.
- The draft appeared inside the correct email thread, not as a separate new email
- The recipient (To) is correct
- The draft is genuinely relevant to the real email's content, with nothing invented
- Nothing was sent automatically — it was still a draft, waiting for you
- You reviewed it, and only then clicked Send yourself
Recommended before this guide