Zapier · Zaps, filters, paths and loops

9 Zaps for three businesses. Run every one yourself.

Zapier connects the apps a business already uses. When something happens in one, such as a form being sent, a payment going through or a row changing in a spreadsheet, a Zap does the next steps in the others: add the contact, send the email, create the invoice, tell the team.

I built 9 Zaps for three made-up businesses: a home-cleaning company, a solar sales team and a company that runs paid workshops on Zoom. Each has a form you can fill in. Everything runs here in your browser, on test events or on your own answers. Need this for your business, or hiring for Zapier? Get in touch.

How to use this page

  1. Pick a business. New to Zapier? Start with the cleaning company: its three Zaps cover most of what Zapier does.
  2. Fill in its form, or pick a test event. Ready-made ones include “Gmail fails once” and “the number on file is a landline”.
  3. Press Run Zap. Watch every step run, with what it did in each app, every message it sent and how many tasks it used.

Short on time? Each Zap opens with The problem and What I built in plain words. The editor and the Build notes are the detail a Zapier builder would check. Words you may not know

Zaps you can run
9
Apps they connect
13
Test events to run them on
38
Steps and paths, each reached by a test
67/67

Are these real businesses?

No. Maple & Main Cleaning, Kettlebrook Solar and Fieldnote Workshops, and everyone who works there, are made up, so every Zap can be shown end to end with its messages and tried by anyone. The Zaps use Zapier’s real triggers, actions and built-in tools, under their real names, and follow its rules for filters, paths, loops, delays and tasks, checked against Zapier’s help center, so each one can be rebuilt step for step in a real account. Nothing on this page sends a message or keeps what you type.

Who built this

I’m Nick Soderstrom, a project and operations lead who builds automations. My client automation work so far has been in Zapier and GoHighLevel, including a 2025 Upwork contract for GoHighLevel, Zapier and Slack automations (see recent contracts). Those Zaps belong to the clients, so the ones here are samples I built to show how I design, test and hand off a Zap. This page and its simulator were built by directing AI, like the projects on my AI Projects page.

Zapier words in plain English (21)
Zapier
A service that connects the apps a business already uses, so that something happening in one starts work in the others. No code is needed.
Zap
One automation: a trigger, then the steps that follow it.
Trigger
What starts a Zap: an event in another app, such as a form being sent, a payment going through or a row changing. A trigger never uses a task.
Instant and polling triggers
With an instant trigger, the app tells Zapier the moment something happens. With a polling trigger, Zapier asks the app for anything new on a schedule: every 15 minutes on the Free plan, every 2 on Professional, every minute on Team and Enterprise.
Action
A step that does something in an app: add a row, send an email, create an invoice, update a deal.
Search
A step that looks something up in an app. If it finds nothing it can stop the run (the default), carry on anyway, or create the thing it was looking for, which Zapier calls “find or create”.
Mapped value
A value from an earlier step used in a later one. Zapier shows it as the step’s number and the field’s name, like “3. Output”. Shown here as a pill.
Task
What Zapier’s plans count. One task for each action or search that succeeds. Triggers, filters, paths, formatting, delays, loops and digests use none.
Filter
A step with rules. If they are not met, the run stops there on purpose and is recorded as Filtered.
Paths
A step that splits a Zap into branches, each with its own rules. Every path whose rules are met runs, one after the other, left to right. Nothing can come after a Paths step.
Fallback path
A path that runs only when no other path’s rules are met.
Formatter
Zapier’s tool for tidying data: capitalize a name, put a phone number in one format, reword a date, look a value up in a table.
Lookup table
A Formatter tool that swaps one value for another, such as a home size for a price or a state for a person, with a fallback for values it does not know.
Delay
A step that pauses the run for a set time (Delay For) or until a date (Delay Until), for up to 30 days. The run shows as Delayed until then.
Looping
A step that repeats every step after it once for each item in a list, up to 500 items. Each repeat is its own run in Zap history.
Digest
A tool that collects entries over time and hands them over as one block of text, for a daily or weekly summary.
Autoreplay
A setting that tries a failed step again, up to 5 times over about ten and a half hours, before anyone is emailed.
Error handler
Steps attached to one step that run only if that step fails, in place of the rest of the Zap. The run is recorded as Handled error.
Zap history
The list of every run, with its status: Successful, Filtered, Safely halted, Handled error or Errored, and others, such as Delayed, while a run is waiting.
Safely halted
A run that stopped on purpose, usually because a search found nothing. It is not an error and nobody is emailed.
Classic and Next Gen Zaps
These are Classic Zaps, built step by step in the Zap editor. In 2026 Zapier also began offering Next Gen Zaps, in early access, which can be built by describing a workflow to an AI tool.
Case study 1 · Home cleaning

Maple & Main Cleaning

Maple & Main cleans about 140 homes a month around Columbus with three crews. Quote requests used to sit in the website form’s inbox until someone had a quiet hour, invoices went out in a batch on Fridays, often a week after the job, and reminder calls happened when the office remembered. Nothing here needed new software. The form, the spreadsheet, QuickBooks, the calendar and Slack were already in place, so three Zaps now pass the work between them.

Zaps
3
Steps
27
Apps connected
7
Test events
15
Where
Columbus, Ohio

The sample team

  • Renee Alvarado Owner
  • Marcus Bell Office manager (owns the Zaps)
  • Tasha Greene Crew lead
  • Priya Nair Bookkeeper, two days a week

How the Zapier account is set up

One Zapier account on the Professional plan, which Paths needs; polling triggers check every 2 minutes. The Zaps sit in one folder, numbered in the order a customer meets them. Every app is connected once, by the office manager, so no Zap depends on a crew member’s login.

JotformGoogle SheetsGmailSlackQuickBooks OnlineGoogle CalendarTwilio

Maple & Main Cleaning is a fictional business. The people, addresses, emails and phone numbers are samples.

Connected apps

7 apps, each connected once

Zapier does not replace these apps. It signs in to each one, as the person named, and passes information between them. Each Zap’s trigger is listed with how fast it reacts.

  • JotformThe “Get a quote” form on the website. Each submission starts Zap 01.
  • Google SheetsOne spreadsheet, “Maple & Main Ops”, with the Leads, Jobs and Clients worksheets the office already used.
  • GmailReplies to quote requests, review requests, and the fallback when a text cannot be sent.
  • SlackPosts to #new-leads and #office, and messages Renee directly about recurring leads.
  • QuickBooks OnlineFinds or creates the customer, then creates and sends the invoice.
  • Google CalendarThe “Crew schedule” calendar. An event one day away starts Zap 03.
  • TwilioSends the day-before reminder texts from the office number.
What starts each Zap
ZapStarts whenHow fast
01 · New quote requestJotform · New SubmissionInstant
02 · Job done to invoiceGoogle Sheets · New or Updated Spreadsheet RowPolling, every 2 min
03 · Visit reminderGoogle Calendar · Event StartPolling, every 2 min
Live demo

Fill in the form yourself

This is the form the business’s customers use. Fill it in and press Get my quote. Use any name and a made-up email: nothing is sent or stored. Then press Watch the Zap run, which appears once you submit, to see every step Zap 01 · New quote request takes on your answers and what each person would receive.

Get a quote

Tell us about your home and we will email a price range within a minute. No obligation.

Required

How the form reaches Zapier, and the settings that matter.

How it is set up (4 notes for builders)
  • Jotform’s own Zapier connectionThe form is connected through Jotform’s New Submission trigger, which is instant: Jotform tells Zapier as each submission arrives. Nothing is embedded in the page.
  • Field names are the contractThe Zap maps fields by their label in Jotform. Renaming “ZIP Code” on the form breaks the mapping, so the form’s labels are listed in the handoff guide as things not to rename.
  • Validation belongs in the formZIP code is limited to five digits and Email must look like an email, both in Jotform. The person can fix a typo while they are still on the page; the Zap cannot ask them.
  • A test submission before turning it onThe trigger was tested with a real submission from the live form, not Jotform’s sample data, so every mapped field shows a real value while the steps are built.
The Zaps

Pick a Zap, pick a test event, press Run

Each tab below is one Zap. Read The problem and What I built for the short version. Then pick a test event and press Run Zap: the log lists every step in order, with the time it ran and what it did in each app, and the editor ticks off each step as it runs.

For Zapier builders: the simulator follows Zapier’s rules. A polling trigger starts the run at the next check, an instant one at once. A filter that does not pass ends the run as Filtered; a search that finds nothing ends it as Safely halted unless the step says otherwise. Paths runs every path whose rules are met, left to right, the fallback only when none is, and nothing follows it. Every step after a loop runs once per value, each iteration as its own run. Tasks are counted the way Zapier bills them: one per successful action or search, none for triggers, Filter, Paths, Formatter, Delay, Looping or Digest. This case has 27 steps across its Zaps, triggers included. New to the words? Open the decoder.

01 · Form → priced reply, logged, routed

New quote request

Every quote request gets a price range by email within a minute, lands in the Leads sheet, and reaches the right person on Slack.

The problem

Quote requests came in through the website form and waited in a shared inbox. On a busy day the first reply went out the next afternoon, by which time the person had usually booked someone else. Names arrived in all capitals, phone numbers in five formats, and about one request in six was from a ZIP code the crews do not cover.

What I built

When the form is sent, the Zap tidies the name and phone number, looks up the usual price for that home size, and adds the lead to the Leads sheet. Then Paths decides what happens: inside the service area, the person gets the price range and a link to book a walkthrough, and the office sees the lead in Slack. If they also want recurring service, the owner gets a direct message. Outside the area, the person gets a polite no.

Maple & Main /01 · New quote requestOn
Trigger
Instant
Autoreplay
On
Owner
Marcus Bell

The Zap as it reads in Zapier’s editor. Each step gets a green tick when the run reaches it; paths that did not run fade. Open a step for its settings. The numbered pills are values mapped from an earlier step.

  1. 1. Trigger · InstantJotform · New Submission

    Runs the moment someone sends the “Get a quote” form on the website.

    Settings
    Form
    Get a quote
    No task
  2. 2. Formatter by Zapier · TextTidy the name

    People type their name in capitals, in lower case, or with stray spaces. Every later step uses this version.

    Settings
    Transform
    Capitalize
    Input
    1. Full Name
    No task
  3. 3. Formatter by Zapier · NumbersPut the phone number in one format

    Whatever was typed becomes +16145550142, the format Twilio and click-to-call links need. A number that is not a real phone number comes out empty.

    Settings
    Transform
    Format Phone Number
    Input
    1. Phone
    To Format
    +15555551234 (E.164)
    Phone Number Country Code
    US
    No task
  4. 4. Formatter by Zapier · UtilitiesLook up the usual price

    The price list lives in this one step. A home size that is not in the table gets the fallback, so the email never shows a blank.

    Settings
    Transform
    Lookup Table
    Input
    1. Home Size
    Lookup Table
    Studio or 1 bedroom → $110 to $140 · 2 bedrooms → $140 to $180 · 3 bedrooms → $180 to $230 · 4 or more bedrooms → $230 to $300
    Fallback Value
    confirmed after a walkthrough
    No task
  5. 5. Google Sheets · Create Spreadsheet RowAdd the lead to the sheet

    Every request is logged before anything is sent, inside the area or not, so the count of leads is always right.

    Settings
    Spreadsheet
    Maple & Main Ops
    Worksheet
    Leads
    Name
    2. Output
    Email
    1. Email
    Phone
    3. Output
    ZIP
    1. ZIP Code
    Home size
    1. Home Size
    Service
    1. Service
    Quoted
    4. Output
    1 task
  6. 6. Paths by Zapier3 paths

    Every path whose rules are met runs, left to right; the fallback runs when none is. Nothing comes after a Paths step.

    No task
    Path · In our areaZIP Code (Text) Is in 43201, 43202, 43212, 43214, 43221, 43085
    1. 7. Gmail · Send EmailSend the price range

      A plain reply from the office address with the usual price for that home size and a link to book a walkthrough.

      Settings
      To
      1. Email
      From Name
      Maple & Main Cleaning
      Subject
      Your Maple & Main quote
      Body
      Hi 2. Output… Service: 1. Service · Home size: 1. Home Size · Usual price per visit: 4. Output
      1 task
    2. 8. Slack · Send Channel MessageTell the office

      Posts the lead to #new-leads with the cleaned-up name and phone number, so whoever is free can follow up.

      Settings
      Channel
      #new-leads
      Message Text
      New quote request: 2. Output · 1. ZIP Code · 1. Home Size · 1. Service
      Send as a bot?
      Yes, named “Leads”
      1 task
    3. End of path
    Path · Wants recurring serviceZIP Code (Text) Is in 43201, 43202, 43212, 43214, 43221, 43085 And Service (Text) Contains Recurring
    1. 9. Slack · Send Direct MessageFlag recurring leads to Renee

      A recurring client is worth far more than a one-time clean, so the owner hears about these directly and calls the same day.

      Settings
      To Username
      Renee Alvarado
      Message Text
      Recurring lead: 2. Output wants “1. Service”. Worth a call today: 3. Output
      1 task
    2. End of path
    Fallback · Outside our areaRuns only when no other path does
    1. 10. Gmail · Send EmailSay so, politely

      People outside the service area get an honest answer in a minute, not silence.

      Settings
      To
      1. Email
      From Name
      Maple & Main Cleaning
      Subject
      About your quote request
      Body
      Hi 2. Output… we do not clean in 1. ZIP Code yet…
      1 task
    2. End of path
Pick a test event
Tue Mar 3, 9:41:00 AMNot started
  1. Pick a test event above, then press Run Zap. Each line is one step, with the time it ran and whether it used a task; open In your apps to see what it created or changed. Emails, Slack messages and texts are shown as they would arrive.

Build notes

The detail a Zapier builder would check before trusting this Zap. Start with What if… for the unusual cases in plain words. Words you may not know

  • The same person sends the form twiceThey get two replies and two rows. That is acceptable for a quote form, and the Leads sheet has a filter view that shows repeated emails. A Zap that searched the sheet first would cost a task on every lead to save a rare duplicate.
  • A phone number that is not a phone numberFormat Phone Number returns nothing for “call me”, so the Slack post says there is no usable number and the office replies by email.
  • A ZIP code typed with a space or +4The form field is limited to five digits with a validation rule in Jotform, so “43214-1234” cannot be sent. The rule belongs in the form, where the person can fix it.
  • Gmail or Slack is down for a minuteAutoreplay tries the failed step again, first after five minutes. The run waits as Scheduled and no error email goes out unless every try fails.
  • A new service is added to the formNothing breaks: the service name is passed through as text. Only a new home-size option needs a line in the lookup table, and until then the fallback covers it.

Zapier features in this build

  • Instant trigger
  • Formatter: Capitalize
  • Formatter: Format Phone Number
  • Formatter: Lookup Table
  • Paths with custom rules
  • Fallback path
  • More than one path per run
  • Autoreplay
  • Google Sheets
  • Gmail
  • Slack
Reliability

Built so the team can forget about it

A Zap that works in a demo is easy. One a business can rely on has to cope with messy form answers, people who come back, apps that are down for a minute and channels that get renamed. These habits are in every case study. In plain words: nothing is created twice, the customer is looked after first, failures have a plan, and nobody is told unless they need to act.

Troubleshooting

What I check first when I inherit a Zapier account

Most fragile Zapier accounts fail in the same few ways. This is the order I look in, and what I do about each.

  1. Zaps nobody ownsBuilt by someone who has left, running on their personal logins. I list every Zap with its owner, last run and error rate, and move the app connections to shared service logins.
  2. Errors nobody readsError emails going to an old inbox while a Zap fails for weeks. I point notifications at a named person and turn on Autoreplay where trying again can help.
  3. A Zap that triggers itselfA Zap that edits the very row or record its trigger watches, running in circles and using up tasks. I add a filter that only the first run can pass, or change the trigger column.
  4. Paths used as if-elseTwo paths whose rules overlap, so some runs take both and customers get two emails. I make the rules exclusive, or turn the catch-all into a fallback path.
  5. Searches that stop the runA search that finds nothing halts by default, taking the steps after it down too. Where those steps should run anyway, I set the search to continue or to create what it was looking for.
  6. Tasks spent on nothingFilters placed after paid steps, and searches doing a job a free lookup table could do. I reorder the steps so the free ones come first.
  7. Raw form data everywhereWhatever was typed into a form is mapped straight into the CRM. I add Formatter steps at the top and map their output everywhere below.
  8. Delays on Zaps that get switched offA run waiting in a delay only continues if the Zap is on when its time comes. I mark every Zap with a delay as one to edit as a draft, never to turn off.
How I work

From a brief to Zaps the team trusts

  1. Scope

    What should happen, when, and who needs to hear about it. Which app is the home of each fact. Written down before a Zap is opened.

  2. Map the path

    The trigger, each step, and every place a run could stop. I count the tasks per run and per month before building, so the plan is chosen on purpose.

  3. Build on real test data

    A real form submission, a real test payment, a real calendar event. Every mapped field shows a real value while the steps are built.

  4. Break it on purpose

    A renter, a landline, an archived channel, a payment that has not cleared: each test event on this page is one I would run before switching a Zap on.

  5. Switch on and hand off

    Zaps turned on one at a time, error emails pointed at the owner. Then a short recorded walkthrough and a one-page guide: what each Zap does, which names never to change, what to do when an error email arrives.

  6. Watch it

    Zap history checked daily in the first week, then weekly: errors, runs stuck in Delayed, and tasks used against the plan.

Naming, so the next person can find things

Zaps
01 · New quote request: numbered in the order a customer meets them, named for what they do
Folders
Sales / Leads: one per team or stage, shared, so nothing lives in a personal folder
Steps
Tidy the name, not Formatter 2: Zap history lists steps by name, so each one says what it does
Connections
HubSpot · service login: named for whose login they use, never one person’s own

Hiring for Zapier, or need it built?

I build, fix and document Zaps: the triggers and steps, the error handling around them, the task budget, and the handoff so a team can run them. If you’re hiring for an operations or automation role or need this for your business, I’d like to hear about it.