Questions › Guides

n8n: send alerts from a workflow that get retried

Short answer: Add an HTTP Request node, set Method to POST and URL to your HoldAlarms webhook URL, and turn on Send Body. HoldAlarms answers n8n as soon as the alert is queued, then delivers it to your endpoint and retries if it fails (n8n: HTTP Request node).

n8n has its own Retry On Fail setting for a node (n8n: node settings). Turn it on for the HTTP Request node. Sending TradingView alerts into n8n instead? See TradingView → HoldAlarms → n8n.

Why alerts get lost

  1. Your endpoint is down or restarting. n8n gets an error and the step fails; your endpoint never gets that alert.
  2. Slow replies. n8n waits on your endpoint, and a timeout fails the step.
  3. Nobody notices. A failed step shows in n8n'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 n8n, add an HTTP Request node: Method POST, URL your webhook URL, Send Body on, Body Content Type JSON (or Raw with text/plain).
  4. Send one test and check Recent alerts on your dashboard.

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

What HoldAlarms does

We answer n8n 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

Should I turn on n8n's Retry On Fail?

Yes, on the HTTP Request node. It reruns the node if HoldAlarms can not be reached. HoldAlarms then retries your own endpoint up to 5 times.

Is this the same as sending TradingView alerts into n8n?

No. This guide sends alerts out of n8n. For TradingView into n8n see the TradingView, HoldAlarms and n8n guide.

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 n8n 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.