A Zapier AI Agent connects instructions, a trigger, and tool actions across 9,000+ apps, no code required. This guide builds a recruiting coordinator agent that checks a candidate's interview stage in a tracking sheet freely, but only ever drafts an offer email for a human to review and send, never sending one itself. You'll set an On Demand trigger, add two tools, and test in Zapier's chat panel. Budget 30-40 minutes on Zapier's free plan.
| Fact | Value |
|---|---|
| Tool | Zapier Agents |
| Difficulty | Beginner |
| Time required | 30-40 min |
| Compatibility | Zapier account (Free plan works for testing), a connected ATS or tracking sheet, Gmail or Outlook, browser only |
| Last updated | November 2026 |
What you'll build
You'll build a recruiting coordinator agent for a startup's hiring pipeline. It can check a candidate's current interview stage in a shared tracking sheet whenever someone asks, and when a candidate is ready for an offer, it can draft the offer email in Gmail. It never sends that email itself; the draft lands in Gmail's Drafts folder for a recruiter to review, edit, and send by hand.
A Zapier AI Agent is built from three things: instructions written in plain language that describe what should trigger it and what it should do, a trigger that decides when it runs (on a schedule, from an app event, from a Zap, or On Demand when you click Run or send it a chat message), and tools, which are ordinary Zapier actions from any of its 9,000+ apps that the agent can call on its own. Zapier doesn't have a per-action approval toggle the way some other builders do; instead, you keep a risky action safe by pointing it at a Draft-style action instead of a Send-style one, and by telling the agent explicitly, in its instructions, to ask before it acts.
Choose Zapier when your team is already standardized on it for other automations and you want an agent that reuses the same app connections. Choose n8n instead when you want exact control over HTTP requests and a formal Human review toggle per tool, or Make when you want a visual reasoning panel that shows each decision step by step.
Prerequisites
- A Zapier account (the Free plan is enough to build and test an agent)
- A Google Sheet or ATS with candidate names and interview stages
- A connected Gmail or Outlook account
- No coding experience required, just comfort filling in forms on a web page
Step-by-step guide
Create the agent and write its instructions
Go to agents.zapier.com and click + New agent in the left sidebar. Choose to start with a custom agent rather than a template, and in the text field describe what the agent should do, who triggers it, and which apps it uses. Click Create agent to let Zapier's prompt assistant tidy your wording, or Skip this step to keep your own phrasing exactly as written.
1Draft instructions to paste into the New agent dialog:23"When I ask about a candidate, look up their current interview stage in our4hiring tracker Google Sheet by name or email. When I say a candidate is ready5for an offer, draft (do not send) an offer email in Gmail addressed to them,6summarizing role, start date, and salary from what I tell you. Always ask me7to confirm the salary and start date before drafting."Expected result: A new agent appears with your instructions, and a Connect your apps step listing Google Sheets and Gmail.
Connect your apps and pick the On Demand trigger
In the Connect your apps step, create a connection for Google Sheets and Gmail by clicking the Settings icon next to each, or select an existing connection from the dropdown. Click Create to land on the agent's Configure screen, then set up its trigger: choose On Demand so the agent responds whenever you click Run or send it a chat message, rather than firing on a schedule or an app event.
1Trigger: On Demand2(alternatives: Schedule by Zapier, an app event trigger, or trigger via a Zap/MCP call)Expected result: The Configure screen shows your trigger as On Demand, with Google Sheets and Gmail listed as connected apps.
Add the read-only tool: look up candidate stage
In the Instructions field, click the Insert tools tab, then + Add tool. Select Google Sheets, then the Lookup Row action, and point it at your hiring tracker sheet with the candidate's name or email as the search column. This tool is safe for the agent to call on its own since it only reads a row; add it to your instructions as a labeled reference the agent can call.
1Tool: Google Sheets - Lookup Row2Spreadsheet: Hiring Tracker3Search column: Email4Returns: Candidate name, role, stage, interviewerExpected result: Asking the chat 'what stage is jane@example.com at?' triggers a visible tool call and returns her actual row from the sheet.
Add the risky tool as a draft, not a send
Click Insert tools and + Add tool again. Select Gmail, and choose Create Draft rather than Send Email; this is the Zapier equivalent of a human-review gate, since nothing reaches the candidate's inbox until a recruiter opens the draft and clicks Send themselves. Give the tool a clear description so the agent knows exactly when to use it.
1Tool: Gmail - Create Draft2Description for the agent: Draft (never send) an offer email once a candidate is confirmed3ready for an offer. Requires the recipient, role, start date, and salary.Expected result: Asking the chat to draft an offer for a candidate creates a new draft in the connected Gmail account instead of sending anything.
Reinforce the ask-before-acting rule and test in chat
Go back to the Instructions field and make sure it explicitly tells the agent to confirm salary and start date with you before drafting, and to never send anything on its own. Open the chat panel (the chat icon next to the agent) and run through the full flow: ask about a candidate's stage, then ask it to draft an offer, and confirm it asks you for the missing details before calling the Gmail tool.
1Test script:21. "What stage is jane@example.com at?" -> expect a Lookup Row tool call, no confirmation needed32. "Jane is ready for an offer, $95k, starting Dec 1" -> expect the agent to4 restate the details and ask you to confirm before it calls Create DraftExpected result: The agent answers the stage question immediately, but pauses to confirm salary and start date before it ever touches the Gmail tool.
Test thoroughly, then publish
Until you publish, the agent only runs during testing in the chat panel; nothing is live yet. Run several real candidates through it, including edge cases like a name that doesn't match any row, before clicking Publish in the upper-right corner. Publishing activates the trigger immediately, so finish testing first; to make further changes afterward you'll create a new draft version rather than editing the published one directly.
1Before publishing, verify:2- Lookup Row tool returns correct data for 3+ real candidates3- Create Draft tool never fires without you confirming salary + start date4- A nonexistent candidate email produces a clear 'not found' answer, not a guessExpected result: Clicking Publish activates the agent; it now responds live via chat or Run, with every offer email landing as a draft for a human to send.
Complete working example
1# Zapier AI Agent spec: Recruiting Coordinator2# Paste the `instructions` block into the agent's Instructions field,3# then add the two tools listed below through Insert tools -> + Add tool.45name: Recruiting Coordinator6trigger: On Demand (chat or Run button)78instructions: |9 You are a recruiting coordinator for our hiring team.1011 When someone asks about a candidate, look up their current interview stage12 in the Hiring Tracker Google Sheet by name or email using the13 look_up_candidate_stage tool. Report the stage, role, and interviewer.1415 When someone says a candidate is ready for an offer, you must have the16 role, start date, and salary before doing anything else. If any of those17 are missing, ask for them. Once you have all three, restate them back and18 ask "Should I draft this offer?" before calling draft_offer_email.1920 Never send an email yourself. draft_offer_email only ever creates a draft21 in Gmail; a human always reviews and sends it.2223 If a candidate's email doesn't match any row in the tracker, say so24 plainly instead of guessing at their stage.2526tools:27 - name: look_up_candidate_stage28 app: Google Sheets29 action: Lookup Row30 config:31 spreadsheet: Hiring Tracker32 search_column: Email33 returns: [name, role, stage, interviewer]34 approval: none (read-only)3536 - name: draft_offer_email37 app: Gmail38 action: Create Draft39 description_for_agent: >40 Draft (never send) an offer email once a candidate is confirmed ready41 for an offer. Requires recipient, role, start date, and salary.42 config:43 to: "{{candidate_email}}"44 subject: "Your offer from Acme Inc."45 body: >46 Includes role, start date, salary, and next steps, written in a47 warm, professional tone.48 approval: human review required (draft lands in Gmail Drafts, never sent by the agent)4950test_cases:51 - input: "What stage is jane@example.com at?"52 expect: look_up_candidate_stage called, no confirmation needed53 - input: "Jane is ready for an offer, $95k, starting Dec 1"54 expect: agent restates details and asks to confirm before draft_offer_email runs55 - input: "What stage is doesnotexist@example.com at?"56 expect: agent reports no match found, does not guess57Common mistakes
Why it's a problem: Adding Gmail's Send Email action instead of Create Draft
How to avoid: Send Email has no review step; the moment the agent decides to run it, the email is gone. Use Create Draft for anything that reaches a real person outside your team.
Why it's a problem: Writing vague instructions like 'help with recruiting' and expecting the agent to infer the approval rule
How to avoid: Spell out the rule explicitly: which details are required before drafting, and that it must ask for confirmation first. Vague instructions get vague, inconsistent behavior.
Why it's a problem: Testing only the happy path in chat and publishing without trying a missing or malformed candidate record
How to avoid: Run a nonexistent email, a blank search field, and a candidate with no interviewer listed before you publish. These are exactly the inputs that expose weak instructions.
Why it's a problem: Publishing before you're done testing because 'it's just a draft'
How to avoid: Publishing activates the trigger immediately. If it's On Demand that's low risk, but a scheduled or event trigger will start firing on real data the moment you publish.
Why it's a problem: Giving the agent too many unrelated tools and expecting it to stay focused
How to avoid: Keep an agent to 3-5 related actions. If it also needs to post to Slack, schedule interviews, and update a CRM, consider building a second agent and calling it from the first.
Best practices
- Write each tool's purpose as part of your instructions as if explaining it to a new hire: when to use it, what it needs, what it returns.
- Use Draft-style actions (Create Draft, Save as Draft) instead of Send-style actions for anything that reaches someone outside your team.
- State required fields and the confirmation step explicitly in instructions; don't rely on the model to infer what's risky.
- Test with real data, including edge cases, in the chat panel before you ever click Publish.
- Keep an agent focused on 3-5 related actions; split unrelated responsibilities into a second agent and call it from the first.
- Create a new draft version before editing a published agent, so changes don't affect the live version mid-test.
Still stuck?
Copy one of these prompts to get a personalized, step-by-step explanation.
I have a Zapier AI Agent with a Google Sheets Lookup Row tool (look_up_candidate_stage) and a Gmail Create Draft tool (draft_offer_email) gated by an explicit confirm-before-drafting instruction (spec below). Add a third tool that posts a Slack message to #hiring once a draft is created, and update the instructions so it happens automatically after the draft, with no extra confirmation needed for that step. [paste complete_code]
In the Zapier agent's Configure screen, use Zapier Copilot and ask: 'Add a tool that checks if a candidate already has an open offer draft in Gmail before creating a new one, so we don't draft two offers for the same person.'
Frequently asked questions
Do I need to know how to code to build an ai agent with Zapier?
No. Every step happens through forms and dropdowns: writing instructions in plain English, connecting apps, and picking actions from a list. There's no scripting language involved anywhere in this guide.
Does a Zapier AI Agent have an approval toggle like some other builders?
Not a dedicated one. Zapier's own guidance is to request approval before critical actions through your instructions, and to use draft-producing actions (like Gmail's Create Draft) instead of send-producing ones for anything that reaches someone outside your team, which is the pattern this guide uses.
What's the difference between the On Demand trigger and a scheduled or app-event trigger?
On Demand only runs when you click Run or send the agent a chat message; nothing happens on its own. A Schedule by Zapier trigger runs at fixed intervals, and an app trigger waits for a real event like a new row or email, so either one starts acting on live data the moment you publish.
Can one Zapier agent call another agent?
Yes. Zapier's best practice guidance recommends breaking a complex workflow into smaller, focused agents and using agent-to-agent calls to let one delegate work to another, rather than building a single agent that tries to do everything.
What does this cost to run?
Zapier's Free plan includes 100 tasks a month, enough for testing. Agents consume activities separately from regular Zap tasks: the free Agents tier includes 400 activities a month, and paid plans start around $33/mo (billed annually) for 1,500 activities.
Can someone set this up for me instead of building it myself?
Yes. RapidDev builds and hardens Zapier agents, including the draft-based approval pattern and testing most tutorials skip. A free 30-minute consultation is the fastest way to scope your version.
Talk to an Expert
Our team has built 1,000+ apps. Get personalized help with your project.
Book a free consultation