Your first Zapier workflow takes about twenty minutes and costs nothing to build. The part nobody tells you is what it will cost to run — because Zapier bills one task per action step, so the workflow you build in this guide consumes two tasks every time it fires, not one.
This walkthrough builds a real automation end to end — a form submission landing in a spreadsheet and pinging you — and shows the task meter running alongside it, so you finish knowing both how to build a Zap and what your plan will actually cover.
Key takeaways
- A Zap is a trigger plus one or more actions. The trigger is free; every action step costs one task.
- The free plan is 100 tasks a month and two-step Zaps only — that step limit stops you before the task count does.
- Build it, then test it with real data before turning it on. Zapier’s test step uses live records from your app.
- Add the error notification. Zaps break silently when a connection expires, and you won’t notice for weeks.
- Count your steps before choosing a plan. A five-action Zap running 200 times a month is 1,000 tasks.
What Is a Zap, Exactly?
A Zap is one trigger and one or more actions. The trigger is the event that starts it — a form submitted, an email received, a row added. The actions are what happens next, in order. That’s the entire model, and everything else is configuration.
| Part | What it does | Costs a task? |
|---|---|---|
| Trigger | Watches an app for an event | No |
| Action | Does something in another app | Yes — one each |
| Filter | Stops the Zap if a condition isn’t met | No |
| Formatter | Reshapes data (dates, text, numbers) | Yes |
| Paths | Branches into different action sets | Actions inside still count |
| Delay | Waits before continuing | Yes |
Use filters early and often. A filter placed as step two that stops 70% of runs saves you every action step that would have followed. Placed last, it saves nothing.
What Will You Build?
A form submission that lands in a spreadsheet and sends you a notification. It’s the canonical first automation because every business has some version of it, and it exercises a trigger plus two actions — enough to learn the model without getting lost.
| Step | App | What happens | Task cost |
|---|---|---|---|
| Trigger | Your form tool | New submission received | 0 |
| Action 1 | Google Sheets | Add a row with the submission | 1 |
| Action 2 | Email or Slack | Notify you with the details | 1 |
| Total per submission | 2 tasks | ||
How Do You Build It, Step by Step?
Six stages inside Zapier’s editor. Work through them in order and don’t skip the testing at each stage — Zapier tests with real data from your account, which catches field-mapping mistakes immediately rather than in production.
1. Create the Zap and pick your trigger app. From your dashboard, create a new Zap. Search for your form tool and select it. Choose the trigger event — usually “New Form Submission” or similar wording.
2. Connect the account. Zapier will ask to authorise access. This opens your form tool’s login and asks you to grant permission. Do this once per app; it’s reused across every future Zap.
3. Test the trigger. Zapier pulls a recent real submission. If nothing comes back, submit your own test entry in the form first, then retry. Don’t continue until you see real data — you need those fields in the next step.
4. Add the first action. Choose Google Sheets, then “Create Spreadsheet Row”. Pick your spreadsheet and worksheet, then map each column to a field from the trigger data. This mapping is the part that matters: you’re telling Zapier which piece of the submission goes in which column.
5. Add the second action. Choose your notification app, then the send-message action. Write the message and insert trigger fields where you want the submitted values to appear — so your alert says who submitted and what they asked, not just “new submission”.
6. Test and turn it on. Run the test. Check the row actually appeared in your sheet and the notification actually arrived. Then publish the Zap.
Once it’s live, submit one more real entry yourself and watch it flow through. Testing inside the editor and testing in production are different things, and the second one is what you’re trusting.
What Does It Cost to Run?
Two tasks per submission on this build, which puts it above the free plan at anything past 50 submissions a month. Zapier’s free tier is 100 tasks and — more restrictively — two-step Zaps only.
| Plan | Price | Tasks/month | Covers this Zap at |
|---|---|---|---|
| Free | $0 | 100 · two-step only | 50 submissions/mo |
| Professional | $19.99/mo annual · $29.99 monthly | 750 | 375 submissions/mo |
| Professional | $49/mo annual · $73.50 monthly | 2,000 | 1,000 submissions/mo |
| Team | from $69/mo annual | 2,000 · multi-user | 1,000 submissions/mo |
Note what the free plan’s two-step limit means in practice: trigger plus one action. The moment you add a notification alongside the spreadsheet row, you’ve outgrown it — regardless of volume. That step ceiling, not the task count, is what pushes most people onto a paid plan.
If that arithmetic bothers you, it’s worth knowing the alternatives meter differently. Make bills per module run at $9/month for 10,000, and n8n bills one execution per entire workflow regardless of step count. Full comparison in our automation tools guide and the Zapier pricing explainer.
What Should You Add Before Trusting It?
Two things, and neither is optional if this Zap does anything that matters. Both take under ten minutes.
An error notification. Zaps break — a connection expires, a field gets renamed, an app changes its API. Zapier can email you when a Zap errors; turn that on in the Zap’s settings. Without it, your automation stops and you find out when someone asks why nobody responded.
A filter, if any submissions should be ignored. Spam, test entries, internal submissions from your own domain. A filter as step two costs nothing and stops those runs before they consume a task.
| Addition | Time | Prevents |
|---|---|---|
| Error notification enabled | 2 min | Silent failure lasting weeks |
| Filter on spam or test entries | 5 min | Wasted tasks and noisy alerts |
| Descriptive Zap name | 30 sec | “Zap 4” meaning nothing in six months |
| A note on any non-obvious step | 1 min | Future you breaking it |
What Goes Wrong on a First Zap?
Four things, all recoverable, and all easier to fix if you know to look for them.
| Problem | Symptom | Fix |
|---|---|---|
| No test data available | Trigger test returns nothing | Submit a real entry, then retry the test |
| Fields mapped to wrong columns | Data in the sheet is scrambled | Re-check mapping against the test record |
| Zap runs but nothing appears | Task shows success, sheet is empty | Wrong worksheet selected — check the tab |
| Duplicate rows | Same submission twice | Usually two Zaps on the same trigger; check for an old draft |
Get comfortable with Zap History early. It’s the single most useful screen in the product and most people don’t find it until something has been broken for a fortnight.
What Should You Build Next?
Something that runs often and follows a fixed sequence. Frequency is what makes an automation worth its build time, and your first Zap taught you the model — the second one should be worth real money.
| Next build | Steps | Why it’s worth it |
|---|---|---|
| Lead capture into a CRM | 4–6 | Highest-payback automation for most businesses |
| Appointment reminder | 2–3 | Protects a whole booked slot per run |
| Invoice chase sequence | 3–4 | Directly attached to cashflow |
| Weekly report digest | 3–5 | Replaces a recurring manual chore |
Detailed walkthroughs: lead capture into your CRM, appointment booking and reminders, and invoicing with a chase sequence. To decide which is worth building first, run the ROI formula.
Frequently Asked Questions
How do I create my first Zap?
Pick a trigger app and event, connect the account, test the trigger with real data, add an action and map the fields, add a second action if needed, then test and publish. About twenty minutes for a two-action workflow.
Is Zapier free to use?
There’s a free tier of 100 tasks a month, limited to two-step Zaps. That step limit is the binding constraint for most people — trigger plus one action only, so adding a notification alongside a spreadsheet row already exceeds it.
What counts as a task in Zapier?
One action step. The trigger is free and filters are free, but every action, formatter and delay consumes a task each time the Zap runs. A three-action Zap running 200 times is 600 tasks.
Why isn’t my Zap triggering?
Usually no test data, an expired app connection, or a filter stopping the run. Check Zap History — it shows every run with its input and output, and it answers most troubleshooting questions in seconds.
How much does Zapier cost per month?
Free for 100 tasks and two-step Zaps. Professional starts at $19.99/month billed annually for 750 tasks, rising to $49/month annual for 2,000. Team starts at $69/month annual.
Should I use Zapier or something else?
Zapier is easiest to learn and has the widest app coverage. If your workflows are long, Make bills per module at $9/month and n8n bills one execution per whole workflow — both cheaper for step-heavy automations.
The Bottom Line
Building a Zap is easy and takes twenty minutes. The thing worth learning alongside it is the meter: every action step you add costs a task on every single run, so a workflow’s shape decides your bill more than your volume does.
Build this one, add the error notification, then watch Zap History for a week. Once you can read that screen and predict your task consumption, you understand Zapier better than most people who’ve used it for a year.
Then build something that runs often — lead capture is the standard next step, and it’s the one with the best payback.
Want one practical automation you can set up in 15 minutes, delivered every Tuesday? Join the free newsletter.
Sources
- Zapier — Pricing plans
- Make — Pricing plans
- n8n — Pricing plans
- SBE Council — 2026 Small Business Tech Use Survey
- U.S. Chamber of Commerce — AI Is Powering Small Business Growth in 2026
All sources retrieved 26 July 2026. Task-cost figures are worked arithmetic from Zapier’s documented billing unit. Interface wording changes — treat the step sequence as the shape, not as exact button labels.
