Production Webhook Not Triggering, but Test URL Works

Hello, I have an issue with a production webhook that isn’t being triggered, and I’ve already gone through the standard troubleshooting steps.

The Setup: I have a workflow that starts with a Webhook node. The HTTP method is set to POST. This webhook URL is placed in an external service (Retell AI) which sends a final report after a phone call ends.

What Works: When I am in the N8n editor and I click “Listen for Test Event,” the Test URL works perfectly. The external service sends the data, and my workflow receives it without any issues.

What Fails: When I use the Production URL in the external service and make sure the workflow is Active, the workflow is never triggered. No execution is logged in the “Executions” list. It fails silently with no error message.

Troubleshooting Already Performed:

  1. I have confirmed the workflow is Saved and Active.
  2. I have confirmed the webhook node’s HTTP Method is POST.
  3. I used a third-party tester (webhook.site) and have 100% confirmed that the external service is successfully sending the POST request with the correct data to my N8n Production URL. The request is being sent, but my N8n instance is not catching or processing it.

3. “Please share your workflow”

Here is the JSON for my “Call Outcome Processor” workflow:

4. “Information on your n8n setup”

  • n8n version: Cloud Version (latest)
  • Database (default: SQLite): Default (Cloud)
  • n8n EXECUTIONS_PROCESS setting (default: own, main): Default (Cloud)
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system: N/A (using n8n cloud)

Hi @Manohar_reddy_Yaram, welcome to the community.

Would you mind sharing what response you’re getting when you send a request to your production URL from a third party service?

Thanks,
Jake

Hi Jake,

Thanks so much for looking into this.

That’s the core of the issue – I am not getting any response at all. When the request is sent to the Production URL from the third-party service (Retell AI), it seems to fail quietly.

To be more specific:

  • No execution is created in my N8n “Executions” list for that workflow.
  • Because no execution is triggered, there is no error message or HTTP response code from N8n that I can share.

To confirm that the third-party service was sending the data correctly, I pointed it to a temporary webhook.site URL and ran a full, live test. The webhook.site URL received the POST request successfully. I also know that my N8n workflow’s Test URL receives the data perfectly when I use the “Listen for test event” feature.

The issue seems to be isolated only to the Production URL, even though I’ve confirmed the workflow is Saved, set to Active, and the webhook node is configured for the POST method.

So, the evidence shows the request is being sent correctly from the outside, but it’s not being “caught” by the production webhook to start a workflow.

Happy to provide my workflow JSON or any other details you need. Thanks again for your help.

Looking at the workflow connections, the webhook node (which should receive the Retell AI data) has no output connections. The workflow only shows connections from the “On form submission” node to Google Sheets and HTTP Request nodes.
You may needs to:
Connect the webhook node to process the Retell AI callback data. Add processing logic for the call outcome data. Update your Google Sheet with the call results.
Here’s what to do: Connect the “Webhook” node to a node that processes the Retell AI callback. You’ll likely want to update the Google Sheet row with call status/outcome.
Add Processing for Call Data
You should add nodes after the webhook to:
Extract call outcome data from Retell AI
Find the matching row in your Google Sheet (by phone number)
Update the “Call Status” and other relevant fields
Verify the Correct Production URL
Make sure Retell AI is configured with the webhook node’s production URL, not the form trigger URL. The production URL should end with the webhook path: 0fdbe89f-ee87-4ac3-b961-35265abfb48d. After connecting the webhook node properly, save and activate the workflow, and test the webhook URL to verify it receives data. Then test with the production URL
The core issue is that your webhook node exists but isn’t doing anything because it’s not connected to the rest of your workflow. Once you connect it and add the processing logic, the Retell AI callbacks should work properly.

Hey @Manohar_reddy_Yaram , are you self-hosting behind a proxy? You might need to engage the variables WEBHOOK_URL and N8N_PROXY_HOPS (see Environment Variables Overview | n8n Docs).