Intercom webhooks
Test and debug Intercom webhooksfor conversations, tickets and users
Follow conversation updates, user events and support automations without guessing what Intercom sent. Hooklistener records each webhook so you can debug handoffs and enrichment fast.
How Intercom webhooks work
| Where to configure it | Developer Hub > your app > Configure > Webhooks. The endpoint must be HTTPS and answer a HEAD request, which Intercom uses to validate it. Topics can only be subscribed in the Developer Hub, not through the API. |
|---|---|
| Signature header | X-Hub-Signature: sha1= followed by the hex HMAC-SHA1 of the JSON body, keyed with your app's client_secret. |
| Timeout | Intercom resends a notification if it does not get HTTP 200 within 5000 ms, so slow handlers see duplicates. |
| Retries | 4xx (except 429) and 5xx responses are retried after 1 minute; if the second retry fails, the delivery is marked failed. A 410 disables the subscription. |
| 429 handling | A 429 throttles the subscription with delays from 1 minute to 2 hours; notifications delayed more than 2 hours are dropped. |
See every Intercom event your app receives
Intercom webhooks drive support queues, onboarding flows and lifecycle automation. When a conversation event is malformed or delayed, the result is slower responses and a broken customer experience.
Hooklistener captures each Intercom delivery with its payload so you can follow message events, inspect user updates and replay (Pro) webhooks to test environments before changes reach customers.
Why support teams need a webhook debugger
Unreadable event payloads
Conversation and user events are hard to read at a glance, which slows down both support and engineering.
Queue and handoff bugs
A small webhook issue can send a customer to the wrong queue, and nobody sees the payload that caused it.
Silent lifecycle failures
Onboarding and enrichment flows often fail without obvious alerts, so nobody knows where the pipeline broke.
How Hooklistener helps with Intercom webhooks
Prettified Intercom payloads
Read each Intercom conversation or user event as formatted JSON with its headers, so support and engineering can both see what arrived.
Replay (Pro) a misassigned conversation
Resend the captured Intercom event that put a customer in the wrong queue to localhost or staging, and confirm the handoff logic is fixed before customers see it.
Inactivity monitors for lifecycle flows
Get an email, Slack or signed-webhook alert when Intercom onboarding or enrichment events stop arriving, instead of finding out from a customer.
Try it: point Intercom at a free webhook URL or run a test with the webhook tester.
Intercom automation plays that reduce friction
Support queue assignment
Assign conversations by topic, plan or customer segment, and check that the webhook payload carries the fields you rely on.
Customer onboarding
Trigger welcome sequences, CSM handoffs and lifecycle updates when key Intercom events arrive.
Product-led support ops
Connect product usage events to Intercom so your team can respond faster to churn risk and expansion signals.
Replay a failed webhook without re-triggering the provider
Once a delivery is captured, you can resend its exact headers and body to localhost, staging or production from the dashboard or through your coding agent over MCP, so the provider never has to fire a new event. Replay is on Pro and above. Read the replay guide.
Comparing webhook debugging tools?
See how Hooklistener stacks up against webhook.site, RequestBin, Beeceptor, Hookdeck and ngrok in the best tools to capture and inspect webhook payloads, or read the head-to-head pages for Hooklistener vs ngrok and Hooklistener vs Beeceptor.
Frequently asked questions
Can I inspect Intercom conversation events in Hooklistener?
Yes. Capture Intercom webhooks and inspect the full event payload, including conversation changes, user data and when each one arrived.
Does Hooklistener help with queue assignment issues?
Yes. Use the stored webhook history to follow your assignment logic and find malformed payloads. Replay is on Pro and above.
Can I test changes without affecting customers?
Yes. Replay (Pro) captured Intercom webhooks to staging or internal endpoints, or forward them to localhost with hooklistener tunnel, so you can check workflow changes safely.
Is this useful for support and ops teams?
Yes. Support, customer success and engineering can open the same shareable debugger link to understand what happened and why.
Make Intercom workflows dependable
Capture every customer event, spot handoff problems early and keep support automation working.