Docs › Setup guides › Zapier, Make, n8n, Grafana
Zapier, Make, n8n and Grafana
Any tool that can send an HTTP POST can send alerts to HoldAlarms. Use your HoldAlarms webhook URL as the request URL. HoldAlarms answers as soon as the alert is queued, then forwards the body unchanged to your destinations and retries if they fail.
Rules for every tool
- Use POST. HoldAlarms doesn't accept PUT or other methods on the webhook URL.
- The URL looks like
https://api.holdalarms.com/hook/<your token>. Query parameters on it are not forwarded. - JSON, plain text, form fields and XML are all forwarded unchanged, with the same content type.
- The token in the URL identifies your account. Keep it out of shared screenshots, exported workflows and public templates.
- Custom headers you add in the tool are not passed on to your destinations. Put anything your endpoint needs into the body.
Optional: keep the token out of the URL
Some tools save the webhook URL where others can read it. Grafana, for example, stores it in plain text. If your tool can add a request header, you can send the token in a header instead of the URL:
- URL:
https://api.holdalarms.com/ingest - Method:
POST - Header:
X-Hook-Token: <your token>(the part after/hook/in your webhook URL)
HoldAlarms treats it exactly like /hook/<your token>. The header is not passed on to your destinations. Zapier (Custom Request), Make and n8n (Send Headers) can all add headers; in Grafana it depends on whether your version offers custom HTTP headers for the webhook contact point. If it doesn't, keep the normal URL and limit who can view contact points.
Zapier
- In the Zap editor, add an action step and choose Webhooks by Zapier.
- Pick POST (Zapier builds the body for you) or Custom Request (you type the body yourself).
- Set Payload Type to JSON, put your HoldAlarms webhook URL in URL, and fill in Data.
- Test the step, then check recent alerts on your dashboard.
Zapier's help page lists Webhooks by Zapier actions for its Team and Enterprise plans, so check yours (Zapier: send webhooks in Zaps).
Make
- Add the HTTP app and choose the Make a request module.
- Paste your HoldAlarms webhook URL in URL and choose POST.
- For Body content type pick application/JSON, or Custom with
text/plainfor a text message. - Run the scenario once and check recent alerts on your dashboard.
Source: Make: HTTP modules.
n8n
- Add an HTTP Request node, set Method to POST and URL to your HoldAlarms webhook URL.
- Turn on Send Body and pick JSON, or Raw with a content type such as
text/plain. - Run the node and check recent alerts on your dashboard.
n8n's own Retry On Fail setting reruns the node if HoldAlarms can't be reached. HoldAlarms then handles retries to your endpoint. Sources: n8n: HTTP Request node, n8n: node settings. Sending TradingView alerts into n8n instead? See TradingView → HoldAlarms → n8n.
Grafana
- Go to Alerts & IRM → Alerting → Notification configuration → Contact points and click + Add contact point.
- Choose the Webhook integration and paste your HoldAlarms webhook URL in URL.
- Leave HTTP Method on POST, then click Save contact point.
Grafana sends a JSON body with an alerts list; each alert has a fingerprint you can use to spot repeats. Grafana stores the webhook URL in plain text and shows it when the contact point is read back, so anyone who can view the contact point can see your token (see Optional: keep the token out of the URL above). The HMAC signature header Grafana can add is not passed on to your endpoint. Source: Grafana: webhook notifier.
Step-by-step guides: Zapier, Make, n8n, Grafana.
HoldAlarms is not affiliated with Zapier, Make, n8n or Grafana Labs. Their names are trademarks of their owners.
← cTrader setup · Retries & failed alerts →
HoldAlarms is not affiliated with TradingView. TradingView is a trademark of TradingView, Inc.