Source type

HubSpot Source Configuration

HubSpot sources receive CRM, app, object, and subscription callbacks with HubSpot request signature v3 verification.

HUBSPOTPOST, PUT, PATCH, DELETEClient SecretProductivity
HubSpot sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.HubSpotProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLHUBSPOTProvider 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.

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 Type

HUBSPOT

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Credential fields

Client Secret

HubSpot source config
{
  "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.

POSTPUTPATCHDELETE

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-v3

Base64 HMAC-SHA256 signature.

x-hubspot-request-timestamp

Millisecond timestamp included in the signed payload.

HubSpot setup

  1. Point the HubSpot webhook subscription at the FastHook Source URL.
  2. Use the HubSpot app client secret in FastHook.
  3. 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.

Continue with HubSpot