Overview
Resolve PulseGate entities and subscribe to message or context changes without duplicating messaging state in the consuming application.
Prerequisites
- Consuming workspace app is installed and authorized for the required PulseGate context/event operations
Permissions required
Steps (4)
-
1
Choose the PulseGate entity or event
Identify the message, conversation, contact, campaign, template, delivery, failure, or event the consuming application needs.
Tips
Validation
Success criteria
-
2
Resolve context
Use ContextResolver operations for entity, relationships, timeline, permissions, presentation, and available actions.
Tips
Validation
Success criteria
-
3
Subscribe to changes
Consume the required PulseGate EventBus topic or velaxe.context.changed notification for refresh behavior.
Tips
Validation
Success criteria
-
4
Execute governed actions
Use context.executeAction or canonical messaging operations when the user/caller has permission to mutate PulseGate 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.