Zapier errors in one place.

What Zapier tells you on its own

When a Zap errors, Zapier emails your account: immediately, immediately then hourly, hourly only, or never.¹ Custom notification rules need the Professional plan or higher. So do error-handling paths and autoreplay; when an error handler runs, Zapier sends no error email.² If a Zap errors on 95% of its runs and ran more than 20 times in the past seven days, Zapier turns it off.³

What's missing: one place with every error from every Zap, grouped, with counts, and alerts in the channel your team already works in.

Setup: one Zap for all of them

Zapier has a trigger for errors, "New Zap Error" in the Zapier Manager app. It fires when a Zap you own hits an error.⁴ A single Zap forwards the errors of all your Zaps to Fehlo.

1. Create a project in Fehlo, pick "Zapier" as the platform and create the webhook URL. Treat it like a password.
2. Create a new Zap. Trigger: app "Zapier Manager", event "New Zap Error".
3. Action: app "Webhooks by Zapier", event "POST". URL: the webhook URL from Fehlo. Payload type: "JSON".
4. Map the fields. Under Data, add these fields and map each to the matching trigger field:

zap_title          Name of the Zap
zap_id             ID of the Zap
step_title         Name of the step that failed
error_message      Error message
task_history_link  Link to the run
zap_link           Link to the Zap

5. Test and publish. Test the step. A few seconds later the test error is in Fehlo, and the setup page notices by itself.

The webhook URL always answers 202, even when Fehlo drops a report, for example over the hourly limit. If it answered with an error, the forwarding Zap would fail, Zapier would report that as a new Zap error, and that would be forwarded again.

What Fehlo does with it

• one issue per Zap, step and kind of error; IDs, numbers and links in the message are ignored for grouping,
• counts, first and last seen, and whether a resolved issue comes back,
• links to the Zap and, when Zapier sends it, to the run,
• alerts by email, Microsoft Teams, Discord, Google Chat, ntfy, Zulip or webhook.

Worth knowing

• "New Zap Error" only covers Zaps you own. On Team and Enterprise accounts it goes to the person who created the failing Zap. It fires only after all autoreplay attempts are done, and only if your error emails aren't set to "Never".⁵
• According to Zapier the trigger gives no details about the specific task that errored.⁵ What ends up in the issue depends on the fields Zapier sends.
• Webhooks by Zapier is a premium app. Zapier staff in the community say it doesn't run on the free Zapier plan.⁶ Check this for your plan.
• Each forwarded error counts as one event against your Fehlo plan's quota. Fehlo accepts at most 300 errors per hour per webhook URL.

Make has an easier route without forwarding: Fehlo reads failed runs straight from the Make API. See Make scenario error monitoring.

Questions