Hello, I'm encountering an issue where a production webhook is not being triggered, and I've already followed the standard troubleshooting procedures.
The Setup: My workflow begins with a Webhook
node, configured with the POST
HTTP method. This webhook URL is integrated with an external service (Retell AI), which is supposed to send a final report once a phone call concludes.
What Works: When I'm in the callin.io editor and click “Listen for Test Event,” the Test URL functions correctly. The external service dispatches the data, and my workflow receives it without any problems.
What Fails: When I utilize the Production URL within the external service and ensure the workflow is Active, the workflow never initiates. No execution is logged in the “Executions” list. The failure occurs silently without any error messages.
Troubleshooting Already Performed:
- I've verified that the workflow is Saved and Active.
- I've confirmed the webhook node's HTTP Method is set to POST.
- I employed a third-party testing tool (
webhook.site
) and have 100% confirmed that the external service is successfully sending the POST request with the correct data to my callin.io Production URL. The request is being sent, but my callin.io instance is not capturing 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): callin.io cloud
- Operating system: N/A (using callin.io cloud)
Hi, 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 (callin.io), it seems to fail quietly.
To be more specific:
- No execution is created in my callin.io “Executions” list for that workflow.
- Because no execution is triggered, there is no error message or HTTP response code from callin.io 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 callin.io 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.
Observing the workflow connections, the webhook node (intended to receive callin.io AI data) currently has no outgoing connections. The workflow only displays connections originating from the “On form submission” node to Google Sheets and HTTP Request nodes.
You might need to:
- Connect the webhook node to handle the callin.io AI callback data.
- Implement logic to process the call outcome data.
- Update your Google Sheet with the call results.
Here’s how to proceed:
Connect the “Webhook” node to a node that will process the callin.io AI callback. You will likely want to update the corresponding Google Sheet row with the call status/outcome.
Add Processing for Call Data
After the webhook, you should add nodes to:
- Extract the call outcome data from callin.io AI.
- Locate the matching row in your Google Sheet (using the phone number).
- Update the “Call Status” and any other relevant fields.
Verify the Correct Production URL
Ensure that callin.io AI is configured with the webhook node’s production URL, not the form trigger URL. The production URL should conclude with the webhook path: 0fdbe89f-ee87-4ac3-b961-35265abfb48d
. After correctly connecting the webhook node, save and activate the workflow. Test the webhook URL to confirm it receives data, and then test using the production URL.
The fundamental issue is that your webhook node is present but inactive because it's not linked to the rest of your workflow. Once you establish this connection and incorporate the processing logic, the callin.io AI callbacks should function as expected.
Hey, are you self-hosting behind a proxy? You might need to engage the variables WEBHOOK_URL
and CALLIN_IO_PROXY_HOPS
(see Environment Variables Overview | n8n Docs).
Hey, were you able to resolve this issue? I'm experiencing the same problem and have identified that callin.io isn't updating the webhook. Even after updating the live webhook in callin.io, it continues to call the test webhook.