How to Build Your First Zapier Automation in 15 Minutes
Zapier is a no-code automation platform that connects about 8,000 apps through triggers and actions. A free account gives you 100 tasks a month and two-step Zaps, which is enough to confirm it works before you pay $29.99/month.
This guide builds one real automation from scratch: Gmail attachment to Google Drive folder plus a Slack ping. Fifteen minutes, no code. By the end you will also know why most first Zaps break in week two, because the failures are predictable.
What do you need before your first Zapier automation?
Three things: a Zapier account, at least two connected apps, and one boring repetitive task you already do by hand. Pick the boring task. People start with clever workflows and give up; the boring ones survive.
Zapier’s free tier caps you at 100 tasks per month and five single-step Zaps. A two-step Zap (one trigger, one action) counts as one Zap. A four-step Zap still counts as one Zap but burns two tasks per run.
Setup steps:
- Sign up at zapier.com with Google or email.
- Click Create then Zap in the top-left.
- Connect each app once under Apps. You authorise each one with OAuth, so no API keys to copy.
- Name the folder structure you will write into on the destination side. Zapier does not create folders for you unless the app supports a “Create Folder” action.
How to build a trigger in Zapier
Click the trigger block and choose Gmail → New Attachment. Zapier authenticates, then asks for a label filter. Type Invoices if you have one. Leave the search string empty unless you need it.
Now the important part: hit Test trigger. Zapier pulls your last few matching emails. If it says “We didn’t find any emails”, the label name is wrong or the account has no attachment in the last 30 days. Fix that here, not later. Almost every “my Zap doesn’t work” complaint is an empty test trigger that the user clicked past.
The trigger test also loads sample data — field names like Attachment: (Exists but not shown). That sample is what later steps reference, so don’t skip it.
How to add an action and map fields
Add an action block, choose Google Drive → Upload File. Zapier asks three things: destination folder, file, file name.
- Destination folder: pick by name from the dropdown. Shared Drives appear under a separate tab and behave differently — if your team uses one, connect it explicitly.
- File: in the field mapping panel, find the Gmail attachment field. It often shows as a generic “Attachment” with a note that binary files can’t be previewed. That’s normal.
- File name: use
{{Attachment Filename}}rather than retyping. If you hardcode a name, every upload overwrites the previous file, and you’ll spend an afternoon wondering where the invoices went.
Add a second action: Slack → Send Channel Message. Set the channel, then write something like New invoice received: {{Attachment Filename}}. Map the field from the previous step’s dropdown, not from the trigger, so you get the actual uploaded name.
How do you test a Zap before turning it on?
Use Test step on each block, then Publish. Zapier will run one real task with the sample data. That means a real file lands in Drive and a real Slack message fires. Delete the test file afterwards — most teams forget, and six months later the folder has 40 test-upload.pdf files.
Once published, the Zap runs on its own. You can watch runs under Zap History, which keeps 30 days of logs on paid plans and roughly one month on free — enough for debugging, not enough for an audit trail.
Why do Zaps break after a few weeks?
Three recurring causes, ranked by how often I see them:
| Symptom | Likely cause | Fix |
|---|---|---|
| Zap turned off by Zapier | Trigger app revoked the connection (password change, 2FA reset) | Reconnect the app under Apps |
| Error “not enough tasks” | Free plan hits the 100/month cap | Upgrade or add a filter to spend fewer tasks |
| Duplicate files uploaded | No dedupe filter | Add a Filter step on a unique field like message ID |
| Tasks run but data is empty | Field remapped to a stale step | Re-map in the action block, re-test |
Zapier does disable Zaps that fail repeatedly, and it emails you once. If you filter that mail into a folder, you find out when someone complains.
Is the free plan enough?
For a single personal automation, yes — 100 tasks covers most inbox-to-drive jobs. It stops being enough the moment you add a filter-heavy workflow, because filters don’t run for free: Zapier counts tasks at the action steps, and multi-step Zaps burn two or three per run. A 4-step Zap at 20 runs a day eats 2,400 tasks a month, which is well into the $73.50 Professional tier.
Anyone automating on behalf of a client, or running anything that touches billing, should look at Professional for the unlimited five-minute polling and path logic. Hobbyists should stay on free and pick one Zap.
What Zapier is not good at
It is not a scheduler for heavy batch jobs. Polling intervals start at 15 minutes on free and drop to 2 minutes on paid — if you need sub-minute reaction, you want webhooks and a real queue. It’s also a poor fit for transformations: string surgery, JSON reshaping, and conditional maths get ugly fast in Zapier’s field editor. People push it there anyway and end up with 12-step Zaps nobody will maintain.
If the logic needs more than six steps, the honest answer is a script.
Quick Summary
- A Zap has a trigger and at least one action; the free plan allows 100 tasks/month and five Zaps.
- Always run Test trigger before building actions; empty test data is the top cause of broken Zaps.
- Map file names from previous steps, never hardcode them, or uploads overwrite each other.
- Paid plans start at $29.99/month for 750 tasks; polling drops from 15 minutes to 2.
- Zapier is the right tool for two to four app handoffs, not for data wrangling.”}
