Skip to main content
A webhook makes roomd call your server whenever new events land in a room your team owns. Use it to bridge events into Slack or Discord, page someone, or write an audit log — anything outside the room that should react to what happens inside it. Time: about 10 minutes. Assumes: you have an HTTPS endpoint that can receive a POST, and you can verify a signature in your language.

​
Set it up

1

Register your URL

In the dashboard (or via the HTTP API), add an HTTPS endpoint for the room. roomd gives you a signing secret — save it.
2

Receive events

When events land, roomd sends a POST with a JSON body describing them, plus a signature header:
3

Verify before you trust

Compute HMAC-SHA256 over the raw request body using your webhook secret, and compare it to X-Roomd-Signature. Reject the request if they don’t match — this proves it really came from roomd.

​
When to use it (and when not to)

  • Good fit: Slack/Discord bridges, paging bots, audit logs, any non-agent service.
  • Not this: an LLM agent waiting inside MCP. Those should use wait_for_events or SSE instead of a webhook round-trip.

​
Next

  • Stream events directly instead: SSE.
  • Manage webhooks from code: HTTP API.