Salesforce Outbound Messaging: Setup & Alternatives | MicroPyramid

Quoted on this wiki

Every place a page here uses this source, in the order the words come in it.

1. Outbound Messaging vs Platform Events - which should I use? “Outbound Messaging is best when you want a no-code, single-endpoint push with built-in retry and do not need transformation or fan-out.” Should I include the session ID in the outbound message?

   In Outbound stack design

2. 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?

   In Outbound stack resilience

3. Is Outbound Messaging deprecated in Salesforce? “The outbound message action still exists in Flow, approval processes, and entitlement processes, so you keep the feature but trigger it from a supported tool - ideally a record-triggered Flow.” Can I send an outbound message from a Flow?

   In Workflow automation

4. Flow (recommended). Since Winter '22, Send Outbound Message is a core action in Flow Builder, usable in record-triggered flows that run after save. You do not pass input parameters - the triggering record's Id is passed implicitly - so you select the same defined outbound message and Flow handles the rest. “Approval processes. Add New Outbound Message as an action on Submission, Approval, Rejection, or Recall steps. Entitlement processes can fire them too.” Workflow Rules (legacy). Still functional, but unsupported - do not build new ones; migrate existing ones to Flow.

   In Outbound alerts and notifications

Quotes are verbatim and belong to their publishers. Where a quote has been translated, the original wording is kept below it.