Source type

Intercom Source Configuration

Intercom sources receive signed notification webhooks for conversations, contacts, admins, and workspace events.

INTERCOMPOST, PUT, PATCH, DELETEClient SecretProductivity
Intercom webhooks documentationAll source types
Intercom sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.IntercomProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLINTERCOMProvider credentialsignatureVerify before queue401 on auth failure405 on wrong methodAcceptedRequestverified: trueConnections route the accepted request to destinationsFilters, transformations, retries, replay, and destination signatures stay downstream from source verification.

Intercom configuration

Create a Intercom source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Client Secret values for provider signature. FastHook uses these settings to validate each Intercom delivery before it enters the routing workflow.

Source Type

INTERCOM

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Credential fields

Client Secret

Intercom source config
{
  "type": "INTERCOM",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "INTERCOM",
      "webhook_signing_secret": "provider-secret"
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

Intercom request contract

FastHook computes sha1= HMAC-SHA1 over the raw body and compares it with x-hub-signature.

POSTPUTPATCHDELETE

Intercom headers

Preserve x-hub-signature when sending Intercom test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.

x-hub-signature

sha1= HMAC-SHA1 signature over the raw body.

Intercom setup

  1. Create an Intercom webhook subscription and point it at the FastHook Source URL.
  2. Enable signed notifications with a hub_secret.
  3. Use that same secret in the FastHook Client Secret field.

Continue with Intercom