The connected account lost access
How you'll know: Zap history shows authentication errors, often after a password change or a person leaving.
Fix: Reconnect the app, ideally with a shared admin login rather than one employee's account.
A Zap is a trigger in one app (a form is submitted, an order comes in) followed by one or more actions in others (add a row, send an email, create a contact). You build it in Zapier's editor without code. This page walks through building one, how Zapier counts what you pay for, the mistakes that stop Zaps firing, and the few places where Zapier genuinely runs out.
Simple triggers work until the workflow outgrows them, then zaps fail quietly and nobody owns them.
Stuck on Zapier? Let's solve it →Trigger: the event that starts a Zap. "Instant" triggers fire when the app sends the event. Others are polling triggers, which check for new data on a schedule set by your plan, so expect a delay.
Action: something the Zap does in another app. Multi-step Zaps chain several actions.
Task: what Zapier bills you for. Each successful action counts as one task. Triggers don't count, and neither do Filter and Paths steps.
Zap history: the log of every run, with the data each step received and sent. It's the first place to look when something didn't happen.
Example: every new web form submission becomes a row in a Google Sheet and a message in Slack.
Name it after what it does, such as "Web form to sheet and Slack". You will have dozens of Zaps one day, and "Untitled Zap" tells you nothing.
Pick the form tool, choose "New Form Submission" or the nearest event, and connect your account.
Watch for: whether the event is marked Instant. If it isn't, new submissions arrive on a delay.
Zapier pulls a recent sample submission. Submit a fresh test entry with every field filled in first, so the sample shows every field you will want to map.
Add Google Sheets, "Create Spreadsheet Row", and map each column to a field from the trigger. Then add Slack, "Send Channel Message", and build the message from the same fields.
Watch for: typing a value into a field instead of mapping it. A typed value is sent the same way every time.
Each action's test sends real data, so point it at a test sheet or channel. When every step passes, publish the Zap and submit one more real entry to watch it run in Zap history.
Most Zaps should stay Zaps. These are the cases where Zapier genuinely stops.
If your Zap matches the left column, keep improving it. The right column is where n-frames comes in.
These cover most of the "my Zap isn't working" threads.
How you'll know: Zap history shows authentication errors, often after a password change or a person leaving.
Fix: Reconnect the app, ideally with a shared admin login rather than one employee's account.
How you'll know: A step errors with a required field missing, only for some runs.
Fix: Add a Filter step so the Zap skips runs missing that field, or set a default in the mapping. The Formatter can clean values before they're sent.
How you'll know: The row is created, but the date column is blank or the amount reads as text.
Fix: Add a Formatter step to convert the value into the shape the destination app expects.
How you'll know: No trigger to pick, but the app can send webhooks.
Fix: Use Webhooks by Zapier as the trigger and point the app's webhook at the URL it gives you.
How you'll know: Your plan ran out mid-month.
Fix: Put Filter steps early so runs that would be thrown away stop before any action counts, and check for a trigger firing on edits as well as new records.
A no-code automation platform. You choose a trigger in one app and actions in others, and Zapier runs the connection whenever the trigger happens, without you writing code.
Zapier trades depth for speed: a big app directory, a visual editor, and pricing by task. Custom automation is slower to start but can reach systems with no API, undo half-finished work when a step fails, and handle high volume at a fixed running cost. The workflow's complexity decides, not which sounds more serious.
It depends on where you work. Power Automate is built into Microsoft 365 and is often already licensed there. Zapier connects to a wider range of apps outside Microsoft. Make is the other common choice, with a visual canvas that suits branching scenarios.
For a Zap that fits the left column above, Zapier's editor and the walkthrough on this page are usually all you need. n-frames builds the automation for workflows that need a system Zapier can't reach, steps that must succeed or fail together, or volume that has outgrown task pricing, and keeps it running with logs and alerts.
It covers thousands of apps, and webhooks cover many more. It can't cover software with no API and no webhooks, like many internal tools and vendor portals. For those, the connection has to be built directly.
Its trigger is probably a polling trigger, which checks for new data on an interval set by your Zapier plan. Triggers labelled Instant fire as soon as the app sends the event.
An online retailer moving every order from the storefront to fulfillment to accounting.
Seven linked Zaps passed each order along, one handing off to the next.
When one failed quietly, nobody knew until a customer asked where their order was.
One custom service took over the whole chain, with logging, retries and an alert on failure.
Orders move through on their own, and a failed run now announces itself.