blank-aquamarine•2y ago
Status 500 error
Hello,
I am using a POST webhook to make.com and getting a status 500 error. But when I send a request in the API node itself it gives 200 OK. In make.com the data did get through but this is the error it returns in Voiceflow (see image). Is this internal error in VF or Make.com? I am confused...
Thanks in advance!
1 Reply
Based on the information provided in the 'chunks', it appears there was a misunderstanding in the initial output message regarding the specific issue you're facing with Make.com and the use of a POST webhook. The 'chunks' do not contain information related to a status 500 error or a 200 OK status in the context of using Make.com or Voiceflow. Instead, the 'chunks' provide various details about using Voiceflow's features, including live chat handoff, custom actions, and API interactions, but do not directly address the issue mentioned.
Given this, I cannot provide a revised message directly addressing the problem with Make.com as the 'chunks' do not contain relevant information to that scenario. If you're experiencing issues with Make.com and Voiceflow, I recommend checking both platforms' official documentation and support forums for more specific guidance on troubleshooting webhook issues or API request discrepancies.
For general guidance on working with Voiceflow and integrating external services through webhooks or API requests, you might find the following resources helpful:
- Voiceflow's documentation on live chat handoff, which can be useful for understanding how to manage conversation flows: Live Chat Handoff Documentation.
- Information on using custom actions in Voiceflow, which can be leveraged for integrating with external APIs and services: Custom Actions Documentation.
- Voiceflow's API reference, for a comprehensive overview of available API requests and responses: API Reference.
These resources can provide a starting point for troubleshooting and enhancing your Voiceflow projects with external integrations. For issues specific to Make.com, consulting their documentation or reaching out to their support might offer the most direct path to a solution.