Overview
Use PulseGate messages.send through Handler, RCP, or Bridge with a recipient, message code, channel, variables, and dispatch mode.
Prerequisites
- Calling workspace app is installed and authorized to use PulseGate
Permissions required
Steps (4)
-
1
Authorize the calling application
Grant the trusted source app the PulseGate operation and any required delegation/resource authorization.
Tips
Validation
Success criteria
-
2
Prepare recipient and message context
Supply the recipient reference, business message code, channel, locale/variables, and desired dispatch mode.
Tips
Validation
Success criteria
-
3
Execute messages.send
Call the canonical PulseGate operation through Handler, RCP, or Bridge v2.
Tips
Validation
Success criteria
-
4
Track the message
Store the PulseGate message reference and use status/events for submitted, sent, delivered, read, failed, and retry state.
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.