Troubleshooting

The Webhook integration can fail because of authentication issues, permission restrictions, payload size limits, query or data availability mismatches, or format incompatibilities between the appliance and the receiving endpoint. See the following topics for symptom-specific causes and remedies.

HTTP 401

Diagnose and resolve HTTP 401 errors returned by the Webhook integration.

The Webhook integration returns an hypertext transfer protocol (HTTP) 401 error when sending data to the endpoint.

The configured authentication credentials are invalid, expired, or not accepted by the endpoint.

Procedure

  1. Verify that the selected authentication method matches the endpoint requirements and re-enter valid credentials.
  2. Send a test request to the endpoint with the same credentials to confirm they authenticate successfully.

HTTP 403

Diagnose and resolve HTTP 403 errors returned by the Webhook integration.

The Webhook integration returns an HTTP 403 error when sending data to the endpoint.

The credentials are valid but do not have permission to create or update resources on the endpoint.

Procedure

  1. Confirm that the service account has write permissions for the target endpoint path.
  2. Update endpoint-side access control rules to allow requests from the appliance.

HTTP 413

Diagnose and resolve HTTP 413 errors returned by the Webhook integration.

The Webhook integration returns an HTTP 413 error when sending data to the endpoint.

The request payload exceeds the maximum size accepted by the receiving endpoint.

Procedure

  1. Reduce the page_count value in the endpoint configuration to decrease the payload size.
  2. If needed, increase the endpoint's allowed request size limit.

No data received

Diagnose and resolve cases where the Webhook integration sends no data.

The receiving endpoint does not receive any data from the Webhook integration.

The selected entity has no matching records, or the configured query filter excludes all records.

Procedure

  1. Confirm that the selected entity type has records available in the user interface (UI).
  2. Temporarily clear the query filter and rerun the integration to verify data flow.

Data is not in the expected format

Diagnose and resolve format mismatches between the Webhook integration and the receiving endpoint.

The receiving endpoint cannot parse the data sent by the Webhook integration.

The configured output format does not match what the receiving endpoint expects.

Procedure

  1. Check the Format setting in the endpoint configuration and confirm the receiving endpoint supports that format.
  2. Set the format expected by the receiver, then send a new test batch and confirm successful parsing.