How to use Zapier

Zapier connects two apps so an event in one (a trigger) automatically causes something in the other (an action). You build that connection — a Zap — by picking the trigger app, picking the action app, mapping the fields between them, and turning it on.

Most people who get stuck in Zapier aren't stuck on the interface — they're stuck on the model. Once you can say your automation out loud as "when X happens in app A, do Y in app B", the screens make sense. This guide gets you from zero to a working Zap, then shows the failure modes that eat afternoons.

What people actually use Zapier for

Send new form submissions straight into a spreadsheet or CRM
Post a Slack message when a deal, order or ticket changes state
Copy new email attachments into cloud storage automatically
Add new customers to an email list without touching a CSV
Chain several apps together with filters so only the right records move

Zapier in five steps

1
Write the sentence before you touch the editor
"When a new row is added in Google Sheets, create a contact in HubSpot." The first half is your trigger, the second half is your action. If you can't write the sentence, the Zap will not work either.
2
Connect both apps first
Add both accounts under App Connections before building. Half of all "Zapier isn't working" moments are an expired or wrong-account connection, and it is far easier to spot that here than mid-build.
3
Build the trigger and pull real sample data
Choose the trigger event, then click Test trigger. Zapier pulls a real record so the field names you map next are the real ones. Never map fields against a made-up sample.
4
Add the action and map fields one by one
In the action step, click each field and insert the matching value from the trigger. Type static text where a value should always be the same. Test the action and check the destination app, not just the green tick.
5
Add a filter, then turn it on
Insert a Filter step so the Zap only continues when it should (status equals Paid, email is not blank). Publish, then watch Zap History for the first few real runs.

Stuck on your own screen?

Paste a screenshot of the exact Zapier screen you're on and Magic Assist AI tells you what to click next — no course, no 40-minute video.

Teach me Zapier

Common Zapier mistakes

Building on fake sample data

If you skip Test trigger, Zapier guesses the fields. The Zap tests fine and then drops real data into the wrong columns.

No filter, so everything fires

Without a Filter step every record triggers the action — including drafts, tests and duplicates. That's how people burn their task quota in a day.

Ignoring Zap History

Zapier keeps a run-by-run log with the exact error. People rebuild the whole Zap instead of reading the one red line that says which field was rejected.

Using polling triggers for urgent work

Many triggers check on a schedule rather than instantly. If timing matters, check whether the app offers an instant (webhook) trigger.

Zapier FAQ

What is a Zap in Zapier?

A Zap is one automated workflow: a single trigger plus one or more actions. It runs whenever the trigger event happens, as long as the Zap is turned on.

Why is my Zap not triggering?

The usual causes are a Zap left off, an app connection that has expired, a polling trigger that hasn't run yet, or a filter step that is blocking the record. Zap History shows which one it is.

Is Zapier hard to learn?

The concepts take about an hour. The difficulty is usually tool-specific — knowing which field in your CRM matches which field in your form — which is exactly the part Magic Assist AI walks you through on your own screen.

How many tasks does a Zap use?

Each successful action step counts as one task. A Zap with two actions that runs 100 times uses 200 tasks. Filters and triggers that stop the run do not count.

More guides

Or search any software and get a plan built on demand.