Source type
Close CRM Source Configuration
Close CRM sources receive Event Log webhook subscriptions for leads, contacts, opportunities, activities, and other CRM objects.
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 TypeCLOSE
Allowed methodsPOST
AuthenticationProvider signature
Credential fieldsSignature Key
{
"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.
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-hashHex HMAC-SHA256 signature.
close-sig-timestampUnix timestamp prepended to the raw body.
Close setup
- Create a Close webhook subscription for the required object types and actions.
- Use the FastHook Source URL as the subscription URL.
- Copy the one-time signature_key returned by the subscription API into FastHook.
- Use event.id for duplicate protection and the Event Log API for historical recovery.