Email Delivery Outcomes — Integration

Overview

Ingest trusted Email.sent EventBus deliveries and correlate them with EngagementHub communication requests and channel records.

Capabilities

• Consumes the Email.sent topic declared in the manifest

• Validates canonical EventEnvelope identity against managed EventBus delivery state

• Records incoming events in the Event Inbox

• Creates delivery outcome records for email channel activity

• Correlates event trace data with communication state

1. 1

   Step 1

   Dispatch a communication through the configured notification-routing path.

   Back to top
2. 2

   Step 2

   Allow the email delivery application to publish Email.sent.

   Back to top
3. 3

   Step 3

   Receive the managed EventBus delivery in EngagementHub.

   Back to top
4. 4

   Step 4

   Validate and record the canonical EventEnvelope.

   Back to top
5. 5

   Step 5

   Correlate the event to the communication request/channel record.

   Back to top
6. 6

   Step 6

   Review the recorded delivery outcome and updated channel state.

   Back to top

Limitations

• The active email ingress contract is the manifest-declared Email.sent topic.

• Event ingress requires trusted source, workspace and envelope identity.

• Duplicate processed inbox deliveries are recognized by event identity.

FAQs

Pricing