Integrations

HubSpot Webhooks Guide

HubSpot webhooks send CRM, object, app, and subscription changes to your systems. Those events often feed lead routing, lifecycle automation, enrichment, billing handoffs, and customer operations, so losing a delivery can create gaps across several teams.

FastHook gives HubSpot a stable source URL, verifies HubSpot request signature v3, stores request evidence, routes accepted events through connection rules, and keeps retry and replay controls close to failed destinations.

Provider ingress contract for signed HubSpot webhook delivery.
Keep the HubSpot public source URL stable. Signature validation depends on the request method, URI, raw body, and timestamp.

HubSpot signature headers

  • x-hubspot-signature-v3: Base64 HMAC-SHA256 signature.
  • x-hubspot-request-timestamp: millisecond timestamp included in the signed payload.

Create a HubSpot source

Create HubSpot source
curl -X POST "https://api.fasthook.io/v1/sources" \
  -H "Authorization: Bearer $FASTHOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "HubSpot production",
    "type": "HUBSPOT",
    "config": {
      "auth_type": "PROVIDER_SIGNATURE",
      "auth": {
        "provider": "HUBSPOT",
        "webhook_signing_secret": "hubspot-client-secret"
      },
      "allowed_http_methods": ["POST", "PUT", "PATCH", "DELETE"]
    }
  }'

Routing strategy

  • Route contact, company, deal, and ticket events to destinations that own those workflows.
  • Keep enrichment and sales automation isolated from billing or support side effects.
  • Use idempotency when HubSpot object updates can arrive more than once.
  • Replay narrow time windows after fixing a broken CRM destination.

Related guides