IntegrationIntermediatewebhooksoutbound-messagesnotifications
Design webhook and outbound message patterns from Salesforce
Real World Scenario
Case status changes must notify Slack, Jira, and custom warehouse within seconds of update.
Expected Answer
• Platform Events preferred over legacy Outbound Messages for flexibility
• Flow-triggered HTTP callout via External Services or Apex async for simple cases
• Webhook signature HMAC for receiver authentication
• Retry with exponential backoff from middleware not synchronous Flow callout in user txn
• Payload minimal: record Id, changed fields, timestamp
• Monitor failed deliveries with replay from event log
• Rate limit outbound fan-out preventing thundering herd on mass update
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Platform Events preferred over legacy Outbound Messages for flexibility. Flow-triggered HTTP callout via External Services or Apex async for simple cases. Pick based on your integration pattern and team capability. Outbound from Salesforce should be async—user transactions must not wait on Slack API availability. Balance speed of delivery with maintainability.
Architect Perspective
Outbound from Salesforce should be async—user transactions must not wait on Slack API availability.