Skip to main content
Use webhooks to send identified company data to any URL in real-time. Build custom integrations, power internal tools, or connect to any service.

Features

  • Real-time delivery when events occur
  • Custom endpoints - send to any URL
  • Flexible payload with full company data
  • Retry logic for failed deliveries
  • Secret authentication for security
  • Delivery logs for debugging

Setup

  1. Go to SettingsIntegrationsWebhooks
  2. Click Create Webhook
  3. Enter a name and your endpoint URL
  4. Optionally add a secret for signature verification
  5. Save and activate

Webhook Events

Configure which events trigger your webhook via Automations:

Payload Format

Contact Revealed Payload

The phone field is only included when a phone number has been revealed for the contact.

Security

Signature Verification

If you add a secret, each webhook request includes a Signature header. The signature is an HMAC-SHA256 hash of the request body using your secret as the key, so it will be different for every request.
Verify the signature by computing HMAC-SHA256 of the raw JSON request body with your secret and comparing it to the header value:

Retry Logic

Failed webhook deliveries are retried automatically: After 5 failed attempts, the delivery is marked as failed and logged.

Viewing Logs

  1. Go to IntegrationsWebhooks
  2. Click on your webhook
  3. Select View Logs
Logs include:
  • Request payload
  • Response status code
  • Response body (if any)
  • Error messages
  • Timestamp

Testing

Send a test webhook to verify your endpoint:
  1. Edit your webhook
  2. Click Send Test
  3. Choose an event type
  4. Check your endpoint for the test payload

Common Use Cases

Troubleshooting

  • Verify you have an automation configured to trigger the webhook
  • Check that the webhook is not archived
  • Review webhook logs for errors
  • Ensure you’re using the raw request body (not parsed JSON)
  • Verify the secret matches exactly
  • Check for any proxy/middleware modifying the request
Webhooks time out after 30 seconds. Ensure your endpoint responds quickly. For slow processing, respond immediately and process asynchronously.