Inspect webhook deliveries

Delivery history connects a product event with the request sent to the receiver and its response outcome.

Before you start

• Use the current released client or web app and sign in to the intended account.
• Select the correct workspace and use non-confidential test data.
• Record the current setting or result before changing it.
• Keep passwords, API keys, recovery keys and private links out of screenshots and support messages.

Steps: inspect webhook deliveries

1. Open the webhook and its delivery history.
2. Select the failed or delayed event.
3. Compare event type, time and endpoint.
4. Read status and redacted response details.
5. Fix the receiver before using any supported replay.
6. Confirm the handler processes a duplicate idempotently.

Expected result

The inspect webhook deliveries workflow completes for the test item and its result remains visible after a refresh or reconnect.

Limits and important details

• Available controls depend on the current client version, plan, role and workspace policy.
• A successful connection does not grant permissions beyond its credential and workspace boundary.
• Verify important results with a harmless test before relying on the workflow.

Troubleshooting

The expected control is missing. Confirm the current client, active workspace and role, then check the relevant settings page.

The operation is rejected. Read the exact error and compare credentials, permissions, quota and workspace policy.

The result is still unclear. Repeat with one small test item and contact private support with the time, client version and nonsecret error.

Related guides

• Choose webhook events
• Troubleshoot webhooks