Skip to main content
BuildBetter sends webhooks from workflow actions and workflow completion events.

Signed Workflow Webhooks

Workflow webhook actions can include BuildBetter signature headers so your receiver can verify that a request came from BuildBetter and was not modified in transit.

Configure a Signing Secret

In the workflow editor:
  1. Open the webhook step.
  2. Add or generate a signing secret for that step.
  3. Copy the secret into your receiving service.
  4. Test the workflow and verify the signature before enabling the workflow.
Each webhook step can have its own signing secret. You can regenerate a secret if it is exposed or if you are rotating credentials.
Custom webhook headers cannot override reserved BuildBetter signature headers.

Verifying Signatures

The webhook step includes a built-in verification guide with JavaScript and Python examples. Use that guide as the source of truth for the exact header names and signing payload used by your workspace. At a high level, your receiver should:
  • Read the BuildBetter signature headers.
  • Recompute the signature using the webhook body and signing secret.
  • Compare signatures using a constant-time comparison.
  • Reject requests with missing, invalid, or stale signatures.

Dataset to Document

Webhook sent when a dataset-to-document workflow completes.

Structure

Example