A Zap is Zapier’s term for one automated workflow: a trigger (something that happens in one app) connected to one or more actions (something that happens automatically in another app). This guide builds your first working Zap from account creation through testing and publishing — expect about 20-30 minutes for your first one, faster for each one after.
Prerequisites
- A free Zapier account (no credit card required)
- Accounts for the two apps you want to connect (e.g., a form tool and a spreadsheet)
- No coding knowledge needed
Step 1: Create an Account and Start a New Zap
From your Zapier dashboard, click “Create Zap.” You’ll land on a two-column canvas — a trigger on the left, and one or more actions on the right.
Step 2: Choose Your Trigger App
Search for and select the app that starts the automation — for example, “Google Forms” for a new form submission, or “Gmail” for a new email matching certain criteria. Connect your account when prompted and choose the specific trigger event (“New Response,” not just “Google Forms” generically).
Step 3: Add Your Action App
Search for and select the app that should do something automatically — for example, “Google Sheets” to add a new row. Connect your account and select the specific action (“Create Spreadsheet Row”).
Step 4: Map the Fields
This is the step beginners most often rush: map each field from your trigger (the form’s “Name” field, for example) to the correct field in your action (the spreadsheet’s “Name” column). Getting this wrong is the single most common reason a Zap runs successfully but produces garbled or missing data.
Step 5: Test the Zap
Use Zapier’s built-in test feature to run the Zap once with real (or sample) data before publishing. Confirm the result actually appears correctly in your action app — a successful test in Zapier’s interface doesn’t always mean the data landed exactly where you expected.
Step 6: Publish
Once your test succeeds, toggle the Zap on. It will now run automatically whenever the trigger event occurs, using one task from your monthly allowance each time it completes successfully.
Three Worked Examples
Example 1: Form Submission → CRM Task
Trigger: new response on a contact form. Action: create a task in your CRM with the submitter’s details pre-filled, so no lead sits unactioned in your inbox.
Example 2: Email Attachment → Cloud Storage
Trigger: new email matching a specific label or sender (e.g., signed contracts). Action: save the attachment automatically to a designated Google Drive or Dropbox folder, eliminating manual downloads.
Example 3: Calendar Booking → Notification
Trigger: new booking on a scheduling tool like Calendly. Action: send yourself a Slack or SMS notification with the client’s name and meeting time, so you never miss a new booking buried in email.
How to Estimate Your Monthly Task Usage
Count how many times each trigger event actually happens per month, then multiply by the number of action steps in that Zap. A form receiving 40 submissions/month feeding a 2-step Zap (create CRM task + send notification) uses 80 tasks that month, not 40 — a common miscalculation that leads to hitting Zapier’s free 100-task limit faster than expected.
Common Mistakes to Avoid
- Skipping the test step: a Zap that looks correctly configured can still map fields wrong until you actually verify the output.
- Underestimating task usage: multi-step Zaps consume one task per step per run, not one task total.
- Building overly broad triggers: a trigger that fires more often than intended burns through your task allowance on runs you didn’t actually need.
- Forgetting to turn the Zap on: a fully configured, tested Zap does nothing until you toggle it live.
Once you’re comfortable with the basics, our 15 workflow automation ideas guide has more recipes to build next, and if Zapier’s task-based pricing starts feeling limiting, our free Zapier alternatives roundup covers cheaper options.
FAQ
Is Zapier free?
Zapier’s free plan includes 100 tasks per month, but limits you to 2-step Zaps (one trigger, one action) and 5 total Zaps — enough for learning, but limited for real production workflows.
What counts as one task in Zapier?
One task is one successfully completed action step. A Zap with a trigger and two actions uses 2 tasks per successful run, not 1.
Can I test a Zap without using up a task?
Yes — Zapier’s built-in test feature during setup does not count against your monthly task allowance; only live, published runs do.
What happens if I go over my monthly task limit?
Zapier pauses your Zaps until the next billing cycle or until you upgrade to a higher tier — tasks don’t roll over, and existing automations simply stop running rather than incurring overage charges automatically.
Disclosure: AppGuideHQ may earn a commission if you sign up through some links on this page, at no extra cost to you. See our Terms of Use.