Integrations
What does Vigila connect to?
Vigila runs its own HTTP checks and accepts alerts from Better Stack, UptimeRobot, Grafana, PagerDuty or any tool that can POST JSON; each opens a draft incident for your team to confirm. Published updates go out by email, signed webhooks, Slack, RSS and Atom. Nothing else is claimed here.
| Integration | Status | How it works |
|---|---|---|
| HTTP checks | Live | Run from Vigila's servers on your interval, with status-code ranges, an optional keyword and failure/recovery thresholds; every redirect is checked against private addresses. |
| Generic JSON alerts | Live | POST { title, status, message, id, started_at } to an integration's secret address; trigger opens a draft incident, resolve records a fact. |
| Better Stack (Uptime) | Live | Its incident webhook (JSON:API format) is read for the monitor name, cause, start and resolve times. |
| UptimeRobot | Live | Its alert-contact webhook (JSON or form fields): alertType 1 opens a draft, 2 records recovery. |
| Grafana alerting | Live | Unified alerting webhooks: firing opens a draft incident, resolved records a fact; matched by group key. |
| PagerDuty | Live | V3 webhooks: incident.triggered opens a draft incident; incident.resolved records a fact. |
| Email subscribers (Resend) | Live | Double opt-in and one-click unsubscribe (RFC 8058) on every update email. |
| Webhook subscribers | Live | Signed JSON (X-Vigila-Signature: HMAC-SHA256 of timestamp and body) for every published update. |
| Slack | Live | An incoming-webhook address per page; each published update is posted to the channel. |
| RSS, Atom and status.json | Live | Feeds of published updates and a JSON summary for public pages. |
| Custom domains | Early access | Added through Render's custom-domain API, verified by DNS, served with HTTPS (Team and Business). |
“Early access”: built and working, not yet verified with a real customer account. No other integrations exist today; inbound email and SMS notifications aren't offered.