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
- Pick a business. New to Zapier? Start with the cleaning company: its three Zaps cover most of what Zapier does.
- Fill in its form, or pick a test event. Ready-made ones include “Gmail fails once” and “the number on file is a landline”.
- 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.
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.
Three Zaps, one way of working
Each Zap does one job. The line with the lightning bolt on each card is its trigger: the event in another app that starts it. Pick a card to open that Zap below.
- 01New quote requestJotform · New SubmissionForm sent → priced reply, lead logged, office told
- 02Job done to invoiceGoogle Sheets · New or Updated Spreadsheet RowJob marked Done → invoice sent, review asked two days later
- 03Visit reminderGoogle Calendar · Event StartDay before a visit → a reminder text to the client
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.Connection: Maple & Main (Marcus)
- Google SheetsOne spreadsheet, “Maple & Main Ops”, with the Leads, Jobs and Clients worksheets the office already used.Connection: office@mapleandmain.example
- GmailReplies to quote requests, review requests, and the fallback when a text cannot be sent.Connection: office@mapleandmain.example
- SlackPosts to #new-leads and #office, and messages Renee directly about recurring leads.Connection: Maple & Main workspace (Marcus)
- QuickBooks OnlineFinds or creates the customer, then creates and sends the invoice.Connection: Maple & Main books (Marcus, admin)
- Google CalendarThe “Crew schedule” calendar. An event one day away starts Zap 03.Connection: office@mapleandmain.example
- TwilioSends the day-before reminder texts from the office number.Connection: Office line, 614-555-0100
| Zap | Starts when | How fast |
|---|---|---|
| 01 · New quote request | Jotform · New Submission | Instant |
| 02 · Job done to invoice | Google Sheets · New or Updated Spreadsheet Row | Polling, every 2 min |
| 03 · Visit reminder | Google Calendar · Event Start | Polling, every 2 min |
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.
Sent
Thanks. Your price range is on its way to your inbox.
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.
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.
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.
- 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. Trigger · InstantJotform · New Submission
Runs the moment someone sends the “Get a quote” form on the website.
No taskSettings
- Form
- Get a quote
- 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.
No taskSettings
- Transform
- Capitalize
- Input
1. Full Name
- 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.
No taskSettings
- Transform
- Format Phone Number
- Input
1. Phone- To Format
- +15555551234 (E.164)
- Phone Number Country Code
- US
- 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.
No taskSettings
- 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
- 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.
1 taskSettings
- Spreadsheet
- Maple & Main Ops
- Worksheet
- Leads
- Name
2. Output1. Email- Phone
3. Output- ZIP
1. ZIP Code- Home size
1. Home Size- Service
1. Service- Quoted
4. Output
- 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 taskPath · In our areaZIP Code (Text) Is in 43201, 43202, 43212, 43214, 43221, 43085- 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.
1 taskSettings
- 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
- 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.
1 taskSettings
- 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”
- End of path
Path · Wants recurring serviceZIP Code (Text) Is in 43201, 43202, 43212, 43214, 43221, 43085 And Service (Text) Contains Recurring- 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.
1 taskSettings
- To Username
- Renee Alvarado
- Message Text
- Recurring lead:
2. Outputwants “1. Service”. Worth a call today:3. Output
- End of path
Fallback · Outside our areaRuns only when no other path does- 10. Gmail · Send EmailSay so, politely
People outside the service area get an honest answer in a minute, not silence.
1 taskSettings
- To
1. Email- From Name
- Maple & Main Cleaning
- Subject
- About your quote request
- Body
- Hi
2. Output… we do not clean in1. ZIP Codeyet…
- End of path
Running on your own form answers, at your local time. What the rest of the world does: (your choice under the form). Nothing is sent or stored.
- 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.
- Clean the data once, at the top. The three Formatter steps come straight after the trigger, and every later step maps their Output, never the raw form field. Formatter steps use no tasks, so tidying costs nothing.
- Prices in a lookup table, not in the email. The email maps one field, the lookup’s Output. When prices change, Marcus edits the table in one step. The Fallback Value means a new home-size option on the form cannot produce an email with a hole in it.
- Log before Paths. Nothing can follow a Paths step, so anything every lead needs happens first. The row is written before the split, which is why an outside-the-area lead is still counted.
- Paths are not if-else. Zapier runs every path whose rules are met. That is used on purpose here: an in-area lead who wants recurring service runs both the first and second path. The second path repeats the ZIP rule so it cannot fire for someone the crews cannot reach.
- A fallback, not a third set of rules. “Outside our area” is the fallback path: it runs only when no other path does. Writing it as “ZIP is not in the list” would work today and break the day a ZIP is added to one list and not the other.
- Slack goes after the email. Inside the first path the email is sent before the Slack post. If Slack fails, the customer has still been answered.
| App | Field | How it is used |
|---|---|---|
| Jotform | Full Name, Phone | Cleaned up by Formatter before any other step sees them. |
| Jotform | Home Size | The key for the price lookup table. |
| Jotform | ZIP Code | Decides which paths run. |
| Jotform | Service | Contains “Recurring” for the leads the owner wants to hear about. |
| Google Sheets | Leads worksheet | One row per request, with the price that was quoted. |
Marcus Bell owns this Zap and gets Zapier’s error emails. Autoreplay is on: a step that errors is tried again up to 5 times before anyone is emailed. Every run is kept in Zap history with what each step received and returned.
- A name typed in capitals reaches the email and the sheet as “Dana Whitfield”.
- Each home-size option on the form returns its own price range; an unknown one returns the fallback.
- An in-area, one-time lead runs the first path only.
- An in-area, recurring lead runs the first and second paths, in that order.
- A ZIP outside the list runs the fallback only, and the lead is still in the sheet.
- With the Slack channel archived, the customer email has already been sent and the run shows as Errored.
Zapier features in this build
Job done to invoice
The crew lead changes one cell to Done. The invoice goes out within minutes, and two days later a happy client is asked for a review.
The problem
Invoices were written on Fridays from a week of text messages, so a Monday job was billed five days later and paid later still. Review requests were sent in a rush whenever someone remembered, sometimes to a client who had phoned that morning to complain.
What I built
The crew lead sets the job’s Status to Done in the Jobs sheet. The Zap finds the client in QuickBooks, or adds them, creates the invoice from the row and emails it, then writes the invoice number back to the sheet. It waits two days, reads the row again, and asks for a review only if nobody has logged a complaint in the meantime.
Loading the editor, simulator and build notes…
Visit reminder
Every client hears from the office the day before their clean, by text if their number takes one and by email if it does not.
The problem
Two or three times a month a crew arrived to a locked door: the client had forgotten, or the dog was loose, or the alarm was set. Each one cost an hour of paid time. Reminder calls worked when they were made, and they were made when the office had a quiet afternoon.
What I built
The crew schedule already lives in a Google Calendar, with the client invited to each visit. One day before a visit starts, the Zap looks the client up in the Clients sheet, puts the start time in plain words and sends a text from the office number. If the number turns out to be a landline, the step’s error handler sends the reminder by email and tells the office, so no client is skipped.
Loading the editor, simulator and build notes…
Kettlebrook Solar
Kettlebrook sells and installs home solar in three states, with thirty people in sales. Leads from Facebook lead ads were downloaded as a spreadsheet twice a day and shared out by hand, so a homeowner who asked for an estimate at nine might hear back at four. Consultations booked in Calendly were retyped into HubSpot when someone had a minute, and managers learned what had been booked by asking around. Three Zaps now do the carrying: each lead reaches the right territory at once, each booking becomes a deal, and the day’s bookings arrive as one message.
- Zaps
- 3
- Steps
- 24
- Apps connected
- 5
- Test events
- 13
- Where
- Arizona, Nevada and New Mexico
The sample team
- Monica Reyes VP of sales
- Darius Cole Sales operations (owns the Zaps)
- Elena Park Territory lead, Arizona
- Tom Whitaker Territory lead, Nevada
- Sofia Marin Territory lead, New Mexico
How the Zapier account is set up
One Zapier account on the Team plan, so the Zaps, folders and app connections are shared and no Zap stops when one person leaves; polling triggers check every minute. HubSpot, Slack and Calendly are each connected once with a service login owned by sales operations.
Facebook Lead AdsHubSpotSlackCalendlyGmail
Kettlebrook Solar is a fictional business. The people, emails, phone numbers and HubSpot records are samples.
Three Zaps, one way of working
Each Zap does one job. The line with the lightning bolt on each card is its trigger: the event in another app that starts it. Pick a card to open that Zap below.
- 01Lead routingFacebook Lead Ads · New LeadAd lead → HubSpot contact with an owner, rep told at once
- 02Consult bookedCalendly · Invitee Created or RescheduledCalendly booking → HubSpot deal, team told, added to the day’s list
- 03Daily roundupSchedule by Zapier · Every DayWeekdays at 5:30 → the day’s bookings in one message
5 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.
- Facebook Lead AdsThe “Free solar estimate” lead form. Each new lead starts Zap 01.Connection: Kettlebrook Solar page (sales ops)
- HubSpotContacts and deals. The Zaps find or create both, set the owner and add notes.Connection: zapier@kettlebrook.example (service login)
- SlackDirect messages to territory leads, and posts to #consults, #sales-ops and #sales-floor.Connection: Kettlebrook workspace (sales ops bot)
- CalendlyHome solar consultations. A new or moved booking starts Zap 02.Connection: Kettlebrook team account (sales ops)
- GmailThe end-of-day roundup to the VP of sales.Connection: salesops@kettlebrook.example
| Zap | Starts when | How fast |
|---|---|---|
| 01 · Lead routing | Facebook Lead Ads · New Lead | Instant |
| 02 · Consult booked | Calendly · Invitee Created or Rescheduled | Instant |
| 03 · Daily roundup | Schedule by Zapier · Every Day | On a schedule |
Fill in the form yourself
This is the form the business’s customers use. Fill it in and press Submit. 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 · Lead routing takes on your answers and what each person would receive.
Loading the form…
How the form reaches Zapier, and the settings that matter.
How it is set up (4 notes for builders)
- A lead form, not a landing pageFacebook lead ads keep the form inside Facebook and prefill it from the person’s profile. Zapier’s New Lead trigger receives each submission as it happens.
- Custom questions arrive as named fields“Do you own your home?” and “Monthly electric bill” are custom questions on the form. Zapier shows each as its own field, mapped by name in the filter and the steps after it.
- Test with a real leadFacebook’s lead ads testing tool creates a real test lead for the form. The Zap was built against one of those, so every mapped field shows a value.
- One Zap for every adThe trigger watches the form, not an ad. New ads that reuse the form are routed with no change to the Zap, and the ad’s name is saved on the contact.
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 24 steps across its Zaps, triggers included. New to the words? Open the decoder.
Lead routing
A homeowner fills in the ad’s form, and within a minute they are in HubSpot with an owner who has been told to call.
The problem
Leads from Facebook lead ads were exported twice a day and divided by hand. Calling a lead within five minutes makes a conversation far more likely than calling within an hour, and the team’s typical first call came five hours later. Renters filled in the form too, and people who had asked before were handed to a new rep as if they were strangers.
What I built
The moment a lead comes in, the Zap drops anyone who does not own their home, tidies the phone number, and looks up which territory lead covers the state. It then finds the person in HubSpot by email or creates them with that owner. A new contact’s owner gets a direct message in Slack with everything needed to call. Someone who is already in HubSpot keeps their existing owner: the Zap adds a note to their record and tells sales operations.
Loading the editor, simulator and build notes…
Consult booked
When a homeowner books or moves a consultation, HubSpot has the deal with the right date before the rep has closed the tab.
The problem
Consultations were booked in Calendly and typed into HubSpot later, or not at all, so the pipeline report was always a few days behind what the calendar already knew. When someone moved their booking, the old date stayed in HubSpot. Managers found out what had been booked by asking in Slack.
What I built
Each new or moved booking of a solar consultation finds the homeowner in HubSpot, or adds them, then finds their consult deal or creates it, and sets the consult date either way. So a moved booking updates the deal it already has. The team sees one line in #consults, and the same line is added to a digest that the third Zap sends out at the end of the day.
Loading the editor, simulator and build notes…
Daily roundup
Managers get the day’s bookings in one post at the end of the day, and on a day with none they get nothing.
The problem
Managers wanted to know what had been booked each day without reading every line of a busy channel, and the VP of sales, who is rarely in Slack, wanted the same by email. A daily message that says “nothing today” teaches everyone to ignore the daily message.
What I built
Every weekday at 5:30 pm the Zap releases the “Consults today” digest that Zap 02 has been adding to. If the digest is empty, a filter ends the run there. Otherwise the list goes to #sales-floor and by email to the VP of sales, and the digest is cleared for tomorrow.
Loading the editor, simulator and build notes…
Fieldnote Workshops
Fieldnote runs 90-minute live workshops for nonprofit fundraisers, two or three a month, with 40 to 120 people in each. A seat is bought through a Stripe payment link. Until this year the founder registered each buyer in Zoom by hand from Stripe’s receipt emails, usually the same evening, so people who paid at the last minute sometimes had no link when the session began. After a workshop, the recording went out to everyone in one email that thanked the people who had missed it for coming. Three Zaps now cover the path from payment to follow-up.
- Zaps
- 3
- Steps
- 21
- Apps connected
- 6
- Test events
- 10
- Where
- Remote; attendees across the US and Canada
The sample team
- Nadia Farouk Founder and lead trainer
- Jules Bennett Operations (owns the Zaps)
- Ama Owusu Community and support
How the Zapier account is set up
One Zapier account on the Professional plan, which Paths and Looping need; polling triggers check every 2 minutes. The Zaps are numbered in the order an attendee meets them, and all six apps are connected by the operations lead with the company’s shared logins.
StripeZoomGoogle SheetsSlackMailchimpGmail
Fieldnote Workshops is a fictional business. The people, workshops, emails and links are samples.
Three Zaps, one way of working
Each Zap does one job. The line with the lightning bolt on each card is its trigger: the event in another app that starts it. Pick a card to open that Zap below.
6 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.
- StripeOne payment link per workshop. A completed checkout starts Zap 01.Connection: Fieldnote (live mode, restricted key)
- ZoomRegisters each buyer for their webinar; new registrants and finished recordings start Zaps 02 and 03.Connection: workshops@fieldnote.example (Webinars licence)
- Google SheetsThe Attendees worksheet: one row per paid seat, read back after the workshop.Connection: ops@fieldnote.example
- SlackA line in #registrations for each seat sold.Connection: Fieldnote workspace (ops)
- MailchimpAdds buyers who asked to hear about new dates, tagged with the workshop they bought.Connection: Fieldnote audience (ops)
- GmailThe day-before email and the follow-ups after each workshop.Connection: hello@fieldnote.example
| Zap | Starts when | How fast |
|---|---|---|
| 01 · Paid seat | Stripe · Checkout Session Completed | Instant |
| 02 · Day-before email | Zoom · New Webinar Registrant | Instant |
| 03 · After the workshop | Zoom · New Cloud Recording | Instant |
Fill in the form yourself
This is the form the business’s customers use. Fill it in and press Pay. 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 · Paid seat takes on your answers and what each person would receive.
Loading the form…
How the form reaches Zapier, and the settings that matter.
How it is set up (4 notes for builders)
- Stripe payment links, one per workshopNo checkout page was built. Each workshop is a product with a payment link, and each link carries a metadata field, Workshop, that Stripe copies onto the checkout session.
- The consent box is Stripe’s ownPayment links can show an optional promotions box. Its answer arrives on the checkout session as Consent › Promotions, which the Zap’s last filter reads.
- A restricted key for ZapierThe Stripe connection uses a restricted API key that can read checkout sessions and nothing else, so the Zapier account could never move money.
- Tested in Stripe’s test mode firstThe Zap was built and run end to end against a test-mode payment link and a practice Zoom webinar, then its connection was switched to live mode.
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 21 steps across its Zaps, triggers included. New to the words? Open the decoder.
Paid seat
Someone pays for a seat and has their own Zoom link before they have closed the receipt.
The problem
Buyers were registered in Zoom by hand, from Stripe’s receipt emails, when the founder had an evening free. People who paid on the day of a workshop sometimes had no link when it started. The attendee list lived in three places that never agreed, and everyone who bought a seat was added to the newsletter whether they had asked for it or not.
What I built
When a checkout completes and the payment has cleared, the Zap looks up which Zoom webinar belongs to that workshop and registers the buyer, so Zoom sends their personal join link at once. It adds a row to the Attendees sheet and a line in Slack. Last, a filter checks the box the buyer ticked at checkout: only those who asked to hear about new dates are added to Mailchimp, tagged with the workshop they bought.
Loading the editor, simulator and build notes…
Day-before email
Whenever someone registered, they get their join link and what to bring one day before the workshop starts.
The problem
The join link arrives when someone pays, which can be three weeks before the workshop. By the day itself it is buried, and the half hour before each session was spent answering “where is my link?” one email at a time.
What I built
Each new registrant starts a run that works out the moment one day before their workshop and then waits for it. When that moment comes, they get one short email with their own join link, the start time and what to have ready. Someone who registers on the day itself, after that moment has passed, gets the email straight away.
Loading the editor, simulator and build notes…
After the workshop
When the recording is ready, everyone on the roster gets one email, and it is the right one for whether they came.
The problem
After each workshop one email went to everybody: it thanked people who had not come for coming, and offered a certificate of attendance to people who had not attended. Splitting the list by hand meant exporting two reports and comparing them, so it was skipped.
What I built
When Zoom finishes processing the recording, the Zap fetches the roster for that workshop from the Attendees sheet and the list of people Zoom saw in the room. It then loops over the roster. For each person, Paths compares their email with the list from Zoom: those who came get the recording, their certificate and a feedback form; everyone else gets the recording and the next live dates.
Loading the editor, simulator and build notes…
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.
Clean the data once, at the top
Names in capitals and phone numbers in five formats are fixed by Formatter steps right after the trigger. Every later step uses the tidy version, so the CRM, the email and the Slack post all agree.
See Maple & Main Cleaning 01 · New quote request, Kettlebrook Solar 01 · Lead routing
Stop early, for free
A filter uses no task, and nothing after it runs. So the filter comes before anything is created: a renter, an unpaid checkout or a team meeting ends the run with nothing spent and nothing to clean up.
See Kettlebrook Solar 01 · Lead routing, Fieldnote Workshops 01 · Paid seat, Maple & Main Cleaning 03 · Visit reminder
Never the same record twice
Contacts, customers and deals are found before they are created, by email or by a name that can be searched. Someone who comes back is recognized, and a booking that is moved updates the deal it already has.
See Kettlebrook Solar 01 · Lead routing, Kettlebrook Solar 02 · Consult booked, Maple & Main Cleaning 02 · Job done to invoice
The important step first, the fragile one last
A step that fails stops the run but does not undo the steps before it. So the customer’s email, the invoice or the seat comes first, and the Slack post, the step most likely to break, comes last.
See Maple & Main Cleaning 01 · New quote request, Kettlebrook Solar 02 · Consult booked, Fieldnote Workshops 01 · Paid seat
Quiet when nothing is wrong
A run that stops at a filter or an empty search is recorded and emails nobody. The daily roundup is sent only on days with something in it. People trust a message more when it only arrives for a reason.
See Kettlebrook Solar 03 · Daily roundup, Maple & Main Cleaning 02 · Job done to invoice, Fieldnote Workshops 03 · After the workshop
A plan for each kind of failure
A brief outage is retried by Autoreplay and nobody hears about it. A failure that is a fact about the customer, like a landline that cannot take a text, has its own error handler. Anything else emails the Zap’s owner with a run they can replay.
See Maple & Main Cleaning 01 · New quote request, Maple & Main Cleaning 03 · Visit reminder, Kettlebrook Solar 01 · Lead routing
Rules in one place
Prices, territories and webinar IDs live in lookup tables, one row each, not spread across branches and email text. When a rule changes, one cell changes.
See Maple & Main Cleaning 01 · New quote request, Kettlebrook Solar 01 · Lead routing, Fieldnote Workshops 01 · Paid seat
The task count is part of the design
Every run on this page shows the tasks it used, counted the way Zapier bills them. A lookup table in place of two searches, or a filter moved up a step, is the difference between a plan that fits and one that runs out mid-month.
See Kettlebrook Solar 01 · Lead routing, Kettlebrook Solar 03 · Daily roundup, Fieldnote Workshops 03 · After the workshop
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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
From a brief to Zaps the team trusts
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.
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.
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.
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.
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.
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, notFormatter 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.