Article
Salesforce Outbound Messaging: Setup & Alternatives | MicroPyramid
micropyramid.com
Quoted on this wiki
Every place a page here uses this source, in the order the words come in it.
Messages can arrive out of order and the same notification can be delivered more than once, so your listener must be idempotent (key off the Notification Id). “You can watch all of this under Setup -> Outbound Messages (the delivery monitor), which shows next items for delivery, oldest failures, attempt counts, and failure reasons, and lets you retry or delete stuck messages.” What does the listener have to send back?
Outbound Messaging in Salesforce sends a SOAP message to an external endpoint URL whenever a record meets your criteria - a declarative, retry-backed way to push data out of Salesforce without writing Apex. You define an outbound message (the object, the endpoint, the fields to send, and whether to include the session ID), generate a WSDL to build a listening service, then trigger the message from automation. “So new outbound messages should fire from Flow or an approval process, and for genuinely event-driven integrations you should usually reach for Platform Events, Change Data Capture (CDC), or Apex callouts instead.” Key takeaways
Key takeaways “What it is: a point-and-click action that POSTs a SOAP notifications envelope to an external HTTPS endpoint when a record changes.” Guaranteed-ish delivery: your listener must return an Ack of true; if it does not, Salesforce retries with backoff for up to 24 hours.