Skip to main content
Webhook ingestion brings supported survey, feedback, review, or meeting events into ClosedLoop AI when a native connection is not available.
The integration page can create and test a signing secret, but production use currently requires ClosedLoop AI support to confirm your workspace setup and validate the endpoint before data is sent.

​
Availability

The Integrations catalog shows the webhook sources available to your workspace. Availability can vary by platform, workspace, plan, and region. Open Integrations, select the supported webhook source, and choose Set Up. The integration page can create, display, test, and regenerate the signing secret. Before production use, ClosedLoop AI support must confirm the endpoint and verification details for your workspace.

​
Supported event categories

Provisioned webhook integrations can accept supported native payloads in these categories: The source platform sends its native payload. ClosedLoop AI processes only payloads supported by the platform integration set up for your workspace.

​
Security contract

Provisioned inbound webhooks use HMAC-SHA256 over the unmodified raw request body. ClosedLoop AI accepts the signature in these headers: The signature may be hexadecimal or Base64 encoded. A sha256= prefix is accepted.
An x-api-key header does not authenticate an inbound webhook. Use only the signing secret and configuration confirmed during provisioning.

​
Secret rotation

The webhook integration page can display, copy, and regenerate its signing secret. Coordinate rotation with the source platform because requests signed with the previous secret fail after regeneration.

​
Verification

After ClosedLoop AI support confirms a test event, use Data Log to locate the import under its platform name. Data Log shows whether a product insight is linked. If it shows No Insights, check again later or contact support.

​
See also