Overview
Deliver selected EngagementHub lifecycle events to administrator-configured external HTTPS endpoints with signing, retry state and delivery logs.
Capabilities
-
Stores webhook endpoints and subscribed event names
-
Creates webhook delivery and attempt records
-
Signs outbound payloads using configured secret references
-
Requires HTTPS destinations and applies outbound network safety checks
-
Retries queued deliveries and records response/error state
Setup Steps (6)
-
1
-
2
-
3
-
4
-
5
-
6
Limitations
-
Webhook endpoints are administrator-configured and event-scoped.
-
Outbound delivery uses the application webhook queue and retry runtime.
-
Endpoint secrets use Core AppSecretService references for workspace-scoped secret handling.
FAQs
What does the Signed Webhooks integration use?
Deliver selected EngagementHub lifecycle events to administrator-configured external HTTPS endpoints with signing, retry state and delivery logs.
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