Integration · Automation
Zapier automation, and when task volume says it is time to move
Zapier is often the right first tool: quick to set up, easy for a non-developer to own and connected to most SaaS apps. We build Zaps that stay readable, count the tasks before you commit, and tell you plainly when the volume has outgrown it.
Zapier
Automation
Access
Authentication and least-privilege scopes
App connections authorised inside your Zapier account, OAuth or API key per app, shared through team folders
- crm: one pipeline
- forms: one form
- webhooks: catch hook + secret
- sheets: one file
Zaps live in your account. We work as a member of your team account and leave it at handover.
Objects
What we read and what we write
Trigger (polling or instant)
Read: YesWrite: No
Polling checks the app on a schedule; instant triggers receive a push.
Action step
Read: NoWrite: Yes
Each successful action uses one task.
Filter or Paths step
Read: YesWrite: No
Decides whether and where a run continues, without using tasks.
Catch hook (Webhooks by Zapier)
Read: YesWrite: No
Receives JSON from your systems; a secret field is checked first.
Zap run history
Read: YesWrite: No
Per-step input and output, used to replay held or failed runs.
Records in your apps
Read: YesWrite: Yes
Contacts, rows, tasks and messages written by actions.
Data flow
System of record and write-back
Zapier passes data from the trigger app to each action app in order. It keeps run history so a run can be inspected or replayed, while your apps keep the records.
- Trigger: instant where the app pushes events, polling where it does not.
- Filter: stops runs that should not continue, before any task is used.
- Actions: each successful step writes to an app and uses one task.
- Errors: failed steps show in run history and can be replayed after a fix.
- Form app
- Payment app
- CRM
- Team chat
- Spreadsheet
Worked example
Zapier in a build
| Criterion | Lead alert | Order sync | Ticket enrichment |
|---|---|---|---|
| Runs per month | 300 | 6,000 | 40,000 |
| Action steps that run | 2 | 4 | 6 |
| Tasks per month | 600 | 24,000 | 240,000 |
| Trigger type | Instant | Instant | Polling |
| What we would do | Build it in Zapier | Zapier works; price n8n alongside | Price n8n or a code service first |
Sample workflows
What teams build with Zapier
Pattern 01
New lead to CRM and owner alert
A form submission creates the CRM contact, assigns an owner by region and posts a summary to the team channel. A filter drops test and spam entries before any task is used.
Pattern 02
Payment to onboarding checklist
A successful payment adds the customer to the onboarding sheet, sends the welcome email and opens the first task for the account owner.
Pattern 03
AI brief for inbound requests
A model step turns a request into a short brief with the open questions listed. A person reviews it before anything goes to the customer.
Task volume
Estimate your Zapier tasks
Move the sliders to match one Zap. Only action steps that actually run use tasks.
Tasks per month for this Zap
24,000
MiddleZapier still works. Price n8n alongside it before you add more Zaps like this one.
Sample math, not a price. The bands are our planning rule of thumb; check Zapier’s pricing page for what your plan includes.
Failure handling
What breaks, and what the build does about it
A burst of trigger data arrives at once
Flood protection holds the runs so you decide whether to send them. We check held runs after imports and bulk edits.
The plan runs out of tasks mid-cycle
New runs are held, not lost, until the cycle resets or the plan changes. We review task use per Zap each month so the limit is never a surprise.
An app changes a field or a token expires
The step errors and shows in run history with its input. Once the connection is fixed, we replay the affected runs.
Fit · Zapier
When it is the wrong choice
- Runs per month times action steps lands in the tens of thousands of tasks or more. Price n8n or a small code service first.
- The workflow needs loops over large lists, deep branching or custom code in most steps.
- Data must stay in your own network or region. Zapier is a hosted service.
Alternatives worth pricing
Higher volume, self-hosting and code steps, with workflows you can still read on a canvas.
Branching scenarios with routers and per-module error handlers.
Very high volume or logic that needs tests; see the side-by-side comparison.
Where it is used
Related use cases, services and guides
Limits
Limits and common errors
A task is a successful action. Triggers, Filter and Paths steps, steps that error or halt, steps that never run and several built-in utilities (Formatter, Delay, Looping and others) do not use tasks.
Source: Tasks in Zapier (opens in a new tab) · Zapier Help Center · accessed
Without pay-per-task billing, reaching the task limit holds new Zap runs until the billing cycle resets; held runs can be replayed later.
Source: Tasks in Zapier (opens in a new tab) · Zapier Help Center · accessed
Polling triggers check every 1 to 15 minutes per active Zap, depending on the plan. REST hook triggers run in near real time, and polling data is deduplicated.
Source: Trigger (opens in a new tab) · Zapier Platform Docs · accessed
Flood protection holds runs when a trigger check returns too many steps (100+), so you can choose whether to run them; no data is lost.
Source: How to troubleshoot held Zap or step runs (opens in a new tab) · Zapier Help Center · accessed
Security
Security notes
- Catch hooks verify a shared secret in the payload before the first action runs.
- Each app connection uses the narrowest access the app allows and belongs to your team account.
- Zaps that handle personal data are listed with what they store, so run history can be reviewed and cleared.
FAQ
Frequently asked questions
How does Zapier count tasks?
A task is a successful action step. Triggers, Filter and Paths steps, failed steps, steps that never run and several built-in utilities do not use tasks. Multiply runs per month by the action steps that actually run to estimate your usage.
At what point does Zapier stop being the cheaper option?
There is no single number, because it depends on your plan and on how many action steps each run uses. Once the estimate reaches tens of thousands of tasks a month, we price the same workflow on n8n and as a small service, and put both totals in writing.
Can you take over Zaps that someone else built?
Yes. We start with an audit of what each Zap does, what it touches, where it fails and how many tasks it uses. Then we fix, merge or retire Zaps before adding anything new.
Do instant triggers use fewer tasks than polling triggers?
Neither uses tasks; triggers never do. The difference is delay: polling checks on a schedule set by your plan, while an instant trigger fires when the event happens. We use instant triggers wherever the app offers them.
Can a Zap call an AI model safely?
Yes, through built-in AI steps or a webhook to a model API. The model’s output stays out of customer-facing actions until a filter or a person has checked it.
Next step
Have a workflow in mind? Let’s scope it together.
Book a free 30-minute strategy call. Bring one process you want to automate and we will talk through scope, integrations and a sensible first step.
Free 30-minute call · no commitment