Intercom Webhook Tester — Test & Inspect Intercom Webhooks Online

If you are wiring up Intercom webhooks, the first question is always the same: what does Intercom actually send? The docs show an idealised payload, but the real request — its headers, its X-Hub-Signature header, the exact JSON shape — is what your handler has to parse. A Intercom webhook tester gives you a public URL that captures those real requests so you can read every byte before you write any code.

Get a free Intercom webhook tester URL

The fastest way is our free Webhook Bin — a no-code webhook tester that gives you an instant public URL and stores every request that hits it, headers and body included. No signup, no deploy:

1. Open the Webhook Bin and copy the URL it generates for you.
2. In the Developer Hub → your app → Webhooks, add a webhook endpoint and paste that URL.
3. Trigger an event (see below) and watch the request land in the bin in real time.

Because the bin keeps the full request, you can inspect the X-Hub-Signature header, the Content-Type, and the complete payload — the three things you need to build and verify a handler.

What a Intercom webhook looks like

Intercom delivers webhooks as an HTTP POST with a application/json body. Intercom wraps every event in a notification_event envelope with a topic field, and signs with the older X-Hub-Signature (SHA-1) scheme — capture one to see the deeply nested data.item structure.

A typical conversation.user.created payload looks like this:

{
  "type": "notification_event",
  "topic": "conversation.user.created",
  "data": {
    "item": {
      "type": "conversation",
      "id": "...",
      "source": {
        "author": {
          "type": "user",
          "email": "[email protected]"
        }
      }
    }
  }
}

Common Intercom events you will want to test:

• conversation.user.created
• conversation.admin.replied
• contact.created

Verifying the Intercom signature

Intercom signs each request so you can prove it really came from Intercom. The signature travels in the X-Hub-Signature header and is HMAC-SHA1 of the raw request body, using your app's client secret. Capture a real request first, then use our HMAC signature verifier and the verify a webhook signature guide to confirm your verification logic against a payload you can actually see.

From inspecting to receiving on localhost

A bin is perfect for seeing the payload. When you are ready to drive your local handler with real Intercom events — without deploying — forward them straight to localhost with the Webhook Relay agent. The full walkthrough is here: Receive Intercom webhooks on localhost.

That gives you a stable public URL that tunnels to your machine, so Intercom keeps delivering to the same endpoint while you iterate on localhost, no firewall changes or public IP required.

Test Intercom webhooks online in three steps

1. Capture — point Intercom at a Webhook Bin URL and inspect the real request.
2. Verify — confirm the X-Hub-Signature header with the HMAC verifier.
3. Forward — when the shape is clear, receive Intercom webhooks on localhost and build your handler.

New to webhooks in general? Start with what is a webhook and how to test webhooks.

Ready to inspect your first Intercom event? Open a free Webhook Bin and paste the URL into Intercom.