Zapier for Accountants: Five Automations for Intake and Reminders

Five Zaps cover most of an accounting practice's intake and reminder admin: enquiry to client record, document request pack, missing-documents chase, inbox attachment sorting and deadline reminders. In the worked example below they use roughly 720 tasks a month without AI and 1,320 with an AI sorting step, so the plan choice turns on that one step.

Zapier bills by tasks, meaning each successful action step, not by Zaps. Triggers and filters are free, so the cost of an automation is the number of action steps in it, multiplied by how often it runs. Everything below is priced that way, so you can swap in your own volumes.

Follow me on Instagram@sagnikteaches

How the task maths works, in four rules

Zapier's pricing and help pages set out the counting. Learn these four rules and you can price any Zap on a napkin.

Connect on LinkedInSagnik Bhattacharya

1. Triggers never use tasks. A Zap that starts when a form arrives costs nothing until it does something.
2. Filter, Paths, Formatter and Delay steps do not use tasks. On paid plans a Delay can hold a run for up to 30 days (Delay is not on Free), which makes reminders cheap.
3. Every successful action step uses one task or more. Failed actions are not counted. Creating a record, sending an email, adding a row and uploading a file are one task each. A search step costs one task when it is set to carry on even if nothing is found, and none when it is set to stop.
4. An AI step uses one, three or five tasks, depending on the model tier chosen (Standard, Advanced or Premium), and one if you bring your own API key for an Advanced or Premium model. Zapier's model-tier help article says new AI steps on paid plans default to Premium, which is five, and each tool call the step makes adds the tier rate again. A Free account cannot publish a Zap with an AI by Zapier step at all. The pricing page itself does not list the multipliers, so I price AI steps at five; check the tier shown in each step before you rely on the sum.

The Free plan gives 100 tasks a month and two-step Zaps only, with no filters or paths, so it cannot run any of the five below as written. Professional starts at $19.99 a month billed annually ($29.99 billed monthly) for 750 tasks; 1,500 tasks is $39 annual or $58.50 monthly. Those are list prices from Zapier's pricing page; check them before you buy. If you want to understand how those AI steps are built, how to add AI steps to Zapier covers set-up.

Subscribe on YouTube@sagnikteaches

The practice used for every sum

Say a six-person practice with about 150 clients. In an average month it receives 30 new enquiries, signs 10 of them as clients, has roughly 40 clients waiting on missing documents, receives about 120 emailed attachments, and sends about 100 deadline reminders. Those figures are illustrative; swap in your own from last quarter's inbox.

The first total fits the 750-task tier with only 28 tasks to spare, which is thin: a filing month that doubles Zap 3 adds about 150 tasks and tips the practice over, so either price the 1,500 tier for peak months or switch pay-per-task on and watch the bill. The second total needs the 1,500 tier. The AI step therefore costs $19.01 a month more on annual billing ($39 less $19.99) or $28.51 on monthly billing, before you count the setup time. The rest of this tutorial explains where each number comes from.

Zap 1: enquiry form to client record and acknowledgement

The trigger is a new submission on your website's enquiry form (or a new row in the spreadsheet it writes to). A Filter step rejects obvious spam, such as submissions with an empty email or a message containing links. Then three actions run: create the contact in your CRM or practice-management tool, send a short acknowledgement email, and create a task for the partner who handles new enquiries.

Task count: three per enquiry, because the trigger and filter are free. At 30 enquiries that is 90 tasks. The spam filter earns its place here: if the form also collects 10 junk submissions a month on top of the 30 real enquiries, stopping them at the free filter saves 30 tasks (10 runs at three tasks each) and keeps junk out of the client list.

The acknowledgement email to use

Subject: Thanks for getting in touch

Hi [first name],

Thank you for your enquiry. A partner will reply within one working day to arrange a short call. In the meantime, please do not send tax IDs, bank details or passwords by email; we will give you a secure upload link once we have agreed the work.

[your name]

That last line matters. An automated acknowledgement that invites sensitive documents by email creates the very problem the later Zaps then have to clean up. Pair it with engagement wording you have already settled; AI engagement letters for accountants covers drafting the scope clearly.

Zap 2: document request pack when an engagement is signed

The trigger is a deal or client moving to "Engaged" in your CRM, or a signed engagement letter landing in a watched folder. Four actions follow: create a client folder in your document store, create an "Uploads from client" subfolder inside it, email the client the checklist and the secure upload link, and create a staff task to check the folder after five days.

Task count: four per new client. At 10 new clients that is 40 tasks. This Zap is cheap because it fires only on conversion, not on every enquiry. The checklist should be specific to the engagement type. A filled-in example for a sole trader's year-end return:

Documents we need by [date] (illustrative checklist)
1. Bank statements for the full year (all accounts used for the business)
2. Sales invoices issued and a list of money received but not yet invoiced
3. Purchase receipts or a summary by category
4. Last year's return, if prepared elsewhere
5. Details of any asset bought or sold over the year
Upload them to the folder in this email. Anything you cannot find, tell us which and we will advise.

The most common failure is a client who forwards documents by email anyway. That is what Zaps 3 and 4 are for. If your practice already tracks leads and onboarding in a CRM pipeline, check what that CRM's own workflows can do before you build this Zap.

Zap 3: the missing-documents chase, with delays instead of tasks

This is the Zap that returns the most time, and Delay steps make it cheap. The trigger is a client record moving to "Waiting on client". Then: Delay for three days (no tasks), look up the record to see whether the status is still "Waiting" (one task), and if so email a polite nudge (one task). Delay for four more days, look up again (one task), send a firmer second reminder (one task), and create a phone-call task for staff (one task).

The status check is a lookup action, so it costs a task each time it runs. A filter on the trigger data alone cannot know what happened during the delay. Two outcomes:

• Client responds after the first nudge: three tasks (first look-up, first email, then the second look-up, after which the filter stops the run).
• Client ignores both: five tasks (two look-ups, two emails and the call task).

Say 40 clients enter the state in a month and 60 per cent respond after the first reminder. Every client gets the first look-up, the first email and the second look-up: 40 × 3 = 120 tasks. The 16 who stay silent add the second email and the call task: 16 × 2 = 32. That is 152 tasks. In a busy filing month, assume double.

Before and after: the chase email

A typical manual chase reads: "Hi, just checking if you have those documents yet?" It prompts a reply of "which documents?". The automated version should list what is still missing. Pass the missing items from your CRM field into the email:

Hi [first name],

We are still waiting for: [missing items].
You can upload them here: [secure link]. If any of these do not exist, reply and tell us which, and we will note it on file.

[your name]

If you want AI to personalise the tone, do it as a draft step that saves to a staff queue, not a step that sends. That keeps a human on the message that goes to the client.

Zap 4: sort emailed attachments, with and without AI

The trigger is Gmail's "New Attachment" trigger, which lets you set a label or mailbox and search keywords, such as an inbox label your staff apply or a client-uploads address. A cheap version has two actions: upload the file to the client's folder (one task) and add a row to a log sheet (one task). That is two tasks per attachment, or 240 for 120 attachments.

The AI version adds a classify step between trigger and upload: "Is this a bank statement, invoice, receipt, payroll report or other?" The classification decides the sub-folder and fills the log's category column. At five tasks for the AI step, the Zap runs seven tasks per attachment, or 840 a month. At one task with your own API key it would run three, or 360, though that needs an account with the AI provider and its own bill.

Sample classification prompt and output

Classify this attachment by its file name and the email subject only.
Reply with exactly one word from: statement, invoice, receipt, payroll, tax-notice, other.
File name: {{attachment_name}}
Subject: {{email_subject}}

Illustrative outputs: "Bank_Mar.pdf" with subject "March bank docs" returns "statement". "IMG_4421.jpg" with subject "scan" returns "other". The second is where the human step matters: "other" items go to a staff folder for filing by hand. Weigh whether the AI step is worth $19 to $28 a month in plan cost against the minutes of manual sorting. At 120 attachments and 30 seconds each by hand, sorting is 60 minutes a month; if your name patterns are consistent enough for keyword rules to cover most, the cheap version wins.

Keep the AI step to file names and subjects at first. Sending document contents to an AI provider is a data-handling decision for your engagement letter and privacy notice, not a Zap setting. The accountants' AI risk checklist lists the error points to cover.

Zap 5: deadline reminders from your calendar

The trigger is a calendar event that marks a client deadline, such as an extension date or a payment date. Two actions: email the client a plain reminder (one task) and notify the staff owner in chat or by email (one task). At 100 reminders a month that is 200 tasks.

Use a trigger that fires ahead of the event, not at its start. If the deadlines sit in Google Calendar, Zapier's Event Start trigger fires a specified amount of time before an event starts and takes an optional search term, so a word such as "DEADLINE" in the event title keeps ordinary meetings out. If your calendar app has no such trigger, create the calendar events dated a week ahead and name them clearly.

A realistic mistake: a Zap reminds a client about a deadline that moved. This happens when the reminder is built as "new event, then Delay until a week before": the calendar event was updated, but the run was already waiting in the Delay step with the old date. Avoid it by using a trigger that fires before the event where you can, keeping any delays short (days, not weeks) and adding a look-up before sending if deadlines move often. That look-up adds a task per run, so on 100 reminders it raises the Zap from 200 to 300.

Which plan fits, and the shared-account catch

Professional is a single-user plan on Zapier's account-access notes; Team allows up to 25 users. A practice where several people build and maintain Zaps should price Team, which starts at 2,000 tasks a month at $69 billed annually ($103.50 billed monthly) on the pricing page. That is a different order of cost from the $20 to $40 figures above, so decide who owns the Zaps early. If a single login belongs to one person and they leave, the Zaps and their connections go with them. The automation audit is the habit that stops this.

If you hit your task limit and pay-per-task is off, usage stops until the next billing cycle. Zapier's pricing page says that with pay-per-task on, extra tasks are charged at 2.5 times the base rate on monthly plans and 1.25 times on annual plans, and usage still stops once it reaches three times your task subscription. I could not verify the base rate in dollars, so check your billing page. Put a calendar reminder to check usage mid-month in the first quarter.

Building Zap 3 in the editor, step by step

Zap 3 is the one to build first, so here is the order of steps in the editor. Allow about 45 minutes the first time.

1. Trigger: choose your CRM's "record updated" or "stage changed" event and test it with a real record.
2. Filter: continue only if the stage equals "Waiting on client" and the missing-items field is not empty. This costs nothing and stops half-built runs.
3. Delay for: three days. Zapier holds the run; no tasks are used.
4. Find record: look the client up again by ID. This is the one task that tells you whether anything changed.
5. Filter: continue only if the stage is still "Waiting on client".
6. Send email: use the chase wording above with the missing-items field merged in.
7. Repeat the delay, look-up, filter and email for the second reminder, then add the staff task.

Test with a dummy client whose email is your own, and shorten the delays to one minute for the test. Put the real delays back before you switch the Zap on, and check the Zap history the next morning to see that the delay steps show as held, not failed.

Three practices, three different bills

The five Zaps cost different amounts depending on the practice, which is why the worked example above should be treated as a method, not a quote.

• A two-person bookkeeping practice with 40 clients. Perhaps 8 enquiries, 3 new clients, 15 clients to chase and 40 attachments a month. Zap 1: 24 tasks. Zap 2: 12. Zap 3: about 57. Zap 4 without AI: 80. Zap 5 on 30 reminders: 60. Total about 233, which fits the 750 tier with room for growth, though at that volume you could trial the Free plan on one two-step Zap only to see how the trigger behaves.
• A twelve-person practice with 600 clients. Roughly 100 enquiries, 30 new clients, 150 chases, 500 attachments and 400 reminders. Zap 1: 300. Zap 2: 120. Zap 3: about 570. Zap 4 without AI: 1,000; with AI at five: 3,500. Zap 5: 800. Without AI the total is about 2,800, needing the 5,000 tier at $89 annual or $133.50 monthly on Professional; with AI the total is about 5,300, which tips into the 10,000 tier at $129 or $193.50. A practice this size will usually want Team, where the same two tiers are $119 and $169 a month billed annually. At this size, where the AI step adds $40 or more a month, a dedicated document tool may beat a Zap; native integrations versus Zapier sets out that call.
• A seasonal tax-return practice. Eight quiet months at 150 tasks, four busy ones at 1,200. Choose the tier for the busy months and downgrade carefully: Zapier's pricing FAQ says downgrades take effect at the end of the current billing cycle, so a mid-season change does not help.

Checking each Zap worked after the first fortnight

Open the Zap history and read ten runs of each Zap. For every one, ask four questions: did the right client receive the right message; did the task land with the right person; was the step count what you priced; and did any run error silently. Then compare your actual month's usage with your estimate. If actual usage is over 20 per cent above the estimate, find the Zap that surprised you before it eats the allowance. The usual culprit is a trigger that fires on every update of a record rather than on one specific change.

Failure modes that cost money or trust

• A Zap that errors every run. Zapier turns a Zap off automatically when 95 per cent of its runs error and there are more than 20 runs in seven days. Until then it silently sends nothing. Turn on error emails and read them. How to stop automations breaking silently covers the checks.
• Duplicate contacts. A returning enquirer creates a second record. Use a "find or create" step where your CRM offers one, and count it as its own task.
• Loops that send twice. Two Zaps listening to the same label both email the client. Give each trigger a distinct label.
• Task creep in the busy season. Year-end and the weeks before filing deadlines can double Zap 3 and Zap 5. Price the peak month, not the average.

Which of the five to build first

Rank by time saved per task spent. Zap 3 usually wins: chasing documents is the repetitive job staff dislike most, and its Delay steps keep the cost low. Zap 1 is second because it protects the first impression. Zap 5 is third. Zap 2 is a quick win but only fires ten times a month. Zap 4 comes last, and only with AI after the cheap version has run for a month and you know what share of attachments the keyword rules miss.

Build one, run it for two weeks, and read the task history before building the next. The history shows the real task count per run, which is more reliable than my estimates. If you would rather map this with someone, that is what my AI implementation consultation covers, at the contact page.

Questions accountants ask about Zapier costs and safety

How many Zapier tasks does a small practice need?

In the worked example here, five Zaps for a practice taking 30 enquiries and 10 new clients a month came to about 720 tasks without AI and about 1,320 with an AI sorting step. Your numbers depend on volume and on how many steps each Zap has, so count steps per run before choosing a plan.

Do triggers and filters count as tasks?

No. Zapier's task guidance says triggers, Filter, Paths, Formatter and Delay steps do not use tasks, while each successful action step does. Failed actions are not counted. That is why a filter placed early in a Zap is a free way to stop unwanted runs from using your allowance.

Can the whole practice share one Professional plan?

Zapier's account-access notes say Professional has one user, and Team allows up to 25. If several staff need to edit Zaps, price the Team plan, which starts at the 2,000-task tier. Check the current plan page before you commit.

Should client tax documents go through an AI step?

Only after you have checked your engagement letter, privacy notice and the AI provider's data terms. Start by classifying file names and email subjects rather than document contents, and keep identity numbers and full bank details out of any AI step.

Further reads

• When Does Zapier Get Too Expensive? Finding the Tipping Point — Where the task bill tips over.
• Best AI Note Taker for Accountants: Which Fits a Small Practice? — Costs and record-keeping for meeting notes.
• Dext Pricing for Accountants: Essentials, Advanced and AI Assist — A built-in alternative for receipts and documents.
• Is Zapier Safe for a Law Firm? Five Automations and Five to Avoid — A confidentiality-first view of the same tool.
• Zapier for Photographers: Automate Enquiries, Contracts and Reminders — Another worked task count for enquiries and reminders.
• AI Chatbot for Accountants: Website FAQs Without Giving Tax Advice — Handling enquiries before they reach a form.
• HubSpot for Accounting Firms: Lead Tracking and Onboarding Pipelines — What a CRM pipeline handles without a Zap.
• Power Automate for Accountants: Flows for Documents and Approvals — Route client uploads and manager sign-off with two auditable flows, then check the connector and credit costs before buying.
• What Is Automation in Accounting? Bank Feeds, Capture and AI Agents — What accounting automation includes, which parts are plain rules and which need AI, with a month-end example and the checks that stay manual.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Zapier pricing page and FAQ; Zapier help-centre articles on task usage, Delay, AI by Zapier model-tier pricing and Zaps that error; Zapier's Gmail and Google Calendar app listings.