https://retellai.com/?utm_source=discord&utm_medium=seo logo
I am having an issue where there agent level webho...
# ❓・ai-evy-support
u
@AI Evy I am having an issue where there agent level webhook doesn't get triggered in my n8n workflow, I used post man to trigger it and it works from there but it doesn't from retell, I added the webhook to both account and agent level and it still doesn't work and none of the chats are showing up in the chat history either I had this issue earlier this month, but when I added the webhook to the account level, it worked but now that isn't even working
a
Thanks for tagging me @$iddh(Mr. get stopped at LOD). I'll look through relevant sources and get back to you shortly.
### Answer --- A few things to check based on documented behavior: **Webhook timeout**: The webhook has a timeout of 10 seconds. If your n8n endpoint doesn't return a success status (2xx) within 10 seconds, the webhook will retry up to 3 times. [(1) ]() **Agent-level vs account-level behavior**: If you set an agent-level webhook, it will ignore the account-level webhook for that agent. **Known issues**: Other users have reported similar problems with agent-level webhooks not receiving data, particularly when using Make.com (similar to n8n) . In one case, the issue appeared to be intermittent and resolved itself. [(2) ]() **Conversation Flow compatibility issue**: There's a reported bug where the inbound webhook URL on phone numbers can conflict with conversation flow agent webhooks—saving the conversation agent can sometimes remove the webhook URL from the phone number configuration. [(3) ]() **Troubleshooting steps**: 1. Verify your n8n webhook is returning a 2xx status code within 10 seconds [(1) ]() 2. Check if the webhook URL is still saved in your configuration (it may have been removed unexpectedly) [(3) ]() 3. Try testing with a web call from the dashboard to verify the webhook triggers [(4) ]() Since chats aren't showing in history either, this may indicate a broader configuration or service issue rather than just the webhook. I'd recommend reaching out to support@retellai.com for assistance with your specific agent configuration.
​ To learn more, see the sources I considered: [[1] Webhook Overview](https://docs.retellai.com/features/webhook-overview) [[2] Agent Level Webhook not receiving data](https://discord.com/channels/1186424376300679209/1412776467112263750) [[3] inbound webhook URL failing to save (or stay saved) and wont work together with conversation agaent](https://discord.com/channels/1186424376300679209/1398428473781125314) [[4] Discord message from @tomjennings25 on 2025-12-14](https://discord.com/channels/1186424376300679209/1294891368505937952/1449715238411698266) ​
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
u
the timeout is at 10 seconds, my n8n webhook isn;t being triggered whatsoever so I cant tell
a
Thanks for the follow-up, @$iddh(Mr. get stopped at LOD). I'll get back to you soon.
u
@AI Evy
a
​ To learn more, see the sources I considered: [[1] Discord message from @tomjennings25 on 2025-12-14](https://discord.com/channels/1186424376300679209/1294891368505937952/1449715238411698266) [[2] Agent Level Webhook not receiving data](https://discord.com/channels/1186424376300679209/1412776467112263750) [[3] Update Chat Agent](https://docs.retellai.com/api-references/update-chat-agent) [[4] Create Chat Agent](https://docs.retellai.com/api-references/create-chat-agent) ​
### Answer --- Since your n8n webhook isn't being triggered at all (and Postman works fine) , and chats aren't showing in history either, this points to a potential configuration or service-side issue rather than your n8n setup. What to verify: 1. Confirm the webhook URL is actually saved — There's a reported bug where saving a conversation agent can sometimes remove the webhook URL from the phone number configuration unexpectedly. [(1) ]() [(2) ]() 2. Check if this is a Chat Agent — Based on your mention of "chats" not showing in history, if you're using a Chat Agent, ensure the webhook is configured via the
webhook_url
parameter: [(3) ]() [(4) ]()
Copy code
javascript
webhook_url: "<https://your-n8n-webhook-url%22>
[(3) ]() , [(4) ]() 3. Other users experienced similar intermittent issues — Agent-level webhooks have been reported as not receiving data, and in some cases the issue resolved itself. One user noted this happened between specific hours and then started working again. [(2) ]() Since the issue persists and chats aren't appearing in history at all, this likely requires direct support investigation. Reach out to support@retellai.com with your agent ID and workspace details so they can check your specific configuration.
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
u
@AI Evy draft me a email to send with placeholders for my ids and what not
a
Thanks for the follow-up, @$iddh(Mr. get stopped at LOD). I'll get back to you soon.
### Answer --- Here's a draft email you can send to Retell support: --- To: support@retellai.com Subject: Webhook Not Triggering & Chats Not Appearing in History Hi Retell Support, I'm experiencing an issue where my agent-level and account-level webhooks are not being triggered. Issue Details: - Agent ID:
[YOUR_AGENT_ID]
- Org/Workspace ID:
[YOUR_ORG_ID]
*(found in account settings, bottom left of dashboard) * - Webhook URL:
[YOUR_N8N_WEBHOOK_URL]
What I've tried: - Configured webhook at both agent-level and account-level - Tested the webhook URL via Postman — it works correctly - Verified the webhook timeout is within 10 seconds Observed behavior: - Webhooks are not being triggered at all from Retell - Chats are not appearing in the chat history either - This issue started around
[DATE]
Additional context: - I previously had this issue earlier this month; adding the webhook at account-level resolved it temporarily, but now that workaround no longer works. Could you please investigate my configuration to determine why webhooks aren't firing and why chat history isn't populating? Thank you,
[YOUR_NAME]
[YOUR_EMAIL]
--- Replace the bracketed placeholders with your actual details before sending.
message has been deleted
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.