Questions › Guides

Zapier: send webhook alerts that get retried

Short answer: Use a Webhooks by Zapier POST or Custom Request action and put your HoldAlarms webhook URL in URL. HoldAlarms answers Zapier as soon as the alert is queued, then delivers it to your endpoint and retries if it fails (Zapier: send webhooks in Zaps).

Why alerts get lost

  1. Your endpoint is down or restarting. Zapier gets an error and the step fails; your endpoint never gets that alert.
  2. Slow replies. Zapier waits on your endpoint, and a timeout fails the step.
  3. Nobody notices. A failed step shows in Zapier's history, but often no one looks until something is missing.

Set it up with HoldAlarms

  1. Start a trial and copy the webhook URL from your dashboard. It looks like https://api.holdalarms.com/hook/<your token>.
  2. Add your own endpoint as a destination in HoldAlarms.
  3. In the Zap editor, add a Webhooks by Zapier action, choose POST, set Payload Type to JSON and paste the URL into URL.
  4. Send one test and check Recent alerts on your dashboard.

Full reference: Docs: Zapier, Make, n8n and Grafana.

What HoldAlarms does

We answer Zapier with HTTP 200 once the alert is queued, then deliver it to your endpoint in the background. Your endpoint gets 10 seconds per attempt. If it fails, we retry up to 5 times, 2 to 60 seconds apart (permanent errors such as 401 or 403 aren't retried). Retries finish within about 3 minutes, or up to about 6 if your server asks for longer waits with Retry-After. After that the alert is parked in a dead-letter queue and you get an email.

Two honest limits: we add a hop, so HoldAlarms doesn't cut latency; and a delivered alert means your endpoint accepted it, not that your app finished processing it. Starter is €19/mo and Ops €49/mo.

Questions

Which Zapier plans have Webhooks by Zapier?

Zapier's help page lists Webhooks by Zapier actions for its Team and Enterprise plans. Check your plan in Zapier.

Should I use POST or Custom Request?

POST builds the body from the Data fields for you. Custom Request sends the body exactly as you type it, which suits nested JSON or plain text. Both work with HoldAlarms.

Does Zapier send form fields or JSON?

Whatever you pick as Payload Type. HoldAlarms forwards JSON, form fields and XML unchanged, with the same content type.

Can I use PUT instead of POST?

No. HoldAlarms accepts POST only on the webhook URL.

Are my custom headers passed on?

No. Custom headers you add are not forwarded to your destinations. Put anything your endpoint needs into the body.

Does HoldAlarms reduce latency?

No. HoldAlarms adds a hop, so each alert reaches your endpoint slightly later than it would directly. What it gives you is an answer to Zapier as soon as the alert is queued, and 5 retries to your endpoint.

More guides

HoldAlarms is not affiliated with Zapier, Make, n8n or Grafana Labs. Their names are trademarks of their owners.