Overview
Create or maintain a MessageTemplateBinding used by messages.send.
Prerequisites
Permissions required
Steps (4)
-
1
Choose the source application semantics
Identify the trusted source app, message code, channel, locale and active binding scope.
Tips
Validation
Success criteria
-
2
Choose template content
Select the Email Hub template and version that represent the semantic message.
Tips
Validation
Success criteria
-
3
Persist the binding
Save the MessageTemplateBinding so the semantic code resolves through Email Hub.
Tips
Validation
Success criteria
-
4
Send a governed test
Invoke messages.send with variables and verify the binding renders and sends through the authorized sender path.
Tips
Validation
Success criteria
About this guide
MailBridge brings connected mailbox operations into a Velaxe workspace. Link standards-based IMAP/SMTP accounts, synchronize folders and messages, work with message bodies and attachments, compose new mail, maintain durable drafts, and manage reusable templates and published versions.
Campaign operations include audiences, recipient snapshots, scheduled delivery, deterministic A/B variants, open and click tracking, unsubscribe and suppression handling, bounce processing, recipient activity, campaign reports, and analytics rollups. Verification supports instant checks, uploaded batches, cached results, and capacity-aware worker processing.
Trusted workspace applications can discover accounts, send direct or semantic messages, use templates, mint governed Bridge v2 connections, resolve Email Hub context, and react to Email.received, Email.sent, Email.bounced, and context-change events through explicit capability and resource authorization.