StatusPulse StatusPulse
← All features

Integrations · Pro+

Outbound integration webhooks

You don't need StatusPulse to build a native PagerDuty connector — point a signed webhook at the receiver and your existing on-call routing takes over.

Why you need it

Your ops stack already knows who's on call, when to escalate, and how to wake people up. The last thing you need is another tool fighting for that responsibility. Outbound webhooks let StatusPulse hand the alert off to the tools that already do the routing.

  • Plug into PagerDuty, Opsgenie, Zapier, or your own. Any HTTPS endpoint that accepts a POST gets a webhook — no native connector required, no per-vendor lock-in, no "we'll build that in Q3".
  • Signed payloads your receiver can trust. Every delivery carries a Stripe-style X-StatusPulse-Signature: t=…,v1=… HMAC-SHA256 header — drop the secret into the same verifier you wrote for Stripe webhooks and you're done.
  • Custom headers per webhook. Paste an Authorization: Token … for PagerDuty, Authorization: GenieKey … for Opsgenie, or whatever your internal bus expects — no proxy in the middle.
  • Retries that survive your downtime, not just ours. Failed deliveries back off at 30 s, 60 s, 120 s, 240 s (five attempts) with a stable delivery id across retries — so writing an idempotent receiver is one line of code.
  • Send-test and rotate-secret built in. Prove the wiring with one click, rotate the HMAC key when a contractor leaves, no engineering ticket either way.

Where it pays off

The default integration any time your ops tooling already exists:

  • PagerDuty Events v2. POST to events.pagerduty.com/v2/enqueue with the routing key in the header; on-call wakes on open and auto-resolves on close.
  • Opsgenie alerts. Same shape, different URL — map the StatusPulse severity to an Opsgenie priority through your existing alert policy.
  • Zapier / Make.com / n8n. Pipe incidents into anything with a no-code connector — Discord, Linear, JIRA, a Google Sheet, a customer's webhook receiver.
  • Your internal ops bus. A single receiver that fans out further — opens a tracking ticket, posts to a war-room channel, appends to a public-facing API, all from one signed POST.

Not the right tool when: all you want is a Slack or Teams channel pinged — use the built-in integrations for those; running your own receiver for one channel is over-engineering.

Available on Pro+. Already on StatusPulse? See the full config in Help →

Related

Try Outbound integration webhooks in StatusPulse

5 probes, 1 status page, forever. No credit card. US or EU host — you choose.

Start free See pricing