Error triggering webhook for call_analyzed

Support Help
1

We’re seeing repeated failures delivering the call_analyzed webhook due to a 413 error (“Body exceeded 1MB limit”).

Call ID: call_7c7aa74a13b26bdd7efc426a817

Logs show:

  • Initial call_ended webhook failed with 413

  • call_analyzed was triggered and retried multiple times

  • All retries failed with the same 413 error

Because of this, we never receive the call_analyzed payload in our webhook (n8n).

What should we do in this situation to get the call_analyzed?

2

The 413 error indicates your webhook endpoint is rejecting the payload because it exceeds your server’s size limit (1MB in your case), not a limitation on Retell’s side(1).

When the call_analyzed webhook fails due to payload size, the webhook will be retried up to 3 times(2). If all retry attempts fail with the same 413 error, Retell cannot deliver the webhook to your endpoint(2).

To resolve this and retrieve the call_analyzed data:

Immediate solution: Use the API to fetch the call data directly. The call_analyzed webhook is triggered when call analysis is complete and contains the full call data including the call_analysis object(2). You can retrieve this same data by calling the Get Call API endpoint with your call ID(3).

Long-term fixes:

  1. Increase your server’s request size limit - Your n8n or server configuration needs to accept payloads larger than 1MB. The error shows your server is rejecting the request with “request entity too large”(1).

  2. Reduce payload size - The call_analyzed webhook contains all fields from the call object except the full transcript in some cases(2). If you’re using knowledge base retrieval, large amounts of retrieved content could contribute to payload size(1). Consider whether you need all data pushed via webhook, or if you can fetch specific fields via API when needed.

  3. Use signed URLs - If your agent has opt_in_signed_url enabled, URLs in the webhook will include security signatures(4)(5)(6). This doesn’t reduce payload size but ensures secure access when fetching recordings separately.

For your specific call call_7c7aa74a13b26bdd7efc426a817, retrieve the analysis data directly via the API rather than waiting for webhook delivery.

3

Hello @Alex_Krasun

The issue here is that your server is rejecting the paylod becuase its too big.

4

Response to @Alex_Krasun:

The call_analyzed webhook failure you’re experiencing is due to your server rejecting the payload because it’s too large(1).

The error logs show:

  • Error triggering webhook for call_analyzed with Axios Error: error code: ERR_BAD_REQUEST, error message: Request failed with status code 413(1)
  • Response status: 413 with response data indicating “request entity too large”(1)

The Retell AI team confirmed that your server is rejecting the request, not their system(1). The webhook is successfully triggered from Retell AI’s side, but your server returns the 413 error indicating the payload size exceeds your server’s configured limits(1).

To resolve this:
You’ll need to increase the payload size limit on your server to accommodate larger call_analyzed webhook payloads, especially for calls longer than 5 minutes(1).