Every morning you check your inbox or website forms, copy names and emails into your CRM, then type "New lead in" to Slack. That's drudgery, and it's easy to miss when you're out for lunch.
So what is Zapier? It's a service that connects the apps you already use so one event triggers another action, without any code.
What does Zapier actually do?
Zapier asks your apps to follow a simple command: "When this happens, do that." Each of these workflows is called a trigger and one or more actions.">Zap. A Zap has a trigger (the starting event) and one or more actions (what happens next). The trigger might be a new spreadsheet row or a form submission. An action could be creating a contact, posting to chat, or updating a record.
Most of this requires no coding. You pick apps and steps from menus, then map which data goes where. The real work is deciding what should happen, because Zapier will execute whatever you tell it with great consistency.
Zapier positions itself as a platform for building AI workflows across 9,000+ apps, claiming use by 3 million+ businesses. Those are vendor figures, so treat them as such rather than an independent audit. The useful part is the breadth of connections: if you use mainstream SaaS tools, there's almost certainly a step available in Zapier today.
What does a real Zap look like, step by step?
Let's walk through one that covers most enquiries: a new website form entry should create a contact in your CRM and post a message to Slack. This is an illustrative example, not a client case.
The trigger and the actions
First you connect your form app as the trigger: "new form entry." Then add action one: "create contact" in your CRM. Action two: "post message" to a Slack channel. You map fields from the trigger into each action. The name field becomes first and last names, the email becomes the contact address, and their budget answer can go straight into the Slack message so sales has context without clicking through.
Testing before you switch it on
When you test your Zap, Zapier performs the real action in your connected app. In our example that means a live contact appears in the CRM and a live message drops into Slack. So use fake test data: a name like "Test User" and an email address you control. If you forget to clean up, you've just created a phantom lead that will sit in your pipeline until someone notices.
What permissions you are granting
For each app you connect, Zapier asks for a general set of permissions rather than one narrow scope. Zapier then only takes the actions your Zap needs. It's how you stay flexible and add steps later without reconnecting, but it's worth understanding what access you've given. If an app holds sensitive data, read which scopes you're approving before you click yes.
How do Zapier tasks and pricing work?
This is where owners get burned, so let's be precise. A task is any successful action that runs in Zapier, and only successful actions count toward your task usage. Triggers never use tasks: a Zap's first step is always a trigger and it doesn't add to your bill. When a Zap runs, each successful action it completes counts as one task.
Working the example into numbers
Our form-to-CRM-to-Slack Zap has two actions. So every single form entry that triggers it consumes two tasks. If you get 30 enquiries in a month, that's 60 tasks from this one Zap alone. Add another Zap for updating your project board on deal stage changes (one action per update), and each move adds another task.
Do the arithmetic over a quarter and the volume starts to look less trivial.
What does not count as a task
Polling doesn't use tasks: if a Zap checks an app every two minutes, it completes over 20 thousand polls per month and Zapier doesn't charge for those events. Tables are included in every plan, and neither their triggers nor actions count as tasks; they're free. Agents use a separate activity quota rather than your task allowance.
The steps that change the math
Not every action costs one task. Code steps run at one task per run with standard runtime, but more tasks if you extend the runtime. AI steps depend on the model tier you select, so a step that classifies an email with a heavier model will cost differently than a lighter one. And from 1 December 2026, Next Gen Zaps and the Zapier SDK also use tasks.
We don't quote plan prices here because they change; check Zapier's pricing page for current figures at the time of writing. The point is that the unit driving your bill is the successful action, multiplied by how often it fires.
What happens when you hit the task limit or a Zap stops?
Zapier gives you two different outcomes once you reach your plan's ceiling, and neither one is obvious until it happens to you.
Overage charges
If pay-per-task billing is on, extra tasks are charged once your plan reaches its task limit. That cap sits at 100% of pay-per-task billing tasks, which Zapier defines as equivalent to three times your selected plan's task limit. In practice that means you can be billed for up to double the number of tasks in your base plan before it stops.
Held runs
If pay-per-task is off, or you hit that three-times cap, Zapier holds any new Zap runs until your billing cycle resets. Your forms are still coming in. But your CRM isn't getting the contacts. Slack isn't pinging sales.
Nothing errors out; it just quietly stops doing the thing you hired it to do.
The silent-failure risk
This is the one that keeps owners up at night, and owners raise it in online communities. An automation can stop working for a reason as mundane as an app changing its API or someone renaming a field, and if nobody is watching the task log you won't find out until a lead goes missing three days later.
Our advice is blunt: name one person who owns the automations, set up notifications on failures, and review the logs at least once a month. If that person leaves, write down what they know before they go.
What is Zapier good for, and what should you not automate with it?
Zapier's own guidance is that the best candidates are deterministic processes: tasks like creating the same types of content, replying to standard messages, or extracting similar data from emails. We agree with that framing. If the input-to-output mapping is consistent and you can describe it in one sentence ("when X happens, create Y with Z"), it's a good fit.
Where it shines
In our experience, frequent tasks that currently cost someone fifteen to thirty minutes a day are ideal. Moving data between two apps that have no native integration is exactly what Zapier was built for. Manual work that doesn't scale because there's only one person who knows how to do it becomes repeatable and owned by the system once it's automated.
Where to stop and think first
Don't automate a judgement call. If your sales team has to decide whether an enquiry qualifies before it goes into the pipeline, you need a human in that loop or a very well-defined rule set.
Also, don't automate a messy process either. If the current workflow involves four exceptions, two "depends on" situations and one phone call to a supplier, Zapier will faithfully encode your mess at machine speed. Write the process down first, agree what the happy path looks like, then build.
In practice · Case study
Workflow Automation
Giving the editorial team their time back — permanently.
Read the case studyWhen should you look at Make or n8n instead?
Here's the honest trade-off. Zapier's strength is ease of use and breadth: 9,000+ connected apps means almost anything mainstream has a step ready to go. You can build a working automation in an afternoon without touching code. That convenience comes with a price structure that scales with volume: every successful action is a task, and tasks are what you pay for.
Make and n8n price differently, and our comparison pages cover how. The cost to you is setup time: both require more thought about routing, error handling and where things live. If you have a technical person in-house who wants control over that, the switch makes sense.
We compare them properly in two places: our Zapier vs Make comparison walks through pricing models, complexity trade-offs and when each one wins. Our Zapier vs n8n comparison does the same for self-hosted options, including what "owning your infra" actually means in practice. If you're curious about what n8n is before deciding it's relevant to you, start with what n8n is.
Our usual steer to clients: if you have a modest number of active Zaps and moderate volume, Zapier is the right tool. Don't over-engineer a problem that will be solved by one well-built workflow. If your task bill has grown past what feels reasonable and your workflows are getting complex with branching logic or lots of retries, sit down with both pricing models on paper before you renew.
If you want someone to look at your current automations and tell you whether they should stay on Zapier or move, that's exactly what we do in our automation service. Bring the list of Zaps, the monthly task count, and the two things that have broken this quarter, and we'll give you a straight answer.
Key terms
- Zap
- Zapier's name for one automated workflow, made of a trigger and one or more actions.
- trigger
- The event that starts a Zap, such as a new form submission or a new row in a spreadsheet.
- action
- A step a Zap carries out after its trigger fires, such as creating a contact or posting a message.
- task
- The unit Zapier bills on. Each successful action counts as one task, while triggers do not.
- Polling
- How Zapier checks an app at set intervals for new events. Zapier does not charge tasks for those checks.
Frequently asked questions
What is Zapier used for?
Does Zapier need coding?
How much does Zapier cost?
What counts as a Zapier task?
What happens if I go over my Zapier task limit?
Is there a cheaper alternative to Zapier for a non-technical owner?
Sources
- How is task usage measured in Zapier?, Zapier (accessed 11 Nov 2026)
- Get started with Zapier, Zapier (accessed 11 Nov 2026)
- Zapier homepage, Zapier (accessed 11 Nov 2026)