Loading tutorials…
Loading tutorials…
You signed up for Zapier and the dashboard is staring at you. This walks through one real, working Zap end-to-end — trigger app, action app, sample data, test, turn on — without the marketing fluff.
Who this is forOwners and operators who just opened Zapier and need their first Zap actually running today. If you have a clear "when X happens, do Y" already in your head, this gets you live in 30-45 minutes.
What you'll need
Step 1
Before opening Zapier, write the automation as a single sentence: "When [trigger event] happens in [App A], create/update [object] in [App B]."
The fastest way to build a broken Zap is to start clicking before you know what you want.
Open a notes file. Write: "When [a specific event] happens in [a specific app], I want [a specific outcome] in [a specific app]."
Example: "When a new row is added to the Leads Google Sheet, create a contact in HubSpot with the email, first name, and company columns mapped."
If the sentence has more than one verb or two apps, it is not one Zap — it is two or more. Pick the first one and ship it. You can chain later.
If you cannot write the sentence, you are not ready to build. Most automation debt starts here.
Step 2
Zapier → Zaps → + Create → choose "Zap." Skip AI Copilot for your first build — you want to learn the surface.
Log in at zapier.com. From the left nav, click "Zaps."
Click the orange "+ Create" button → choose "Zap" (not Tables, not Interfaces, not Canvas).
You'll see a two-step editor: a Trigger card and an Action card, with the AI Copilot panel on the right.
Ignore AI Copilot for this first build. It is excellent once you understand the editor, but it will hide the click-by-click logic you need to learn.
In the top-left, rename the Zap from "Untitled Zap" to something descriptive: "[Trigger app] → [Action app]: [outcome]." Future-you will thank present-you when you have 30 Zaps.
Step 3
Click the Trigger card → Choose app → Choose event → Connect account → Test trigger. Each sub-step has a known failure mode.
Click the Trigger card. In the right panel, search for your trigger app (e.g., "Google Sheets," "Typeform," "Shopify").
Choose the event. Read carefully — "New Spreadsheet Row" and "New or Updated Spreadsheet Row" sound similar but fire on completely different conditions.
Click "Connect" → authorize via OAuth. The pop-up must complete; if it closes mid-flow, the connection is half-saved and the Zap will fail silently later.
Select the specific resource (which spreadsheet, which form, which store). For Google Sheets, choose the sheet AND the worksheet (tab) — many DIYers miss the worksheet field.
Click "Test trigger." Zapier will pull the most recent matching record as sample data. If you see "We couldn't find any data" — add one real row/record to the source app, then retest.
Step 4
Click the Action card → Choose app → Choose event → Connect → Map fields from trigger output. Field mapping is the most common point of breakage.
Click the Action card. Search for the action app (e.g., "HubSpot," "Slack," "Airtable").
Choose the event. Be precise: "Create Contact" vs. "Update Contact" vs. "Find or Create Contact" all behave differently and one of them is usually what you actually want (Find or Create prevents duplicates).
Connect the account via OAuth.
Field mapping: every action field shows a dropdown. Click into it and pick the matching trigger field from the sample data. Type field names instead of relying on memory — the data picker is hierarchical and you will pick the wrong field.
For required fields with no perfect trigger mapping, you can type static text (e.g., a constant tag) or use the "Custom" tab to combine multiple fields.
Skip optional fields you do not need. Filling everything for completeness creates more breakage surface.
Step 5
Click "Test action." Zapier runs the action against the real production app with your sample data. Verify in the destination app before turning the Zap on.
Click "Test action." Zapier sends a real request to the destination app using the sample data.
Critically: this CREATES a real record in production. If you are mapping to "Send Slack Message," your team will see it. If you are mapping to "Create HubSpot Contact," a real contact gets written.
Open the destination app in another tab and verify the record looks correct. Field-by-field check the first few times.
If any field is wrong, click "Retest action" after fixing the mapping. Do not turn the Zap on until the test record is perfect.
Delete the test record from the destination app if it is junk. Otherwise it will hang around forever.
Step 6
Click "Publish." The Zap is now live and consumes Tasks. Watch Zap History for the first 24-48 hours to catch silent failures.
Click "Publish" in the top right. The Zap is now live — every matching trigger event consumes Tasks against your plan limit.
Generate a real trigger event (add a real row, submit a real form). Within 1-15 minutes, the Zap should fire.
Open Zapier → Zap History (or click the Zap → History tab). Verify the run shows "Success" with green status.
For the first 24-48 hours, check Zap History at least once. Default Zapier behavior: errors fire once, then halt the Zap silently unless you have notifications configured. You will not get an email.
In the Zap detail page → Settings → "Send email if Zap stops working." Turn this ON. Default is OFF for many plan tiers.
Common mistakes
Picking the wrong trigger event
What goes wrong: "New Spreadsheet Row" fires only on appended rows. If your team edits existing rows or pastes in batches, the Zap never fires and you blame Zapier. Hundreds of records silently skipped per month.
How to avoid: Read every available trigger event under the chosen app. "Updated Row," "New or Updated Row," and "New Row" all behave differently. Test each against your actual data-entry pattern.
OAuth connection half-saved
What goes wrong: The connection looks fine in the editor but every live run fails with a vague auth error. You lose 50-200 leads/mo while debugging the wrong layer.
How to avoid: When connecting, complete the OAuth pop-up fully — do not close it. If the Zap fails with "Authentication error," go to App Connections, delete the connection, and reconnect from scratch.
Field-mapping by clicking instead of reading
What goes wrong: You map "Email" but it pulls "Email (sample)" or some test field instead of the live one. Records write with empty or wrong data. Cleanup takes 2-4 hours at $50/hr in operator time.
How to avoid: Hover the field name in the data picker — the full path appears. Verify it matches the live trigger field, not a sample-only field. Run the test action and inspect the result in the destination app.
No error notifications turned on
What goes wrong: Zap halts after 1 error. You do not get told. By the time you notice (often 2-4 weeks later via a missing dashboard number), the gap is unrecoverable.
How to avoid: Zap → Settings → "Send email if Zap stops working" → ON. Better: pipe errors to a shared Slack channel so any teammate can catch a halt.
Letting Tasks scale without watching the bill
What goes wrong: Free tier is 100 Tasks/mo. Starter is 750/mo at $29. Pro is 2,000+. A single chatty Zap can blow through a tier overnight and the plan auto-upgrades the next billing cycle from $30 to $300/mo.
How to avoid: Monitor Zapier → Settings → Usage. Set a Task usage alert at 80% of your plan. Filter heavy Zaps with Filter by Zapier to skip runs that do not need to execute.
Not renaming the Zap
What goes wrong: After 10 Zaps, you have "Untitled Zap," "Untitled Zap (1)," "Untitled Zap (2)." Finding the right one to debug takes 10 minutes per incident.
How to avoid: Name every Zap as "[Trigger] → [Action]: [outcome]" before you publish. Use folders inside Zapier to group by business area.
Recap
Done — what's next
How to set up multi-step Zaps in Zapier
Read the next tutorial
Hand it off
One Zap is a tutorial. Twenty Zaps is a system. Most founders we talk to want their automations built once, monitored, and owned by someone who treats it as their job — not a 2am scramble when a Zap silently stops. An EverestX automation specialist runs $14-16/hr, typically $300-800/mo for ongoing maintenance across a 10-30 Zap stack.
See specialist rates
One Task = one successful action step. A single-step Zap that fires 100 times costs 100 Tasks. A 5-step Zap that fires 100 times costs 500 Tasks. Filter steps, Paths splits, and trigger pulls do not count — only successful action steps.
Not for your first one. Copilot is genuinely good at scaffolding Zaps from natural language, but it hides the field-mapping logic you need to learn. Build 2-3 Zaps manually first, then let Copilot accelerate the rest.
'New Row' fires only when an appended row is added below the existing range. 'New or Updated Row' fires on any edit to a tracked column. For form-style sheets where rows are appended, use 'New Row.' For status-tracking sheets where someone edits a cell, use 'New or Updated Row.'
Polling-based triggers (most apps) check every 1-15 minutes depending on your plan. Webhook-based triggers fire instantly. Free and Starter plans have 15-minute polling; Pro and above have 2-minute or instant for many apps.
Three common causes: (1) the test ran against stale sample data while live data has a different shape, (2) a required field in the action app is empty in live data but was filled in the sample, (3) OAuth scope changed and the connection silently lost permission. Re-test with the most recent live record.
Open Zapier → Zap History → filter by your Zap. You should see runs with timestamps that match real events. If History is empty for a Zap that should be firing, it has silently halted — usually an auth issue or a Task quota hit.
Zapier
One trigger, three or four actions. Easy to draw on a whiteboard, easy to break in production. This walks through chaining, naming, and the error scenarios that hit you on day 30, not day 1.
Zapier
One Zap. Five different outcomes depending on the trigger payload. This is where Filter by Zapier and Paths by Zapier earn their keep — and where most DIY setups stack conditions wrong and end up routing nothing.
Zapier
Your Zap was working last week. Today, Zap History shows red. This walks through the diagnostic flow specialists run — OAuth, payload shape, rate limits, schema drift — in the order that surfaces the issue fastest.
HubSpot Marketing Hub
Workflows are the engine under HubSpot's marketing automation. They are also where 80% of the silent breakage happens — wrong enrollment criteria, missing re-enrollment toggles, branch logic that loops. Here's how specialists build them so they hold up.
Klaviyo
Shopify and Klaviyo plug together in 10 minutes, but the integration that drives 30%+ email revenue takes 2-3 hours of structured setup. Historical sync, back-in-stock, and identified browsing are where most stores miss the money.