Zapier Tutorial: Build Your First Zap Step by Step

Zapier is a no-code automation tool that connects your apps so routine work runs on its own. You build a “Zap”: a trigger (the event that starts it) followed by one or more actions (what Zapier does next). In this Zapier tutorial you will build a first Zap in six steps: pick a trigger, connect your account, test the trigger, set up the action, test it, and publish. Then you will add a filter, try an AI step, and learn how tasks affect your cost.

This guide is for beginners who have never automated anything. You do not need to code. Every product detail below was checked on Zapier’s own pages on 13 October 2026, and plans change, so confirm anything you plan to pay for.

Related reading: Zapier course, Zapier alternatives, and Zapier vs Power Automate. Key terms used in this guide: prompt injection and AI agent.

What Zapier is and how a Zap works

Zapier describes a Zap with one simple command: “When this happens, do that.” In its get started guide, every Zap has a trigger and one or more actions, and a published Zap runs its actions each time the trigger event occurs. The Zapier app directory lists integrations with more than 9,000 apps, so there is a good chance your email, calendar, spreadsheet and form tools are already there.

Three terms will come up again and again:

• Trigger: the event in one app that starts the Zap, such as a new form entry or a new email.
• Action: the step Zapier performs in another app, such as adding a spreadsheet row.
• Task: one successful action. Zapier’s plans are measured in tasks, so this word matters for cost.

A good mental model: Zapier is a patient assistant who watches one inbox and copies the right details into the right place, the same way, every time.

Before you start: plans, pricing and test data

Zapier’s guide to what counts as a task (updated 16 June 2026) lists these starting points:

• Free: $0, 100 tasks per month.
• Professional: from $19.99 per month billed annually, 750 tasks per month.
• Team: from $69 per month billed annually, 2,000 tasks per month.

Zapier’s pricing guide adds that Professional unlocks multi-step workflows, premium apps, and built-in tools such as Filters, Paths and Formatter, and that paid plans start with a 14-day free trial. In practice, a Free plan Zap is one trigger plus one action. The paid figures above are billed annually; monthly billing costs more, so check zapier.com/pricing before you upgrade, because prices and task tiers can change.

Next, prepare your test data. Zapier’s guide suggests using made-up names, such as superheroes or fictional characters, so you never confuse a test with a real entry. That tip matters more than it sounds, because tests send real data to real apps.

Hypothetical example used in this tutorial: Maria runs a small home bakery. Orders arrive through a web form, and she copies each one into a spreadsheet by hand. Her first Zap will do that copying for her.

Creating your first Zap, step by step

Before you open the editor, answer four planning questions from the Zapier get started guide: Which apps? What event starts the Zap? What should the Zap do? Which pieces of information should move? For Maria: a form app and a spreadsheet; a new form entry; add a row; name, email, order and pickup date.

Create the spreadsheet first and name every column. Then submit one test order with fictional details. Now build:

1. Pick the trigger app and event. In the Zap editor, search for your form app and choose the trigger event, such as a new form entry. If you start from a Zap template, this part is filled in for you.
2. Connect your account. Sign in to the app when asked and choose which account the Zap should use. More on permissions in the security section below.
3. Test the trigger. Click Test trigger. Zapier looks for an existing entry and pulls it in as a sample. According to Zapier, this test only reads data; it does not change anything in your form app. Pick the record and continue.
4. Set up the action and map fields. Choose your spreadsheet app and an event like “create row.” Your column names appear as fields. Click into each one, type a forward slash (/), and pick the matching piece of trigger data. You can also type fixed text, for example “Website form” in a Source column.
5. Test the action. Click Test step. This one is real: Zapier actually performs the action, so a new row appears in your sheet. Open the sheet and check every column. Delete the test row afterward if you like.
6. Publish. When the result looks right, click Publish. From then on, each new order fills a row without you.

Do not skip the tests. The get started guide warns that a test email is actually sent, which is why your test data should use your own address.

Add logic with filters and paths

Once the basic Zap works, logic steps make it smarter. A filter lets the Zap continue only when data meets a condition. A path splits the Zap into branches, so different data gets different actions. Both are listed under Professional features in Zapier’s pricing guide, so you need a paid plan or the trial.

Back to Maria. She adds a second action that emails her a notice, but only for orders larger than a set amount. A filter placed before that email step checks the order total. Small orders still go into the sheet; large ones also trigger the email.

With paths, she could go further: Path A for wedding cakes (create a calendar hold and send a note), Path B for everything else (add to the sheet only). Zapier’s own paths walkthrough shows the same idea for routing leads, and it adds a fallback path that runs when data matches no other branch, such as a typo or an empty field.

A useful rule: if you catch yourself building two nearly identical Zaps, one path-based Zap is usually easier to maintain.

Add an AI step: a worked example

AI by Zapier lets you put an AI action inside a normal Zap. Zapier’s AI by Zapier guide (updated 22 July 2026) says it is available on Pro plans and higher, and that you can pick a model tier: standard steps cost one task, advanced steps three, and premium steps five.

Here is how Maria might use it. Customers often type long notes in the “special requests” box. She wants a short, tidy summary in her sheet.

1. Keep the form trigger you already tested.
2. Add an action step and choose AI by Zapier from the built-in tools.
3. Write a prompt such as: “Summarize this cake request in one sentence: flavor, size and decoration.” Type a forward slash to insert only the special requests field.
4. Define output fields (for example, Summary and Size) so later steps can map them.
5. Test the step, read the result, and adjust the prompt.
6. Map the outputs into two new sheet columns, test again, then publish.

Two habits keep AI steps reliable. First, send the AI only the field it needs, not the whole form. Second, check which model tier is selected before you publish, because a higher tier multiplies task use on every run. For a one-line summary, a standard model is usually enough.

AI output can be wrong. Treat it as a draft. Do not let AI extract allergy or dietary details; Maria reads every original note herself.

How tasks are counted, with simple math

Zapier’s task guide explains what uses your allowance. Triggers do not count. Filters and Paths do not count. Steps that error or halt do not count. Each successful action in another app counts as one task, and AI by Zapier steps use a multiplier: 1x for standard, 3x for advanced and 5x for premium.

Here is a worked example for Maria’s bakery, assuming 120 orders a month (a hypothetical number):

The first Zap already goes past the Free plan’s 100 tasks. The filter row shows why logic steps are cheap: the filter itself is free, and the email only costs a task when it runs. The last two rows show how the AI model tier can double a monthly bill without any change in order volume.

What happens if you run over? The same guide says paid plans include pay-per-task billing at a higher per-task rate, capped at three times your plan’s task limit. After that cap, Zaps pause until the next cycle. Check your usage page during the first month of any new Zap.

Common mistakes and troubleshooting your Zaps

Most beginner problems fall into a few patterns. Here they are, with fixes:

• Testing with real customer data. Fix: use fictional entries and your own email address.
• No sample data for the trigger. Fix: submit one test entry before clicking Test trigger.
• Blank fields in the result. Fix: check that each field is mapped to trigger data, not left empty.
• An expired app connection. Zapier’s troubleshooting guide notes that connections can expire. Reconnect the account in the Zap editor.
• Burning tasks on a busy trigger. Fix: add a filter early so unwanted runs stop before any paid action.

When a live Zap fails, start with Zap history. The same guide explains that Zap history records every run, shows which step failed, and lets you replay a run once the cause is fixed. It also points to Zapier’s status page for outages. Read the error message closely: it usually names the field or permission that caused the failure.

Security: connected accounts and data you send to AI steps

Every Zap acts on your behalf in other apps, so treat setup as you would giving a helper a set of keys.

Connected accounts. The get started guide notes that Zapier asks each app for a general set of permissions, and only takes the actions your Zaps are set up to do. Follow the least privilege idea anyway:

• Connect the account with the smallest access that still does the job. A shared bakery inbox is safer than your personal email.
• If an add-on or integration asks to read all your Google Drive files or all of Gmail and you only need one folder or label, look for a narrower option or skip it.
• Remove Zaps and connections you no longer use.

Data you send to AI steps. Zapier’s security and compliance page states that it does not train on the data that runs through your workflows, on any plan, and that it encrypts data in transit and at rest. AI steps send the mapped fields to an outside model provider. Even so, a careful rule is simple: never send passwords, card numbers, ID numbers, health records or children’s data through an AI step. Map only the fields the prompt needs.

Prompt injection and approvals. If an AI step reads text written by strangers, such as incoming emails or form notes, that text can contain instructions meant to steer the AI. Keep a human approval before anything is sent, deleted, paid or published. The AI by Zapier guide mentions an AI Guardrails step that can detect personal data and prompt injection attempts, which is worth adding when AI reads outside content.

Decision framework: which Zap to build first

Not every chore is worth automating. Score each idea with these questions:

1. How often does it happen? Daily or weekly beats once a quarter.
2. Is it the same every time? Copying and sorting are great fits. Judgment calls are not.
3. What breaks if it goes wrong? A wrong spreadsheet row is easy to fix. A wrong email to a customer is not.
4. How many tasks will it use? Multiply runs per month by actions per run, and add AI multipliers.
5. Does it touch sensitive data? If yes, redesign it or keep it manual.

Good first Zaps: form entries to a spreadsheet, new calendar events to a to-do list, or saving email attachments to a folder. Wait on Zaps that send messages to customers or delete records until you are comfortable reading Zap history.

Next step

Build Maria’s Zap with your own form and sheet, test it with fictional data, and publish it. After one week, check Zap history and your task usage, then add one filter or one AI step. Small, tested changes teach you more than a big automation built in one go.

If you want structured practice with AI tools before you add AI steps to real workflows, Explore Coursiv AI lessons: guided, bite-sized lessons you can take at your own pace.

Related guides: n8n vs Zapier and how to automate boring tasks with AI.

FAQ