Overview
Publish Email Hub lifecycle events so trusted workspace automation and applications can react to received mail, sent mail, bounced mail, and context changes.
Capabilities
-
Email.received publication after inbound mail ingestion
-
Email.sent publication after governed outbound delivery
-
Email.bounced publication when bounce processing resolves delivery failure context
-
velaxe.context.changed publication for contextual cache invalidation
-
Correlation and causation metadata inherited from trusted execution/event context
Setup Steps (3)
-
1
Step 1
Authorize or configure the consuming workspace workflow for the required event topics.
-
2
Step 2
Run the normal Email Hub operation such as IMAP ingest, send, or bounce processing.
-
3
Step 3
Consume the emitted platform event and correlate it with the Email Hub entity or source operation.
Limitations
-
Published event source/workspace identity comes from trusted Email Hub execution context.
-
Consumers use platform event authorization and their own operation/resource policy for downstream actions.
FAQs
Which events does MailBridge publish?
Email.received, Email.sent, Email.bounced, and velaxe.context.changed.
What is velaxe.context.changed for?
It tells ContextResolver consumers that cached Email Hub entity context may need to be refreshed.
Pricing
Starter
USD 219.07 / annual
Pro
USD 584.32 / annual
Enterprise
USD 1,095.66 / annual