What does the webhook payload look like?

The payload is a JSON object with: event (monitor.down / monitor.up / ssl.expiry), monitor (id, name, url, type), reason (human-readable failure description), regions_confirming, detected_at, and resolved_at (for recovery events).

Can I use the webhook integration with Zapier or Make?

Yes. Create a Zapier or Make webhook trigger URL and paste it into Nodown as the webhook endpoint. The JSON payload maps to automation fields automatically.

What happens if my endpoint is down when Nodown tries to deliver?

Nodown retries failed deliveries with exponential backoff. If all retries fail, the delivery is logged as failed in your integration history so you can review missed events.

All integrations

Nodown + Webhook

Send Nodown alerts to any endpoint with a custom JSON payload.

Connect Webhook free View pricing

Free to start · No credit card required

What an alert looks like

Webhook alert

POST https://yourapp.com/hooks/nodown
Content-Type: application/json

{
  "event": "monitor.down",
  "monitor": { "name": "API", "url": "https://api.yourapp.com" },
  "reason": "503 Service Unavailable",
  "detected_at": "2026-05-29T14:32:07Z"
}

Why teams use Nodown with Webhook

The Webhook integration sends a JSON POST request to any URL you specify when a monitor triggers an alert. Use it to connect Nodown to internal tools, custom dashboards, IFTTT, Zapier, n8n, or any service that accepts HTTP.

Connect anything

If a tool accepts an HTTP POST, Nodown can send to it. Build custom alert pipelines, trigger automation workflows, or fan out to multiple tools from a single webhook.

Custom headers

Add custom headers to your webhook requests — API keys, authorization tokens, content-type overrides — to authenticate against any endpoint.

Structured JSON payload

Every webhook payload includes monitor details, event type, failure reason, region count, and timestamps. Parse it with any JSON-capable tool.

Delivery retries

Nodown retries failed webhook deliveries automatically. If your endpoint is temporarily unreachable, alerts queue and retry so you do not miss incidents.

How to connect Webhook to Nodown

Set up takes about 2 minutes. No code required.

1

Prepare your endpoint

Set up a URL that accepts POST requests with a JSON body. This can be an internal service, a serverless function, or a third-party automation tool like Zapier, Make, or n8n.
2

Add the integration in Nodown

Go to Alerting → Integrations → New Integration → Webhook. Enter the URL, add any required headers (e.g. Authorization: Bearer <token>), and click Test to send a sample payload.
3

Inspect the payload and build your handler

The test request shows the full JSON payload Nodown sends. Build your handler to process the event field (monitor.down, monitor.up, ssl.expiry) and the nested monitor object.
4

Assign to monitors

Attach the webhook integration to any monitor that should trigger your endpoint. Multiple monitors can use the same webhook URL.

Get started free

Frequently asked questions

What does the webhook payload look like?: The payload is a JSON object with: event (monitor.down / monitor.up / ssl.expiry), monitor (id, name, url, type), reason (human-readable failure description), regions_confirming, detected_at, and resolved_at (for recovery events).
Can I use the webhook integration with Zapier or Make?: Yes. Create a Zapier or Make webhook trigger URL and paste it into Nodown as the webhook endpoint. The JSON payload maps to automation fields automatically.
What happens if my endpoint is down when Nodown tries to deliver?: Nodown retries failed deliveries with exponential backoff. If all retries fail, the delivery is logged as failed in your integration history so you can review missed events.