Troubleshoot webhook delivery

The test works but real collection does not

The dashboard sends a signed webhook.test envelope. The current collection service sends X-Webhook-Secret and a different body, without the HMAC headers. A receiver that only accepts the dashboard format will reject collection requests.

Inspect the actual request headers and body in your receiver’s private request history. Configure the appropriate authentication and field mapping for each supported format. Collection fields may be at the top level or inside a testimonial object. Do not publish private customer fields while debugging.

No request reaches your receiver

1. Check that the Webhook URL was saved in the correct space and that the owner’s plan includes webhooks.
2. Use a public HTTPS endpoint that accepts POST. Check firewall rules, sign-in requirements, and the URL spelling.
3. Choose Send test event and inspect the receiver history. A delivered request with a failed later workflow step is a different problem from no request arriving.
4. Return a 2xx response promptly. The signed dashboard sender times out after 10 seconds and makes up to three total attempts. Collection requests do not currently use that same retry loop.

Authentication fails

For signed events, verify the raw request bytes before parsing JSON, use HMAC SHA-256, check the current secret, and validate the timestamp. A rotated secret or incorrect server clock can break verification.

For collection requests, validate X-Webhook-Secret against the current configured secret. Do not try to find Socialjuice-Signature on this format, and never disable authentication to get an automation working.

Repeated or missing work

Deduplicate signed requests with Socialjuice-Delivery or the envelope id. Collection requests need a stable testimonial identifier, such as uuid, where available. Confirm that the automation is not running once for the connection test and again for a real submission.

Neither delivery path is an unlimited queue or a guarantee of eventual delivery. After correcting the receiver, send another dashboard test and check the appropriate format separately. Imported reviews and other creation paths may not emit the same event; inspect the specific route rather than assuming universal coverage.

Ask for help with redacted evidence

Send support the approximate time, affected space, delivery format, response status, and a redacted error message. Include a delivery ID for signed events if available. Never include the Signing secret, X-Webhook-Secret value, access tokens, or private customer contact details.