Definition
A workflow action in Salesforce that sends a SOAP message to an external web service endpoint when triggered, containing specified field values from the record, enabling real-time integration with external systems.
Real-World Example
Consider a scenario where a business intelligence manager at Apex Analytics is working with Outbound Message to transform raw Salesforce data into actionable business intelligence. After setting up Outbound Message, leadership has real-time visibility into pipeline health, team performance, and customer trends, enabling faster and more confident decision-making.
Why Outbound Message Matters
An Outbound Message is a workflow action in Salesforce that sends a SOAP message to an external web service endpoint when triggered, containing specified field values from the record. This enables real-time integration with external systems: when a record meets the workflow criteria, the platform automatically sends a SOAP message to the external endpoint with the configured fields. The external system receives the message and processes it however needed.
Outbound Messages are one of the older Salesforce integration patterns. They're configured declaratively through workflow rules, making them accessible to admins, but they have limitations: they're SOAP-based (modern integrations typically prefer REST), they're tied to legacy Workflow Rules (which are being deprecated in favor of Flow), and they don't have great error handling or retry semantics. Modern Salesforce integration uses Flow with HTTP Callout actions, Platform Events, or Change Data Capture, all of which provide better functionality than legacy Outbound Messages.
How Organizations Use Outbound Message
- •Skyline Consulting — Helps clients migrate legacy Outbound Messages to modern Flow-based HTTP Callouts as part of Workflow Rules deprecation.
- •TerraForm Tech — Uses Platform Events instead of Outbound Messages for new integration scenarios that need real-time event delivery.
- •NovaScale — Maintains some legacy Outbound Messages for older integrations while planning their replacement with modern alternatives.