Integrations

Close CRM Webhooks Integration

Close webhook subscriptions deliver real-time Event Log changes for leads, contacts, opportunities, activities, and other CRM objects.

Capture the original request first, enforce the available trust boundary, then route and replay from durable evidence.

How the integration works

  • Each subscription returns a signature_key that is displayed when the subscription is created.
  • close-sig-hash is HMAC-SHA256 over close-sig-timestamp concatenated with the raw payload.
  • The signature key is hexadecimal and must be decoded to key bytes before verification.
  • Close retains Event Log history for up to 30 days for historical reprocessing.

Create the FastHook source

Create CLOSE source
curl -X POST "https://api.fasthook.io/v1/sources" \
  -H "Authorization: Bearer $FASTHOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Close CRM Webhooks Integration",
    "type": "CLOSE",
    "config": {
      "auth_type": "PROVIDER_SIGNATURE",
      "auth": {
        "provider": "CLOSE",
        "webhook_signing_secret": "hex-signature-key"
      },
      "allowed_http_methods": ["POST"]
    }
  }'

Setup

  1. Create a CLOSE source and copy its Source URL.
  2. Create a Close webhook subscription for the required object types and actions.
  3. Copy the returned signature_key into FastHook.
  4. Trigger a CRM change, verify the delivery, and route by event.object_type and event.action.

Production notes

  • Capture the signature key when creating the subscription.
  • Use event.id for idempotency.
  • Keep SSL verification enabled on the Close subscription.

Related documentation