Skip to main content

Trigger a workflow from an external event

Build a workflow whose first block is a webhook block, then POST your rows to its runs. Set WORKFLOW_ID to the workflow’s workflow_id.
Each object in input becomes a row. The response is a Job. Input rules are in Incoming Webhooks.

Receive Job results at your URL

Add webhook_url to a Search, Contacts or Intelligence request. Sixtyfour POSTs to that URL when the results are ready.
Store the job_id so you can match the delivery and fall back to GET /v1/jobs/{job_id} if none arrives. The payloads are in Outgoing Webhooks. To post a workflow’s output instead, end the workflow with an outgoing_webhook block. See Workflow Webhooks.

Handle deliveries

A receiver verifies the signature, acknowledges fast and processes later:
verify is the function in Signing Secrets. Verify against the raw body before parsing JSON. Use a persistent store for seen_deliveries in production. delivery_key dedupes on the Job or run, not event_id: monitor notifications carry no event_id, and Sixtyfour can deliver the same result again with a new event_id.

Test locally

Sixtyfour only delivers to public hosts, and Job webhooks and test deliveries require HTTPS. Expose your local server through a tunnel such as ngrok or Cloudflare Tunnel and use the tunnel’s HTTPS URL as webhook_url.

Test deliveries

Send a sample delivery to your receiver to check its signature verification and parsing before a real Job runs. A test delivery runs no Job and uses no credits. GET /v1/webhooks/test-events lists the samples in items. Each one has a type, a description and an example payload. GET /v1/webhooks/test-events/{type} returns one sample. POST /v1/webhooks/test-events sends one sample to your URL with the same signing and retries as a real delivery:
delivered is true only when your receiver returned 2xx. status_code is the last attempt’s HTTP status, or null when no response arrived. The call waits for every retry and can take up to 100 seconds. Each call sends a new event, so don’t retry it automatically. Test deliveries carry these headers on top of the delivery headers: These type values match deliveries Sixtyfour sends for /v1 requests: The catalog has no sample for the Search Job payload. Its other samples match webhooks from the original routes. See Legacy Using Webhooks. Test deliveries are rate limited. For error responses, see Handling Errors.

Production checklist

  • Create a signing secret under Webhooks in Settings and reject unsigned deliveries.
  • Return 2xx within 10 seconds, including for events you ignore.
  • Dedupe on the Job or run, as delivery_key does above.
  • Poll GET /v1/jobs/{job_id} when a delivery is late. A Contacts or Intelligence Job that fails sends none.