Docs / Vendor onboarding

Connect Intercom webhooks to Relin

Relin receives Intercom webhooks, verifies signatures, stores payloads, and delivers them to your endpoints with retries, alerts, and replay.

Open the Intercom dashboard

Before you start

  • Create a Relin workspace and sign in.
  • Have admin access to the Intercom account where you'll configure the webhook.
  • Decide which events you want to capture, or start with "all events" if you're exploring.

Setup steps

  1. In Relin, open your workspace and click New source. Pick the Intercom tile.
  2. Copy the ingest URL Relin shows. This URL is shown once, so store it.
  3. Open your Intercom app's Webhooks settings.
  4. Send notification topics to the Relin source URL.
  5. Paste the app's client secret here.
  6. Save and send a test event from Intercom. Confirm Relin received it in your workspace.

Client secret: Paste the Intercom app's client secret. Intercom signs webhooks with HMAC-SHA1 of the body using this secret.

What Relin does next

  • Verifies the signature on every incoming event and records the status (verified, failed, unchecked).
  • Stores the payload so you can replay or inspect it later, bounded by your workspace retention window.
  • Delivers the event to every destination you've connected to this source, with retries and per-destination rate limits.
  • Surfaces lifecycle gaps (for vendors with known lifecycles) as anomalies you can triage from the dashboard.

Test it

The fastest check is the events view in your workspace. After you send a test event from Intercom, it appears within a second or two. Click into the event to see the raw payload, signature status, and the delivery attempts to your destinations.

You can also use the REST API or the MCP tools to inspect the stream programmatically.

Intercom-specific notes

  • Intercom signs webhooks using your Intercom app's client secret, not a per-webhook secret. You paste the client secret into the signing-secret field.

Troubleshooting

  • Signature status is failed: the client secret doesn't match. Re-copy it from Intercom and update the Relin source.
  • Signature status is unchecked: no signing secret is configured on the source yet. Paste the secret on the source settings page.
  • No events arriving: check that the ingest URL in Intercom matches the URL Relin shows, including the token segment at the end.
  • Events arrive but destinations fail: open the delivery attempts tab on the event detail page. Each attempt shows the response body, status, and timing.

Next