Why we built SFHooks
Getting data out of Salesforce in real time is harder than it should be. Teams end up polling the API on a timer, burning request limits and still arriving late - or they hand-roll a Change Data Capture consumer, then quietly inherit the hard parts: retries, back-pressure, signature verification, replay, and the observability to know when a delivery silently failed.
SFHooks exists to make that a solved problem. You connect a Salesforce org, point a webhook at your endpoint, and every matching change is captured, signed, and delivered - with the reliability and visibility that production integrations need.
What we care about
Reliability
At-least-once delivery with jittered retries and a dead-letter queue, so a downstream blip never means a lost event.
Trust
Every payload is HMAC-signed with support for rotating secrets, so you can verify authenticity in any language - no SDK required.
Visibility
Live success rate, p95 latency, and per-event delivery history - payloads, attempts, and response codes - for fast debugging.
How it works
SFHooks subscribes to your Salesforce org's Change Data Capture stream over Pub/Sub, filters events to the objects and fields you choose, signs each payload, and delivers it to your endpoints - retrying on failure and recording the full delivery history. You watch the whole pipeline from one dashboard. Read the details in our documentation.
Get in touch
Questions, feedback, or a high-volume use case? We'd love to hear from you.
- General & support: [email protected]
- Sales & enterprise: [email protected]