The Zaps that save an agency the most time are the certificate-request inbox, renewal reminders and web-form intake, and an illustrative six-person office runs all five below on roughly 1,000 to 1,400 tasks a month. A task is one successful action step; triggers, filters, Formatter and Delay steps are free.
The range depends on one setting: the model tier of any AI step. Left on the default for a new step it uses 5 tasks per run, which more than doubles the certificate Zap's bill compared with the cheapest tier. Everything below is priced step by step so you can change the numbers to your own volumes.
How Zapier counts tasks, in the six rules that matter here
Zapier's help centre defines a task as any successful action that runs. That makes pricing a Zap a matter of counting action steps, and these rules cover nearly every Zap an agency builds:
- Triggers never use tasks, and polling a mailbox every few minutes costs nothing.
- Filter and Paths steps are free, so a Zap that stops at a filter only costs the actions it ran before the filter.
- Formatter, Delay, Looping and Storage steps are free, which is what keeps the waiting in Zap 4 at no cost.
- Steps in Zapier Tables and Zapier Forms are free, which makes Tables a cheap place to keep a log.
- A search action set to carry on when nothing is found costs 1 task; set to stop when nothing is found it costs none.
- An AI by Zapier step costs 1 task on the Standard tier, 3 on Advanced, 5 on Premium, and 1 if you bring your own API key (an option for Advanced and Premium models). New steps default to Premium, and every tool call the step makes is charged at its tier rate again.
Two plan facts shape the budget. The Free plan gives 100 tasks a month, two-step Zaps only, and no Filter, Formatter or Webhooks steps, so none of these five fit it. Paid Professional starts at 750 tasks for $19.99 a month billed annually ($29.99 billed monthly), and the next step is 1,500 tasks for $39 a month billed annually ($58.50 monthly), then 2,000, 5,000, 10,000 and beyond. One change to note: from 1 December 2026, Zapier says Next Gen Zaps use tasks too, with at least 1 task per successful run, so a run made only of free steps will no longer be free there.
Zap 1: web form to your agency system or CRM
A quote request on your website usually lands in an inbox where someone retypes it. The Zap replaces the retyping: the trigger is a new submission in the form tool (Jotform, Google Forms or a Zapier Form), and the action creates the applicant or contact in the system you quote from.
Check the Zapier listing for your system first. EZLynx has a Zapier app with actions that include Create Personal Applicant With Opportunity, Create Commercial Applicant With Opportunity, Create Note and Create Document, and Zapier has an EZLynx and Jotform integration page that pairs Jotform's New Submission trigger with those actions. When I checked, Zapier listed no Vertafore app, so an agency on that platform would go through a CRM, a spreadsheet or the system's email-in address instead. I could not confirm listings for other systems, so search yours by name before you plan around it.
Price per run: 2 tasks (create the record, then post a Slack or email alert to whoever picks up new enquiries). Add a Formatter step to tidy phone numbers and capitalise names; it costs nothing.
Illustrative: 40 form enquiries a month cost 80 tasks. The Zap earns its place on the first Monday after a weekend campaign, when 15 enquiries arrive together and none are retyped.
A before and after for one enquiry
Before: a form email arrives, a customer service rep opens the AMS, retypes eleven fields and misses the date of birth because it was on page two. After: the record exists in the system within minutes, with the form's answers in a note, and the rep starts at the quote, not the typing. Keep a required-fields rule on the form so the Zap never creates half-empty applicants.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowZap 2: the certificate request inbox
Requests for certificates of insurance come in as free-text emails from contractors, landlords and clients: "Please send a certificate for the job at 14 Mill Lane showing the property owner as holder." This is the one Zap where an AI step earns its keep, because the details sit in sentences, not form fields. The Zap's job is to log and sort. It never issues.
Build it like this. The trigger is Gmail's New Labeled Email, watching a "Certificates" label that a mailbox rule applies to request messages. If you would rather not maintain a rule, the New Email Matching Search trigger takes a Gmail search such as subject:certificate instead. Then an AI by Zapier step pulls out the insured's name, the certificate holder, the holder's address, any wording the holder demands, the date needed and the policy line. The next step adds a row to a Zapier Table, and the last posts the row's link to the certificate team's channel.
Price per run: 3 tasks on the Standard tier (AI 1, Table row free, alert 1, plus one more action such as applying a Gmail label), or 7 on Premium. On Standard there are no tools, which suits extraction from a single email. Use the 1-task bring-your-own-key option if your agency has its own API account with an AI provider (billed by that provider, separately from any chat subscription) and wants an Advanced or Premium model without the multiplier.
Illustrative: 90 requests a month is 270 tasks on Standard and 630 on Premium. That 360-task gap is almost half of the 750-task plan on its own, from one dropdown.
A sample extraction, and what to fix in it
Prompt: From the email below, return JSON with insured_name, holder_name,
holder_address, special_wording, needed_by, policy_line. If a field is
missing write "NOT STATED". Do not guess. Do not summarise.
Output (illustrative):
{"insured_name": "the sender's company", "holder_name": "the property owner's company",
"holder_address": "NOT STATED", "special_wording": "additional insured,
primary and non-contributory", "needed_by": "Friday",
"policy_line": "general liability"}What you would fix: "needed_by" says Friday, not a date, so add the email's received date to the prompt and ask for a calendar date. Notice also that the model copied special wording the holder demanded. It has not checked whether the policy allows it. The certificate team does that check, which is why the Zap ends at an alert.
Zap 3: renewal reminders sixty days out
Renewals are where agencies keep or lose clients, and the reminder step is easy to forget when the office is busy. The Zap runs on a schedule. Schedule by Zapier's Every Day trigger fires each morning (it has an option to skip weekends), a search step finds policies renewing in 60 days, and a loop sends one task and one email draft per policy.
The detail that controls cost is on the search step. Set it to stop when nothing is found, and a quiet day costs no tasks at all; set it to continue when nothing is found and every empty day burns one. For the data source, a CRM with a renewal date field works, as does a Google Sheet that your AMS export refreshes. Looping is free, so only the actions inside the loop count.
Price per renewal: 2 tasks (create a follow-up task for the account manager, create a Gmail draft for them to personalise and send). Plus 1 task per weekday on which the search finds something.
Illustrative: 120 renewals a month is 240 tasks, plus about 22 searches, so 262. Drafts rather than sends keep a person in the loop, and the draft can pull the client's first name and policy type from the record. For the thinking behind what the reminder should say, see how to automate insurance renewals with AI.
A realistic mistake
One agency-style failure: the renewal date field holds text like "03/04" in one system and a true date in another, so the search matches nothing for a month and nobody notices, because a stopped search is silent. Add a weekly check Zap that counts renewals due and posts the number; a zero in a busy season is your alarm. The related guide to automations that break silently covers the pattern.
Zap 4: quote follow-up that stops itself
Most lost quotes are not refusals; the prospect forgot. The Zap watches for a deal moving to "Quoted" in your CRM, waits two days with a Delay step (free), then checks whether the deal is still at "Quoted". If it is, a draft follow-up appears in the owner's mailbox and a task is created.
The check matters for cost and for manners. After the Delay, a Find Record step re-reads the deal (1 task), and a Filter lets the run continue only if the stage is still "Quoted" (free). Deals that have moved on stop at the filter, so a prospect who already bought is never nagged.
Price per quote: 1 task if the filter stops it, 3 if it carries on (find, draft, task).
Illustrative: 60 quotes a month, with 40 percent already closed or declined by day two. That gives 60 find steps plus 36 runs that continue, each adding 2 tasks, so 60 + 72 = 132 tasks. A second follow-up at day seven doubles it to about 264, which is still modest. Write the drafts yourself in a template; if you ask an AI to personalise the opening line, add 1 task on Standard and keep it to the first sentence, with the person reading every draft.
Zap 5: naming and filing documents as they arrive
Attachments in a shared inbox pile up as "scan0034.pdf". The Zap's trigger is Gmail's New Attachment, narrowed to the label your filing rule applies (check the trigger's label and search options when you set it up). A Formatter step builds the filename from the email, for example the date, the sender's company and the first word of the subject, and a Google Drive step uploads the file into a client folder under that name. A final Gmail step applies a "Filed" label so nothing is processed twice.
The naming pattern is where the value lies. A rule such as 2026-11-04_[client]_[document type]_[policy number] only works if the pieces exist, so decide whether they come from the subject line (a convention your staff follow), from a form, or from an AI step. A Formatter text step can pull a policy number if your numbers follow a fixed pattern, at no task cost; an AI step is only needed when they do not.
Price per attachment: 2 tasks (upload, apply label). With an AI step on Standard to read the document type from the email body, 3.
Illustrative: 150 attachments a month is 300 tasks. A signed application and a driving-licence scan are different sensitivity levels, so send anything holding identity documents to a restricted folder with a separate Zap, and keep client files out of any AI step until your agency has decided what its AI tools may see.
The six-person agency, added up
Here is the whole set priced for an illustrative agency with 40 web enquiries, 90 certificate requests, 120 renewals, 60 quotes and 150 filed attachments a month.
| Zap | Monthly volume | Tasks per run | Tasks a month |
|---|---|---|---|
| 1. Web form to system | 40 | 2 | 80 |
| 2. Certificate inbox (AI Standard) | 90 | 3 | 270 |
| 3. Renewal reminders | 120, plus 22 searches | 2 | 262 |
| 4. Quote follow-up | 60 | 1 or 3 | 132 |
| 5. Document filing | 150 | 2 | 300 |
| Total | 1,044 |
On Premium AI the certificate row becomes 630 and the total 1,404. Either way the set overflows the 750-task plan and sits in the 1,500 step, which Zapier's pricing page lists at $39 a month billed annually or $58.50 billed monthly. If staff save around 4 minutes on each certificate, 6 on each form and 4 on each renewal, plus a few on the rest, that is in the region of 25 to 30 hours a month, so the set runs at roughly 35 to 40 tasks per hour saved, or about $1.30 to $1.60 of subscription per hour saved on annual billing. Those minutes are guesses; time your own team for a week before you trust them.
What happens when the task limit arrives mid-month
Zapier's help article describes two behaviours. If pay-per-task billing is on, extra tasks are billed at 2.5 times your base task rate on monthly billing or 1.25 times on annual billing, according to Zapier's pricing page, and usage stops at three times your plan's task limit until the next cycle. Zapier emails you at 80 percent of that pay-per-task limit. If it is off, Zapier holds new runs until the cycle resets, and you can replay held runs after upgrading. On the 1,500-task step billed monthly, the 2.5 times rate makes a busy month's overflow expensive, which is one more reason to bill annually once the volumes settle.
For an agency, held runs are the dangerous option: a certificate request that waits ten days is a broken promise to a contractor. Decide who reads Zapier's usage emails and who checks the Zap history when one arrives. Zapier also turns a Zap off automatically when it errors on 95 percent of its runs and has run more than 20 times in the past seven days, so a broken connection after a password change can quietly switch a Zap off.
Testing each Zap without spending tasks
Zapier's help article says testing steps in the editor does not use tasks, even when a test action really performs the action in your app. That makes the build stage free, with one trap: a tested Create Gmail Draft step really creates a draft, and a tested Create Applicant step really creates an applicant. Point every test at a dummy contact such as "Test Client" and delete the records afterwards, or the first real producer to open the system will find a made-up applicant.
After the Zap is live, check three things in the first week. First, open the Zap history and compare the number of runs with the number of real events: if 22 certificate emails arrived and the history shows 19, the label rule is missing some. Second, open each AI extraction and compare it with the email by eye for ten runs; extraction errors are rare but they concentrate in odd layouts such as forwarded chains. Third, check the task counter against your sum. If the real figure is higher than the table's, look for a step you counted as free that is not, such as a search set to continue when nothing is found.
A second realistic mistake: the forwarded chain
A contractor forwards an old email thread with three earlier requests inside it. The trigger fires once, the AI step reads the whole chain and returns the holder from the oldest request, not the latest. The row in the Table looks tidy and wrong. The fix is a line in the prompt, "use only the most recent message in the thread, ignore quoted text below it", and a column in the Table that stores the email subject and received time so the certificate team can open the source in one click before issuing anything.
Who owns the Zaps once they are running
Five Zaps is a small estate, but it still needs an owner. Zapier's Free and Professional plans allow one user and Team allows 25, so on Professional the Zaps live under one login. If that login belongs to the person who built them and she leaves, the connections go with her. Create the account on a role address that more than one trusted person can reach, write a one-page note listing each Zap, its trigger, its task cost and who to tell when it fails, and put the monthly task total on the agenda of one regular meeting.
Also decide what the Zaps are allowed to touch. A Zap that files attachments reads every document in a labelled mailbox, which can include identity papers and medical details, and a connection to an AI step sends the email text to an AI provider. Settle those questions with your own compliance contact first, and keep a short list of what each Zap reads. That list is also the answer when a client asks where their details go.
Where I would start, and when Zapier is the wrong tool
Start with Zap 2 on the Standard tier, because certificate requests are the most repetitive job and the easiest to audit. Run it for a fortnight with the alert going to one named person, then add Zap 1. Leave renewals until your renewal date field is clean.
Zapier is the wrong choice when volume grows past a few thousand tasks and a flat per-run price would be cheaper; see when Zapier gets too expensive and the comparison with Make and n8n. If your AMS already automates reminders natively, use that. And before you connect any system holding client details, work through the questions to ask about your agency system.
Zapier questions agencies ask before they start
Can Zapier connect to my agency management system?
Only if the system has a Zapier app, so check its Zapier listing first. EZLynx has one, with actions such as creating an applicant with an opportunity, a note or a document. When I checked, Zapier listed no Vertafore app. Without an app you can fall back on a CRM, a spreadsheet or email-in.
Should Zapier ever send a certificate by itself?
No. Let the Zap log the request, pull out the details and notify the person who issues certificates. A certificate describes cover, so a licensed or authorised team member should check the holder wording against the policy before anything leaves the agency.
What happens when we run out of tasks?
If pay-per-task billing is off, Zapier holds new runs until the cycle resets, and held runs can be replayed after you upgrade. If it is on, extra tasks cost 2.5 times your base task rate on monthly billing or 1.25 times on annual billing, until usage reaches three times your plan's limit. Decide which you want before a busy renewal month.
Do I need the AI step for any of these?
Only for the certificate inbox, where it reads free-text emails. The other four run on fixed fields and cost nothing extra. If you add an AI step, check which model tier it is set to, because the tier changes the tasks per run from 1 to 5.
Further reads
- Best AI Tools for Insurance Agents: Seven for Quotes, Renewals and Calls — Compare the AI tools that sit alongside these Zaps.
- How to Add AI Steps to Zapier: Classify, Summarise, and Draft — Set up the AI step used in the certificate Zap.
- AI Submission Intake: Stop Re-Keying Data Into Insurer Portals — Stop re-keying data into insurer portals.
- What Does AI Cost a Small Insurance Brokerage in Year One? — Put Zapier next to the other year-one costs.
- Automation Audit: Find the Zaps and Scenarios Nobody Owns — Find Zaps nobody owns once you have several.
- HubSpot for Insurance Agents: Pipeline, Renewals and What Breeze Adds — A CRM route for the renewal and quote Zaps.
- Compliance Calendar: Track Licences, Insurance and Certificates — Track licences and expiry dates alongside certificates.
- AI Answering Service for Insurance Agents: Claims Calls and Quote Leads — Feed phone enquiries into the same intake form.
- Zoho CRM for Insurance Agents: Policies, Renewals and Zia — A step-by-step Policies module and renewal rules in Zoho CRM, the edition limits that matter, and what Zia adds for an insurance agency.
- AI Chatbot for an Insurance Agency: Quote Requests, Not Advice — Quote-request-only scope for an agency website bot: fields to collect, replies that refuse, and a hand-off packet for the licensed agent.
- ChatGPT for Insurance Agents: Ten Safe Uses and Three to Avoid — Ten uses an agency owner can approve for ChatGPT, and three to ban outright, with the client-data and policy rules that go with them.
- Insurance Agency SOPs With AI: Turn Routines Into Procedures — Record a routine, draft its decision points with AI and publish an SOP that the next account handler can actually follow.
- Can You Automate Certificate of Insurance Requests Without E&O Risk? — Step-by-step E&O guardrails for automating certificate of insurance requests: triage, standard wording, holder checks and approval rules.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Zapier's help article on how task usage is measured, its AI by Zapier model tier pricing page, its auto shut-off article, its pricing page, and the Zapier listings for EZLynx, Gmail and Schedule by Zapier, all read on 4 November 2026.