Overview
Define reusable message content and bind a trusted source application message code to channel and locale-specific templates.
Prerequisites
Permissions required
Steps (4)
-
1
Create the template
Define the template record and its channel/category metadata.
Tips
Validation
Success criteria
-
2
Add version, localization and variables
Maintain template versions, localized content, components, and variable definitions.
Tips
Validation
Success criteria
-
3
Create the source-app binding
Bind the source application and business message code to the required channel, locale, and template.
Tips
Validation
Success criteria
-
4
Resolve the template
Use templates.resolve or templates.suggest to verify the application-facing binding.
Tips
Validation
Success criteria
About this guide
PulseGate is the communications control plane for Velaxe workspaces. Applications send business communication through trusted contracts while PulseGate resolves recipients and templates, applies authorization and policy, routes delivery, records message state, and publishes clean events.
Operations teams get a dedicated Messenger workspace for conversations, contacts, campaigns, approvals, failed messages, and media, plus administration for provider connections, sender identities, routing, templates, consent, suppression, quiet hours, cost rules, audit, and reports.
Durable workers handle dispatch, schedules, reminders, campaigns, provider webhooks, retries, reconciliation, metrics, retention, exports, media processing, and operational recovery. Handler, RCP, Bridge v2, EventBus, and ContextResolver contracts keep workspace integrations governed and source-aware.