Agent skill · software engineering · jeremylongshore
intercom-webhooks-events
Implement Intercom webhook handling and data event tracking.
Why this skill is useful
Provides specific implementation details and patterns for handling Intercom webhooks and events that the AI wouldn't reliably generate on its own.
What it needs
Requires intercom-client installed locally. Requires intercom account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Intercom Webhooks & Events Overview Handle incoming Intercom webhooks (notifications) with signature verification and implement outbound data event tracking via the Events API. Incoming webhooks push conversation and contact changes to your endpoint; outbound data events push custom activity into Intercom for segmentation and messaging. The full, copy-ready code lives in references/; this file walks the workflow at a high level so you can follow it start to finish, then drill in for depth. Prerequisites HTTPS endpoint accessible from internet Webhook secret from Intercom Developer Hub Access token from Intercom Developer Hub (for outbound data events) intercom-client SDK installed Redis or database for idempotency (recommended) Authentication Two distinct credentials, both issued from the Intercom Developer Hub and read from environment variables — never hard-code them: Incoming webhooks are verified with INTERCOMWEBHOOKSECRET. Intercom signs every delivery with HMAC-SHA1 in the X-Hub-Signature header; you recompute the digest over the raw request body and compare with crypto.timingSafeEqual. Reject any request that fails or is missing the header. Outbound data events authenticate with a bearer INTERCOMACCESSTOKEN passed to IntercomClient. Instructions Read the relevant reference file, then use Write/Edit to scaffold the handler into the target project. 1. Build the signed endpoint. Create an Express route that captures the raw body (express.raw), verifies the X-Hub-Signature HMAC-SHA1 digest against INTERCOMWEBHOOKSECRET, and returns 200 within 5 seconds — Intercom treats a slower response as a failure. Respond first, process after. See incoming webhooks walkthrough Step 1. 2. Model the payload. Every delivery is a notificationevent envelope carrying topic, id, and data.item (the changed resource). Type it so the router is safe. See incoming webhooks walkthrough Step 2. 3. Route by topic. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/intercom-webhooks-events