Source type
HubSpot Source Configuration
HubSpot sources receive CRM, app, object, and subscription callbacks with HubSpot request signature v3 verification.
HubSpot configuration
Create a HubSpot 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 HubSpot delivery before it enters the routing workflow.
Source TypeHUBSPOT
Allowed methodsPOST, PUT, PATCH, DELETE
AuthenticationProvider signature
Credential fieldsClient Secret
{
"type": "HUBSPOT",
"config": {
"auth_type": "PROVIDER_SIGNATURE",
"auth": {
"provider": "HUBSPOT",
"webhook_signing_secret": "provider-secret"
},
"allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
}
}HubSpot request contract
FastHook signs method + request URI + raw body + timestamp with HMAC-SHA256 and compares the base64 digest.
HubSpot headers
Preserve x-hubspot-signature-v3, x-hubspot-request-timestamp when sending HubSpot 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-hubspot-signature-v3Base64 HMAC-SHA256 signature.
x-hubspot-request-timestampMillisecond timestamp included in the signed payload.
HubSpot setup
- Point the HubSpot webhook subscription at the FastHook Source URL.
- Use the HubSpot app client secret in FastHook.
- Keep the public URL stable because the method and URI are part of the signed payload.
HubSpot routing hints
- HubSpot subscription callbacks usually route by subscriptionType, objectId, appId, or property changes.
- Keep the public URL stable because the signed URI is part of HubSpot v3 verification.