When an organisation wants Salesforce to notify an external system in real time, ERP, MDM, marketing tool, logistics platform, three native patterns are available: Platform Events, Outbound Messages and custom Webhooks via Apex. Choosing the wrong pattern generates fragile architectures, data loss or costly maintenance. Here's how to choose.
Native Salesforce pub/sub mechanism. An event is published to a message bus; subscribers consume it asynchronously. Modern and recommended pattern.
An older, SOAP-based mechanism. It is not a direct call: the send is the action of a rule triggered by a record change, and Salesforce manages the queue and the retries. Simple, but ageing.
Custom HTTP call from a trigger or Flow via Apex. The most flexible but also the most complex to maintain and secure.
Platform Events are Salesforce's native event-driven integration mechanism, introduced in Spring '17. They rely on a message bus (CometD / Bayeux protocol) that decouples Salesforce from the consuming system.
EventBus.publish()) or a Flow/event/MyEvent__e channel💡 Ideal use case: notify an ESB or integration middleware (MuleSoft, Azure Service Bus, Kafka) when an opportunity is won, an account is created or an order is validated. The middleware consumes the event and orchestrates the rest.
Outbound Messages have existed since Salesforce's early days. Configured via Workflow Rules (now deprecated) or Process Builders (also deprecated), they send a SOAP message to an external endpoint when a record meets certain criteria.
Ack (acknowledgement), otherwise Salesforce retries for 24 hours⚠️ Outbound Messages in 2026: if you still have Outbound Messages in production, they work, but don't create new ones. Migrate to Platform Events or Apex Callouts depending on your needs. The end of support for workflow rules, since 31 December 2025, leaves this mechanism without further development: it works, but nobody will move it forward.
When neither Platform Events nor Outbound Messages fit, you can make a direct HTTP call from Apex to an external endpoint, commonly called a "Salesforce webhook", even though Salesforce has no native webhook mechanism in the strict sense.
@future(callout=true) or implementing Queueable@future or Queueable, introducing asynchronismRetention and delivery guarantee are not the same thing, and this is the most common confusion on the subject. The 72 hours of Platform Events are a replay window: the bus keeps the event, and it is up to the subscriber to come back for it with its ReplayId if it was unavailable. Salesforce publishes and moves on, without checking that anyone received or processed the message. If nobody comes back within the window, the event is lost for that subscriber. Recovery after an outage is the receiver's responsibility.
Outbound Messages work the other way round. Salesforce keeps the message in its own queue and retries it until the target server returns its acknowledgement. Salesforce carries the responsibility of delivering, until the queue entry expires. On one side a passive retention, on the other an active queue with an acknowledgement: if your integration has to survive an outage of the target system without extra development, these are not the same choice.
| Criterion | Platform Events | Outbound Messages | Apex Callout |
|---|---|---|---|
| Protocol | CometD / pub-sub | SOAP | HTTP REST |
| Configuration | Declarative + Apex | Declarative | Apex code |
| Recovery after a receiver outage | Replay by the subscriber within 72 h | Queue and acknowledgement on the Salesforce side | To be implemented |
| Multi-consumer | Native | No | Custom |
| Payload flexibility | Defined fields | Configured fields | Total |
| Setup complexity | Medium | Low | High |
| Recommended in 2026 | ✓ Yes | Legacy | Specific cases |
Simple. Workflow Rules are deprecated, SOAP is ageing, and Platform Events cover all Outbound Message use cases with more flexibility.
💡 Recommended hybrid pattern: publish a Platform Event from Apex or a Flow, and let middleware subscribe and perform the REST callout to the target system. You combine Platform Events' decoupling with HTTP call flexibility, without Salesforce's callout governor limit constraints.
In 2026, Platform Events is the pattern to prioritise for new Salesforce event-driven integrations. It offers decoupling, retention and multi-consumer support, without the compromises of Outbound Messages or the complexity of Apex Callouts. Reserve Apex Callouts for cases where you need a usable synchronous response or a very custom payload that Platform Events cannot express simply.
Architecture, pattern selection, implementation, I can support you. Reply within 24 hours.
Let's talk →