Back to Insights

Salesforce real-time integrations: Platform Events vs Outbound Messages vs Webhooks

Pierre Frin May 2026 10 min read
Salesforce Sales Cloud Platform Events pub/sub · asynchrone Outbound Messages SOAP · workflow Webhooks (Apex) HTTP · custom Subscriber (ESB · MQ · App) Endpoint SOAP (Système tiers) Endpoint HTTP (REST · custom) Garanties de livraison PE : 72h rétention, at-least-once OM : retry natif Salesforce WH : aucune garantie native SALESFORCE · INTÉGRATION TEMPS RÉEL

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.

The 3 patterns in brief

Platform Events

Native Salesforce pub/sub mechanism. An event is published to a message bus; subscribers consume it asynchronously. Modern and recommended pattern.

Outbound Messages

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.

Webhooks (Apex Callout)

Custom HTTP call from a trigger or Flow via Apex. The most flexible but also the most complex to maintain and secure.

Platform Events : the modern pattern

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.

How it works

Strengths

Limitations

💡 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 : the legacy pattern

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.

How it works

Strengths

Limitations

⚠️ 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.

Webhooks via Apex Callout : the custom pattern

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.

How it works

Strengths

Limitations

Retention 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.

Summary comparison

CriterionPlatform EventsOutbound MessagesApex Callout
ProtocolCometD / pub-subSOAPHTTP REST
ConfigurationDeclarative + ApexDeclarativeApex code
Recovery after a receiver outageReplay by the subscriber within 72 hQueue and acknowledgement on the Salesforce sideTo be implemented
Multi-consumerNativeNoCustom
Payload flexibilityDefined fieldsConfigured fieldsTotal
Setup complexityMediumLowHigh
Recommended in 2026✓ YesLegacySpecific cases

How to choose

Choose Platform Events if…

Choose Apex Callout if…

Don't choose Outbound Messages for new development

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.

Conclusion

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.

Pierre Frin
Founder Grokium · Salesforce Sales Cloud Consultant · Integration Architecture Expert

A Salesforce integration project to design?

Architecture, pattern selection, implementation, I can support you. Reply within 24 hours.

Let's talk →
Going further
My CRM services All technical articles Contact me