SFHooks Docs

Sign inGet started

Getting started

What SFHooks does and the path from a Salesforce org to live webhooks.

What SFHooks does

SFHooks turns Salesforce Change Data Capture (CDC) events into signed HTTPS webhooks and delivers them to your endpoints reliably — with HMAC signatures, automatic retries, and full delivery history.

You connect a Salesforce org once. SFHooks subscribes to its change events over the Salesforce Pub/Sub API and pushes each matching change to the webhook endpoints you configure. There is nothing to poll: events stream to SFHooks and out to your services as they happen.

How it works

The path every change takes
  • Connect a Salesforce org with OAuth. SFHooks starts streaming its Change Data Capture events.
  • Create a webhook: pick the Salesforce object to listen to and the destination URL to deliver to.
  • Receive signed deliveries: each change is sent as a POST with an HMAC signature your endpoint verifies.
  • Monitor: watch delivery success, latency, and per-event history on the dashboard and logs.

Quick start

  1. Connect your Salesforce org and choose where event replay should resume.
  2. Create a webhook pointing at a URL you control (start with a request-bin or a staging endpoint).
  3. Verify the signature on the first delivery so you can trust every payload that follows.
  4. Send a test event (webhook row → actions menu → Send test event) — or change a matching record in Salesforce — and watch it arrive on the Logs page.

Test without touching Salesforce

The Send test event action pushes a synthetic payload through the real pipeline — HMAC-signed, retried, and logged exactly like a live change event, with "change_type": "TEST" and a top-level "test": true so your consumer can tell it apart. Point a webhook at a temporary public URL, send a test event, verify the signature, then rotate the URL to production.

Where to go next