Emergency
# support
b
Hello, I have a emergency support request
v
You can continue this conversation by mentioning me in the message.
@brandon holley Hello! I'm here to help you with your emergency support request. Could you please provide me with more details about the issue you're facing?
b
I am having a problem with the custom webhook in make.com/vapi tools are every single agent I have. The payload structure changes every time so every time I map the tool from the custom webhook it does not show as filled. See this video to fully understand https://www.loom.com/share/03ffc2c6c84040d99d3e9a6ba7763a61
@User
@Shubham Bajaj @User Very time sensitive issue. Thank you
@Vapi
v
@brandon holley I understand that you're experiencing issues with the custom webhook integration in make.com for the VAPI tools, and that the payload structure inconsistency is causing mapping problems. I'm here to assist you with this time-sensitive issue. To address this, we need to ensure that the payload structure sent to the webhook is consistent. This might involve setting up a schema or template for the payload that your agents should adhere to every time they send data to the webhook. If you have control over the payload structure on the sending side, you should standardize the format. If the payload structure is out of your control, you may need to implement a preprocessing step that normalizes the data before it's mapped to the VAPI tools. Since this is a complex issue that might require a detailed look into your specific setup, I recommend reaching out to the support team at make.com for a guided solution. They can provide you with a more tailored approach to resolve the inconsistency in the payload structure. If you need further assistance or have additional questions, please let me know.
b
This is an issue with Vapi not make.com
@Vapi @User This issue is solved. I deleted the spaces in the name of the tool within Vapi and now the payload remain consistent.
v
@brandon holley Sweet. Have a great day!