Loading…
Velaxe
PulseGate — Messaging Operations, Conversations, Campaigns, Routing & Compliance | Velaxe

PulseGate

Use a workspace app as a messaging provider

Bind a trusted same-workspace application as a PulseGate provider through Handler or RCP.

10 min Intermediate Communications Administrator, Product Engineer Updated Aug 23, 2026
View App All Guides

Overview

Bind a trusted same-workspace application as a PulseGate provider through Handler or RCP.

Prerequisites

None.

Permissions required

connectors.write routing.write

Steps (4)

Estimated: 10 min
  1. 1

    Discover the provider app

    Administrator 2 min Back to top

    Select an installed app that advertises the required messaging handler capability.

    Tips

    —

    Validation

    —

    Success criteria

    —

  2. 2

    Probe its capabilities

    Administrator 2 min Back to top

    Verify system.health, system.capabilities, messages.send, and optional messages.status support.

    Tips

    —

    Validation

    —

    Success criteria

    —

  3. 3

    Create the provider binding

    Administrator 3 min Back to top

    Choose PLATFORM_HANDLER or PLATFORM_RCP and save the workspace-app provider configuration.

    Tips

    —

    Validation

    —

    Success criteria

    —

  4. 4

    Route a test message

    Administrator 3 min Back to top

    Select the provider in routing and verify PulseGate message state through the same central dispatch model.

    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.