Overview
Let trusted workspace applications request business messages using message codes, variables, locale and channel semantics resolved through Email Hub bindings.
Problem
Application code becomes tightly coupled when every caller must know a specific email template/version identifier.
Solution
Use messages.send with MessageTemplateBindings so MailBridge resolves the active template/version and renders caller-supplied variables through the governed send runtime.
How it works
A trusted caller invokes messages.send. Email Hub validates caller/resource authority, resolves the semantic binding, selects the template/version, renders the payload, chooses the authorized sender and performs delivery with idempotency support.
Who is this for
Product Engineer
Platform Engineer
Workspace Administrator
Expected outcomes
- Applications call stable message codes instead of template IDs
- Email content and template lifecycle remain owned by MailBridge
Key metrics
Security impact
- Trusted application provenance, semantic message code, template binding, variables, sender and recipient data · PII: yes where email addresses, message content, attachments, recipients, or integration payloads contain personal data
Compliance
- Operation, delegation and resource authorization
- Trusted Handler/RCP/Bridge provenance
Availability & next steps
Starter
Pro
Enterprise