SFHooks Docs

Sign inGet started

Create a webhook

Target URL, object selection, field filters, custom headers, and payload filtering.

Create a webhook

On the Webhooks page, add a webhook to start delivering events to one of your endpoints. A webhook ties a Salesforce object on a connected org to a destination URL.

  1. Give the webhook a recognizable name.
  2. Pick the connection (Salesforce org) it listens to.
  3. Choose the Salesforce object to subscribe to — only objects with Change Data Capture enabled are eligible.
  4. Enter the destination URL (http or https).
  5. Optionally add field filters, custom headers, or payload filters (below), then save.

A unique signing secret (prefixed whsec_) is generated for every webhook so you can verify deliveries. It's shown only once at creation — copy it then, and see Webhook signatures to verify and rotate it.

Field filters

What an event passes through before delivery

Only events that clear every filter are delivered.

By default a webhook fires on every change to the selected object. Add field filters to deliver only when specific fields change — for example, fire only when Status or Amount is part of the change. This keeps low-signal updates off your endpoint.

Custom headers Pro

On the Pro plan and above you can attach static custom headers to every delivery — useful for routing tokens or tenant identifiers your gateway expects.

Reserved headers can't be overridden

SFHooks sets Content-Type and its own X-SFHooks-* headers (timestamp and signature). Those are reserved and can't be replaced by a custom header.

Payload filtering Scale

On the Scale plan you can filter by field values, not just which fields changed. Build conditions with comparison operators — eq, neq, gt, gte, lt, lte — and combine them with AND / OR logic. Only events whose payload matches are delivered (for example, deliver only when Amount gt 1000).

Pausing a webhook

Each webhook has an Active toggle. Turn it off to stop deliveries without deleting the configuration or its signing secret, and back on to resume. SFHooks may also pause an endpoint automatically after a sustained outage — see Delivery, retries & DLQ.

  • Editing the URL or filters takes effect on the next delivery.
  • Deleting a webhook stops deliveries and removes its secret.