Source type

Close CRM Source Configuration

Close CRM sources receive Event Log webhook subscriptions for leads, contacts, opportunities, activities, and other CRM objects.

CLOSEPOSTSignature KeyProductivity
Close sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.CloseProviderPOSTSignedFastHookSource URLCLOSEProvider 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.

Close CRM configuration

Create a Close CRM source, keep POST enabled, and provide the configured Signature Key values for provider signature. FastHook uses these settings to validate each Close delivery before it enters the routing workflow.

Source Type

CLOSE

Allowed methods

POST

Authentication

Provider signature

Credential fields

Signature Key

Close CRM source config
{
  "type": "CLOSE",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "CLOSE",
      "webhook_signing_secret": "hex-signature-key"
    },
    "allowed_http_methods": ["POST"]
  }
}

Close CRM request contract

FastHook decodes the hexadecimal signature key and verifies HMAC-SHA256 over timestamp + raw-body.

POST

Close headers

Preserve close-sig-hash, close-sig-timestamp when sending Close 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.

close-sig-hash

Hex HMAC-SHA256 signature.

close-sig-timestamp

Unix timestamp prepended to the raw body.

Close setup

  1. Create a Close webhook subscription for the required object types and actions.
  2. Use the FastHook Source URL as the subscription URL.
  3. Copy the one-time signature_key returned by the subscription API into FastHook.
  4. Use event.id for duplicate protection and the Event Log API for historical recovery.

Continue with Close CRM