Overview
Expose the canonical EngagementHub capability surface through Velaxe Handler while keeping business execution in the shared EngagementHub runtime.
Capabilities
-
Supports system health and capability discovery
-
Exposes Handler-enabled content, feed, event, promotion, campaign, audience, analytics and ContextResolver operations
-
Uses trusted Handler caller context
-
Routes execution through the canonical capability registry and runtime
-
Applies application grants and resource authorization before business execution
Setup Steps (6)
-
1
-
2
-
3
-
4
-
5
-
6
Limitations
-
Handler discovery and business execution are separate authorization stages.
-
Handler uses the same operation identifiers as the canonical runtime.
-
Caller-owned event registrations and promotion claims receive resource authorization.
FAQs
What does the Platform Handler integration use?
Expose the canonical EngagementHub capability surface through Velaxe Handler while keeping business execution in the shared EngagementHub runtime.
How is access controlled?
EngagementHub uses workspace-scoped platform identity, configured application/provider grants, operation scopes, and resource authorization appropriate to the integration transport.
Where can administrators inspect activity?
EngagementHub exposes integration, connection, EventBus, webhook, communication and operational records through its Studio and generated operations views.
Pricing
Starter
USD 219.07 / annual
Growth
USD 730.42 / annual
Business
USD 1,460.91 / annual
Enterprise
USD 2,921.89 / annual