Integrations
Navi.sh can receive alerts from any monitoring tool that supports outgoing webhooks. Each integration gets its own token-protected URL that you configure once in your tool's settings.
How it works
- In your Navi.sh workspace go to Services → <your service> → Integrations.
- Create a new integration and copy the webhook URL.
- Paste the URL into your monitoring tool's webhook settings.
- Alerts fire and resolve automatically — no polling, no agents.
Supported integrations
| Integration | Path | Auto-resolve signal |
|---|---|---|
| Generic Webhook | /api/v1/events/webhook/{token} | "status": "resolved" |
| Datadog | /api/v1/events/datadog/{token} | alert_transition: "Recovered" |
| Prometheus Alertmanager | /api/v1/events/prometheus/{token} | status: "resolved" per alert |
| Grafana | /api/v1/events/grafana/{token} | status: "resolved" per alert |
| AWS CloudWatch | /api/v1/events/cloudwatch/{token} | NewStateValue: "OK" |
| New Relic | /api/v1/events/newrelic/{token} | current_state: "closed" |
| Sentry | /api/v1/events/sentry/{token} | action: "resolved" |
Token authentication
Every ingestion URL embeds a unique token:
https://api.navi.sh/api/v1/events/datadog/<token>The token is scoped to a single service integration. If a token is compromised, rotate it from the Integrations settings — existing incidents are preserved.
All endpoints respond 202 Accepted
Processing is asynchronous. A 202 response means the payload was received and queued — not that an incident was necessarily created (e.g. a duplicate or resolved event may produce no visible change).