Zapier tutorial

Zapier automation: build, test and trust your first multi-step Zap

Zapier automation connects the apps you already use so that an event in one, such as a new form entry, makes things happen in others without anyone copying data across. This tutorial builds one fictional workflow from trigger to tested, multi-step Zap with an AI step, and shows how to handle errors before they reach a customer.

Independent tutorial. Not affiliated with Zapier. Zapier official site

For you or your whole team

Start with a useful first step.

7-day free trial. No credit card needed.

You will continue on the Tosheo.ai app to create your account and review the trial terms.

What you will practise

Skills worth putting to work.

Trigger and action design

Choosing the event that starts a workflow and the smallest set of actions that finish it.

Field mapping

Passing real data between steps instead of typing values by hand.

Filters and paths

Stopping runs that do not qualify and routing the rest by clear rules.

Structured AI steps

Using output fields so AI results feed later steps reliably.

Safe testing and recovery

Testing with dummy data and using Zap history and replay to recover from errors.

Example task / fictional source material

Build the Mossgate enquiry Zap

Build the fictional Mossgate Gardens workflow in a Zapier account using a test form and a test spreadsheet. Run four dummy enquiries and submit a screenshot description of each run's outcome, your AI step prompt and output fields, and your filter rule.

Review criterion

Correct routing

Out-of-area, commercial and residential test enquiries each end up in the right place.

Review criterion

Structured AI output

The AI step returns named output fields that later steps map.

Review criterion

Safe testing

Only dummy data and test destinations were used.

Review criterion

Human approval

No customer-facing email is sent without an approval step.

Review criterion

Error plan

A fallback branch exists and the learner explains how they would find and replay a failed run.

Copy and adapt

Prompts to try

Replace the parts in square brackets with your own details, and check every output before you use it.

Extract enquiry fields

From the form submission below, extract: postcode area, project type (residential or commercial), budget range (as stated, or not stated) and a two-line summary of what the customer wants. Do not guess missing values. Submission: [mapped form fields]

Plan a Zap before building

I want to automate this process: [process description]. Propose a Zap as a numbered list: trigger, each action, any filter or path with its rule, where an AI step helps and where a person should approve. Flag any step that would send data outside the team.

Write test cases

For this Zap design, list five dummy test records that would check every filter, path and fallback. For each, state the expected outcome. Zap design: [design]

What is Zapier and what is a Zap?

Zapier is an automation platform that connects more than 9,000 apps, according to its own site. Its help centre defines a Zap as a workflow that connects your apps to automate repetitive tasks. Each Zap has a trigger, the event that starts it, and one or more actions, the steps it then performs.

Instead of typing values into each action, you map data from earlier steps, so every run uses the real details from that event. When you publish a Zap it switches on and handles new data created after it goes live, not records that already exist.

What workflow will we build?

The example is a fictional eight-person garden design studio, Mossgate Gardens. Enquiries arrive through a website form and sit in an inbox until someone has time. Some are outside the studio's service area, some are commercial jobs the founder wants to see personally and the rest are home gardens that the studio manager handles.

The Zap will: start when a form is submitted; use an AI step to extract the postcode area, project type and budget range and write a two-line summary; stop if the enquiry is outside the service area; route commercial enquiries to the founder and residential ones to the studio manager; and log every enquiry in a spreadsheet. Before any reply goes to a customer, a person approves it.

How do you build a multi-step Zap step by step?

You build a multi-step Zap by choosing a trigger, testing it to pull in a sample record, then adding actions one at a time and mapping fields from earlier steps. Build and test each step before adding the next, so you always know which step broke.

1. Trigger: new form submission

Choose your form app and the new-submission event, connect the account and test the trigger. Zapier loads sample records; pick a realistic one and continue with it.

2. AI by Zapier: extract and summarise

Add an action, search for AI by Zapier, and write the prompt, inserting the form fields with a forward slash. Add output fields such as postcode area, project type, budget range and summary, so later steps receive tidy fields rather than one block of text.

3. Filter: service area only

Add a Filter so the Zap continues only when the postcode area is on Mossgate's list. Zapier's help centre says a filter stops the Zap entirely for runs that do not match.

4. Paths: commercial or residential

Add Paths with one branch per project type. Zapier says paths route data to different actions based on conditions, and branches run one at a time, left to right.

5. Actions in each branch

Notify the right person with the summary, and add a row to the enquiries spreadsheet.

6. Human in the Loop before replying

Add a Request Approval step before an email reply is sent, so the studio manager can approve, edit or decline the draft.

How do AI steps work in Zapier?

An AI by Zapier step takes a prompt, mapped fields from earlier steps and optional output fields, and returns structured results that later steps can use. Zapier offers templates for summarise, write, classify and extract, and a Preview button so you can test the prompt and review the output before finishing.

Zapier's help page lists model tiers: Standard for high-volume simple tasks without tools, Advanced for stronger reasoning and tool use, and Premium, the default for new steps, for complex analysis. Higher tiers use more tasks per run, so pick the lowest tier that gets the extraction right. Zapier also notes that an AI by Zapier step does not learn from previous actions, so improve results by improving the prompt, not by hoping it adapts.

Keep AI steps on judgement-light jobs such as extracting and summarising. Write the rule for the Filter yourself rather than asking the AI to decide whether a postcode is in the area.

How do you test a Zap safely?

Test a Zap with dummy records and a test spreadsheet, because Zapier states that testing an action step performs the action for real and may change data in your apps. A test email goes to a real inbox; a test row lands in a real sheet.

Zapier requires you to test the trigger and every Filter and Paths step before publishing; other action tests can be skipped, but should not be on a first build. The Test run button in the editor runs every step at once with a chosen trigger record. For Mossgate, submit four fake enquiries: one outside the area, one commercial, one residential and one with a missing budget, and confirm each ends up where it should.

What happens when a Zap fails, and how do you handle errors?

When a step fails, the run shows an errored status in Zap history, where you can inspect what each step received and sent, fix the cause and replay the run. Zapier's help centre says autoreplay can automatically replay errored runs on paid plans, but it does not replay safely halted runs, and on the Free plan manual replay is available only for errored runs.

Design for failure from the start: give every branch a fallback path for unexpected values, use a clear naming scheme so you can find the Zap in history, and check history weekly for the first month. Zapier also notes that replaying a whole run counts successful steps towards task usage again, so replay only the failed step where you can.

How does Tosheo.ai teach Zapier automation?

Tosheo.ai teaches Zapier inside the AI automation course and in operations paths. Lessons start with mapping the process on paper, then build a fictional workflow like Mossgate's step by step, with the hands-on task marked against a rubric for trigger choice, filter logic, safe testing and where a person approves. Lessons take 10 to 15 minutes, and every plan starts with a 7-day free trial with no credit card needed.

Sources and scope

Zapier Help Center: create Zaps (triggers, actions, field mapping, publishing), checked 19 October 2026 ↗

Zapier Help Center: test your Zap steps, checked 19 October 2026 ↗

Zapier Help Center: filters and paths, task usage and limits, checked 19 October 2026 ↗

Zapier Help Center: create AI powered actions with AI by Zapier, checked 19 October 2026 ↗

Zapier Help Center: replay Zap runs and autoreplay, checked 19 October 2026 ↗

Zapier Help Center: Human in the Loop Request Approval, checked 19 October 2026 ↗

Zapier: how it works and number of connected apps, checked 19 October 2026 ↗

Before you decide

A few good questions.

What is a Zapier automation?

A Zapier automation, called a Zap, is a workflow that connects apps: a trigger event in one app starts one or more actions in others, using data mapped from earlier steps.

Do I need to code to use Zapier?

No. Zaps are built in a visual editor by choosing apps, events and fields. Clear logic matters more than code: knowing your trigger, your rules and where a person must check.

Does testing a Zap send real emails or create real records?

Yes. Zapier states that testing an action step performs the action for real. Use dummy records, a test spreadsheet and your own inbox until the Zap is ready.

What is the difference between a filter and paths in Zapier?

A filter stops a run that does not meet your conditions. Paths send each run down one of several branches based on rules, so you can handle different cases in one Zap.

Can Zapier pause for human approval?

Yes. Zapier's Human in the Loop app includes a Request Approval action that pauses a run until a reviewer approves, edits or declines. Zapier lists it as a premium app on paid plans.

Give your team a path, not another playlist.

Explore role-specific lessons, practical tasks and the manager view.

Start free trial7-day free trial · No credit card needed

Zapier automation: build, test and trust your first multi-step Zap

Start with a useful first step.

Skills worth putting to work.

Trigger and action design

Field mapping

Filters and paths

Structured AI steps

Safe testing and recovery

Build the Mossgate enquiry Zap

Correct routing

Structured AI output

Safe testing

Human approval

Error plan

Prompts to try

Extract enquiry fields

Plan a Zap before building

Write test cases

What is Zapier and what is a Zap?

What workflow will we build?

How do you build a multi-step Zap step by step?

1. Trigger: new form submission

2. AI by Zapier: extract and summarise

3. Filter: service area only

4. Paths: commercial or residential

5. Actions in each branch

6. Human in the Loop before replying

How do AI steps work in Zapier?

How do you test a Zap safely?

What happens when a Zap fails, and how do you handle errors?

How does Tosheo.ai teach Zapier automation?

Sources and scope

A few good questions.

Keep exploring.

AI automation course for repeated work

Zapier Agents: what they do and how to review them

Lesson: process maps with AI

Designing AI workflows for a small business

All AI tool tutorials

Give your team a path, not another playlist.