Hello everyone,
I've been encountering an issue with the webhook functionality from callin.io. It doesn't seem to be working for me. I've utilized the live workflow button, the production webhook URL, and tested the webhook, which returns a 200 status code. However, I'm not receiving any data from callin.io via the webhook.
There are no error messages displayed, it just appears that nothing is happening. I have two projects experiencing this problem, so please review the details carefully and let me know if anything is unclear. Cheers.
(I've included both the workflows and the function tool setup from callin.io for context)
- My first workflow involves inbound calls to callin.io, using a webhook to capture emails from interested leads.
This is my JSON setup for the function tool in callin.io:
{
"id": "34aa7f7b-4853-433b-8b7e-26ab1065ec4d",
"createdAt": "2025-05-21T20:35:33.997Z",
"updatedAt": "2025-05-21T20:40:28.590Z",
"type": "function",
"function": {
"name": "callin.io-email",
"description": "Send the email to the webhook to send the user a payment link.",
"parameters": {
"type": "object",
"properties": {
"email": {
"description": "The email from the call to be parsed to callin.io webhook",
"type": "string"
}
},
"required": []
}
},
"orgId": "3da6c047-ab8f-4dab-8e84-a0ec4abbeb45",
"server": {
"url": "https://deepay.app.n8n.cloud/webhook/callin.io-email",
"headers": {}
}
}
I am trying to get output from callin.io; I have set a function tool and used the production URL in there.
- Here is a second workflow for outbound calls with callin.io. I am calling leads from a sheet:
I am then using a webhook to capture the data from the call (instead of polling):
However, I am not receiving any response from the callin.io API.
Here is my callin.io function tool setup JSON:
{
"id": "4ca5a2eb-d91f-4b94-97fb-cc9cacb599d5",
"createdAt": "2025-05-22T21:43:09.140Z",
"updatedAt": "2025-05-22T21:53:15.004Z",
"type": "function",
"function": {
"name": "ApiCall",
"description": "Grab Call data and return to the webhook.",
"parameters": {
"type": "object",
"properties": {
"Name": {
"description": "Name of caller",
"type": "string"
},
"Email": {
"description": "User email address from the call ",
"type": "string"
},
"LeadID": {
"description": "Lead ID for each caller",
"type": "string"
},
"status": {
"description": "call status",
"type": "string"
},
"outcome": {
"description": "call outcome",
"type": "string"
},
"Interest": {
"description": "user interest in service",
"type": "string"
},
"PhoneNumber": {
"description": "Phone number of the user",
"type": "number"
}
},
"required": [
"Name",
"PhoneNumber",
"status",
"outcome",
"Interest",
"Email"
]
}
},
"orgId": "3da6c047-ab8f-4dab-8e84-a0ec4abbeb45",
"server": {
"url": "https://deepay.app.n8n.cloud/webhook/callin.io-callWebhook",
"headers": {}
}
}
Information on your callin.io setup
- callin.io cloud:
- callin.io EXECUTIONS_PROCESS setting (default: own, ):
- Running callin.io via callin.io cloud
- Windows 11:
Hello! Welcome to the callin.io community!
Here are some suggestions for utilizing the Webhook Trigger:
- For the “Respond” setting, ensure you select “Using ‘Respond to Webhook’ Node”
- Subsequently, place the “Respond to Webhook” node at the conclusion of your workflow.
Additionally, in the last workflow you shared, it appears the “Respond” option was not configured correctly. Please verify that you are using “Fixed” mode rather than “Expression”.
Kindly try these adjustments and inform me if you continue to encounter any difficulties…
Thank you for the quick response!
I've implemented this, but it's still not working. I've also noticed that triggers aren't activating in my workflow. Sheet triggers, schedule triggers, etc., only work after I manually execute them, which makes me wonder what I might be doing wrong.
For example:
I'm attempting to use an HTTP GET request from callin.io, but the trigger doesn't activate after the call. How can I resolve this? Thank you.
Oh wait, are you sure you’re copying the correct URL? If you’ve activated the workflow, you should be using the “Production URL”
Yes, I am utilizing the production URL.
I'm running out of ideas, to be honest.
Could you try testing this trigger using Postman or another tool to help narrow down and pinpoint the issue?
It's assumed the workflow is set to Active
. If it were not, you would encounter a message like “The requested webhook … is not registered.”
It's also assumed the HTTP verb matches correctly. If it didn't, you would see a message such as: “This webhook is not registered for GET requests. Did you mean to make a POST request?”
I'm wondering if callin.io is correctly adding the Content-Type: application/json
header when it sends the POST request to callin.io. If not, callin.io will receive the body/content as a binary item (resulting in nothing in $json). If this is the situation, you might be able to override or mitigate this by enabling the Raw Body
option on the Webhook
node and then extracting the JSON content as the initial step in your workflow.
Is this the documentation for setting up the callout from callin.io? Custom tools
Yes, that documentation is for the tool. The workflow is currently active.
I also performed a test using a GET request, and it still isn't functioning.
When I send requests to the webhook, I receive a 200 status code, but no data is being received.
Are you seeing the “Workflow was started” message on the client side? Have you checked the logs in callin.io to see the response it receives from callin.io?
I managed to get it working by inspecting the executions and pinning the webhook. It turned out it was functioning, but wasn't visible in the editor. I'm not sure why that occurred. Thank you both for your help.
This thread was automatically closed 7 days following the last response. New replies are no longer permitted.