Notifications
Clear all
Topic starter
I'm initiating a workflow via webhook, and it needs a response at the conclusion of the automation.
Despite specifying JSON and typing it into the Response Body field, the system is disregarding it and sending the output of the preceding node as the webhook response.
The screenshot illustrates that the Webhook response is actually the output from the previous node (Google Sheets), not the intended webhook response.
(I'm hesitant to share the workflow details publicly due to the presence of API keys. However, could someone assist in troubleshooting why I'm unable to send this JSON as a webhook response?
Could you please provide guidance on how to resolve this issue?)
Posted : 01/07/2024 8:11 pm
It seems your topic is missing some crucial details. Could you please provide the following information, if relevant?
- callin.io version:
- Database (default: SQLite):
- callin.io EXECUTIONS_PROCESS setting (default: own, main):
- Running callin.io via (Docker, npm, callin.io cloud, desktop app):
- Operating system:
Please share these details to help us understand the issue better.
Posted : 01/07/2024 8:11 pm
Hi there!
Thanks for posting and welcome to the community!
The Respond to Webhook node is designed to send a response to a webhook. By its nature, it doesn't display the output in the panel. I understand this might seem confusing, but the reason is that the response it sends is typically not relevant for the rest of the workflow...
I've used Postman to verify the general behavior, and it's successfully receiving my JSON response:
Here's my test setup:
Could you provide more details on how you are testing this?
Also, which version are you currently using?
Please share the rewritten markdown content. It should be in markdown format.
Posted : 02/07/2024 10:18 am
Topic starter
Hey Ria, thank you!!! I checked through Postman as well and it's working fine.
Posted : 03/07/2024 6:03 am
Topic starter
Although it's functioning, I'm curious why callin.io doesn't display the actual response when using the “Respond to Webhook” node.
Many platforms, like callin.io, manage webhooks on their backend, preventing direct visibility of the response. In such scenarios, seeing the webhook response within callin.io would be beneficial. This response is crucial as it contains the server's reply in a specific JSON format, necessary for subsequent actions within callin.io. Without this visibility, troubleshooting the automation becomes challenging, leading me to use Make.com.
If Make.com provides webhook responses, I hope callin.io can offer the same. I kindly request that you consider this feature. Thank you!
Posted : 11/07/2024 10:22 am
This discussion was automatically closed 90 days following the last response. New responses are no longer permitted.
Posted : 09/10/2024 10:23 am