Overview
Expose PulseGate contacts, conversations, messages, templates, campaigns, providers, deliveries, failures, timelines, actions, presentation, and permissions as contextual entities.
Capabilities
-
Entity resolution for contacts, addresses, conversations, messages, templates, bindings, campaigns, channels, provider connections, provider webhook events, deliveries, and failed messages
-
Relationship and timeline resolution
-
Permission-aware available actions
-
Context action execution through the canonical PulseGate runtime
-
Presentation schema, permissions, and velaxe.context.changed subscription guidance
Setup Steps (5)
-
1
Step 1
Configure the consuming application to use PulseGate as a ContextResolver provider.
-
2
-
3
Step 3
Load relationships, timeline, presentation schema, permissions, and available actions.
-
4
-
5
Limitations
FAQs
Can ContextResolver mutate PulseGate records?
Permitted actions use context.executeAction and return through the same PulseGate operation/resource authorization used by other capability transports.
Which entities are contextualized?
The resolver covers core messaging entities including contacts, conversations, messages, templates, campaigns, provider and delivery state, and failed-message resources.
Pricing
Starter
USD 219.07 / annual
Team
USD 730.42 / annual
Enterprise
USD 1,826.15 / annual