Custom incident dashboards
Pipe incidents into your own internal tools — Linear, Notion, a custom incident-management UI, an SQL warehouse for reporting.
Generic integration
Uptimera + Webhooks
If a tool isn't one of Uptimera's first-class integrations, you can almost certainly connect it via a generic webhook. Every incident open and recovery fires a JSON POST to whatever URL you configure — internal dashboards, custom paging logic, automation tools, you name it. Add a signing secret and each payload is HMAC-SHA256 signed.
Availability: Available on the Business plan — webhook alert channels are a Business-plan feature. The Free plan sends email alerts; Pro adds Slack.
Setup
- 1
Create the webhook channel
In Uptimera, open Alerts → Add Channel → Webhook and keep the Format on "Generic JSON". Provide the HTTPS endpoint that should receive the events.
- 2
Add a signing secret (optional but recommended)
Set a signing secret on the channel. When present, every payload is signed with HMAC-SHA256 and the signature is sent in the X-Uptimera-Signature header as sha256=<hex>.
- 3
Verify signatures on your side
Recompute the HMAC over the raw request body with your secret and reject any request where it doesn't match the header. This ensures the payload actually came from Uptimera.
- 4
Handle the event types
The payload's event field is monitor.down on an incident and monitor.up on recovery (plus monitor.ssl_expiring for certificate warnings). Each includes the monitor name, URL, incident id, and a timestamp.
What teams do with this
Stop the build on outage
Use a webhook to flip a feature flag or block deploys while production is degraded.
Auto-create tickets
Wire a webhook into Linear, Jira, or GitHub Issues to create a ticket for every incident — tagged with the monitor, cause, and incident id.
Common questions
What format is the payload?
JSON. The body carries the event type, a monitor object (name, url), an incident object (id, cause, durationSeconds), and an ISO-8601 timestamp. The signing scheme (HMAC-SHA256 over the raw body, sent as X-Uptimera-Signature) is stable.
How are retries handled?
Delivery is currently a single best-effort POST; a failure is recorded server-side against the channel but not automatically retried. If your receiver needs at-least-once delivery, ACK quickly and configure a fallback channel on critical monitors. Automatic retry with backoff is on the roadmap.
Can I point several tools at the same events?
Yes — add multiple webhook channels (or a mix of webhook, Slack, and email channels) and attach whichever you want to each monitor. Every attached channel receives the incident and recovery events independently.
Ready to set this up?
Connect Webhooks to Uptimera in under 2 minutes. Free plan included.