How to Build a Production Zapier Automation That Does Not Break

Most Zapier workflows break within 90 days of launch. They were never designed to fail. Here's how we build automations that survive contact with reality.

Rule 1: Always add a Filter step after the trigger

Triggers fire for events you don't care about. Adding a Filter (free, native) right after the trigger eliminates 60% of accidental runs and the support tickets that follow.

Rule 2: Use Paths instead of nested Filters

Paths (paid feature) let you handle multiple cases cleanly. Three nested Filters is a maintenance nightmare. One Paths step with three branches is debuggable.

Rule 3: Log every run to a Google Sheet

Add a final step writing every successful run to a Sheet — Zap name, trigger data, action result, timestamp. When something breaks 2 months later, you have a forensic trail.

Rule 4: Catch errors with Error Handler

The "Error Handler" path runs when any step fails. Use it to: 1. Post to Slack so you know immediately 2. Write the failure to a "failures" Sheet 3. Optionally retry the original action

Without an Error Handler, failures silently disappear and you find out from an angry customer.

Rule 5: Set up a Storage value as a heartbeat

Use the Storage app to write "last_run_at" on every successful execution. Then have a separate Zap that runs every hour, reads Storage, and alerts Slack if the timestamp is too old. Catches "Zap silently turned off" issues.

Rule 6: Don't trust webhook formats

When ingesting webhooks (Stripe, Shopify, etc.), always pipe through a Code step that normalizes the shape. APIs change. Code step gives you a single place to adapt.

Rule 7: Test with real production data, not Zapier's samples

Zapier's "Test Trigger" uses cached or fake data. Run a real test event through the live pipe before publishing. We've shipped Zaps that worked in test and crashed in prod because of a missing field in real data.

Bonus: a working template

Trigger → Filter → Code (normalize) → Paths → Action → Storage (heartbeat) → Sheet (log)

This 7-step pattern is what every gig we ship at Nexora uses.

Hire a Zapier expert →