Outputs · Outgoing webhooks
ProWhen a room fires, the world hears it.
Point a room at a URL and PingRoom calls it every time the room Pings. Send the signed event to your backend, automation adapter, dashboard, or logging pipeline.
How it works
Point at a URL
Give a room one outgoing webhook: your backend, an automation adapter, or any HTTPS endpoint that accepts PingRoom's JSON event.
Something happens
A Ping fires: a tap, a webhook, a geofence, a schedule, an agent. It doesn't matter how the room was raised.
Your URL gets called
PingRoom POSTs a compact, signed event to your endpoint, independently of who's around to be Pinged.
What lands at your URL.
The event can contain the room name and code, message body, sender display name, structured data, and acknowledgement state. Treat it as sensitive, verify the signature, then process it.
POST <your URL>
X-PingRoom-Signature: 3a7f… (v1, hex HMAC-SHA256)
X-PingRoom-Signature-V2: 9c21… (verify this one)
X-PingRoom-Timestamp: 1780000000
X-PingRoom-Delivery: 6f1c…
Content-Type: application/json
{
"event": "ping",
"room": { "name": "Build Alerts", "code": "ABC123" },
"title": "Deploy finished",
"body": "CI: Production is live ✅",
"sender": "CI",
"action_number": 1,
"trigger_source": "webhook",
"timestamp": "2026-06-02T18:24:05+00:00"
}
Full field reference, signature verification, retry behavior, and SSRF rules live in the webhook docs.
Delivered at the edge
Outgoing calls run through a globally distributed Cloudflare Worker: low-latency, wherever your endpoint lives.
Signed and retried
Every delivery carries an HMAC-SHA256 signature and a timestamp, and retries up to three times on transient failure.
Fires even when no one's home
The outgoing call is independent of push recipients, so it delivers even when nobody is around to be Pinged.
Good for
Forward every Ping onward.
Download PingRoom, create a room, point it at your endpoint. Done.
Download the app