Salesforce webhooks
Debug Salesforce Outbound Messagesand the callouts behind your Flows
Capture what Salesforce sends to your endpoint, read the XML or JSON exactly as it arrived, and find the field that broke a downstream sync.
How Salesforce webhooks work
| What it sends | Outbound Messages: a SOAP message (notifications() call) to your endpoint URL when a workflow rule or approval process fires. Your listener answers with Ack set to true. |
|---|---|
| Where to configure it | Setup > Quick Find "Outbound Messages" > New Outbound Message. Click for WSDL gives the WSDL for your listener. |
| Allowed ports | 80 (HTTP only), 443 (HTTPS only) or a port from 1024 up (HTTP or HTTPS). |
| Authentication | Optional two-way TLS: download the Salesforce client certificate and have your server require it. |
| Delivery status and retry | Outbound Messages > View Message Delivery Status shows attempted deliveries; Retry sets the next attempt to now. |
Bring transparency to Salesforce automation
Salesforce integrations power CPQ workflows, customer onboarding and finance handoffs. Hooklistener shows every request that reaches your endpoint so you can stop wondering why a downstream task failed.
Inspect headers and bodies, forward requests to localhost while you build, and check that your service answers quickly enough for Salesforce to count the delivery as successful.
The Salesforce integration issues worth catching early
Opaque Outbound Messages
Salesforce logs do not keep the exact XML it sent. When a listener rejects a message, you need the request itself to see why.
Platform Event drift
Adding fields to a Platform Event or Flow callout can break consumers that expect the old shape, and nobody notices until a job fails.
Slow incident response
When a downstream API times out, Salesforce retries without much context. You need to see each attempt and how long your endpoint took.
How Hooklistener helps with Salesforce webhooks
Read the Outbound Message XML
Point a Salesforce Outbound Message at a Hooklistener endpoint and read the exact XML and headers it sent, so a rejected message shows the field or format that caused it.
Anomaly detection for payload drift
Hourly anomaly detection compares each endpoint with its past week of traffic and flags missing fields or changed field types when a new Salesforce Platform Event field or Flow change alters the payload.
Custom responses and inactivity monitors
Return the status, headers, body and latency you choose to see how Salesforce reacts to a slow or failing listener, and get an email, Slack or signed-webhook alert when Salesforce stops sending.
Try it: point Salesforce at a free webhook URL or run a test with the webhook tester.
Common Salesforce webhook scenarios
Lead lifecycle
Sync lead assignments from Salesforce to marketing tools and find out when an enrichment provider fails.
Revenue operations
Keep billing platforms aligned with CPQ updates and check the payload again whenever pricing logic changes.
Customer success
Send case updates to collaboration tools and confirm escalations trigger the right playbooks.
Replay a failed webhook without re-triggering the provider
Once a delivery is captured, you can resend its exact headers and body to localhost, staging or production from the dashboard or through your coding agent over MCP, so the provider never has to fire a new event. Replay is on Pro and above. Read the replay guide.
Comparing webhook debugging tools?
See how Hooklistener stacks up against webhook.site, RequestBin, Beeceptor, Hookdeck and ngrok in the best tools to capture and inspect webhook payloads, or read the head-to-head pages for Hooklistener vs ngrok and Hooklistener vs Beeceptor.
Frequently asked questions
How long does Hooklistener keep Salesforce payloads?
History depends on your plan: 1 day on Free, 14 days on Pro, 30 days on Production and 90 days on Scale.
How do I connect Salesforce to Hooklistener?
Create a Hooklistener endpoint, then point your Outbound Message or Flow HTTP callout at its URL. For Platform Events, forward them through your middleware (MuleSoft, Workato and similar) to the same endpoint.
Can I get alerted when Salesforce stops sending?
Yes. Attach an inactivity monitor to the endpoint with a window between 1 minute and 24 hours, and get an email, Slack or signed-webhook alert when no request arrives in that time.
Can I share a payload with a partner?
Yes. Send a shareable debugger link for the captured request instead of pasting XML into an email.
See exactly what Salesforce sent
Capture Outbound Messages and Flow callouts, spot payload changes, and keep ops and engineering looking at the same request.