Wekhook consistent error
# supportb
brandon holley
12/23/2024, 5:40 PMI'm using a tool within my agent. Everytime the tool is trigger by the agent I get this webhook response in make.com. I don't have any error logs other than the error below so I'm not sure what to do. @Vapi @User
Webhooks - Custom webhook1
The Rollback Phase was completed with a warning.
Warning
Automatic failure response was sent to the webhook.
https://cdn.discordapp.com/attachments/1320808266418229250/1320808487923744880/image.png?ex=676af242&is=6769a0c2&hm=63fa2202a273c10f4360a2b9b74145a0c2d02520e6abb994d352f5406d2e1cfb&
brandon holley
12/23/2024, 5:41 PMI'm using a tool within my agent. Everytime the tool is trigger by the agent I get this webhook response in make.com. I don't have any error logs other than the error below so I'm not sure what to do. @Vapi
v
Vapi
12/23/2024, 5:41 PM@brandon holley
It sounds like you're encountering an issue with a webhook in make.com when it's triggered by your agent. The warning message you're seeing, "Automatic failure response was sent to the webhook," typically indicates that the webhook received a request but the process that should follow the request did not complete successfully, hence a failure response was sent back.
Here are a few steps you can take to troubleshoot this issue:
1. **Check the Configuration**: Ensure that the webhook URL and payload format in your agent are correctly configured to match what make.com expects.
2. **Review the Payload**: Verify that the data being sent to the webhook is in the correct format and contains all the necessary information.
3. **Examine the Scenario Logic**: In make.com, review the scenario that is triggered by the webhook. Look for any filters, conditions, or actions that might be causing the process to fail.
4. **Test the Webhook Manually**: Try sending a test request to the webhook URL from a tool like Postman or curl to see if you can replicate the issue.
5. **Check make.com Logs**: Look for any logs or error messages in make.com that could give you more information about why the failure response is being sent.
6. **Contact Support**: If you're unable to resolve the issue with the above steps, consider reaching out to make.com support for further assistance.
If you need more specific guidance or if there's anything else I can assist you with, please let me know!
Vapi
12/23/2024, 5:42 PMmessage has been deleted
Vapi
12/23/2024, 5:42 PM@brandon holley
It seems like you're encountering a warning during the Rollback Phase when using a webhook with make.com (formerly Integromat). The warning indicates that an automatic failure response was sent to your webhook. This typically means that the receiving system (your agent) has acknowledged the incoming data but has encountered an issue that prevents it from processing the data as expected.
Here are a few steps you can take to troubleshoot the issue:
1. **Check the Configuration**: Ensure that the webhook is correctly configured in your agent and in make.com. Verify that the URL, headers, and payload structure match what your agent expects.
2. **Review the Payload**: Look at the data being sent to the webhook. Ensure that it is in the correct format and contains all the necessary information your agent needs to process it.
3. **Examine the Agent's Logic**: Review the logic within your agent that handles the webhook's data. There might be a condition or a scenario that is not being handled properly, leading to the warning.
4. **Error Handling**: Implement or review the error handling in your agent. Make sure that it can gracefully handle unexpected data or scenarios and provide more detailed error logs.
5. **Consult Documentation**: Refer to the documentation for both make.com and your agent to understand the expected behavior and how to handle different phases, including the Rollback Phase.
6. **Contact Support**: If you've gone through these steps and are still facing issues, it might be best to contact support for make.com or the support for the tool you're using within your agent. They may provide more insight into the warning and how to resolve it.
If you need further assistance or have specific questions about your agent's implementation, please provide more details so I can offer more targeted advice. If you believe the issue has been resolved, I can proceed to close this support ticket for you.
Vapi
12/23/2024, 5:42 PMYou can continue this conversation by mentioning me in the message.
b
brandon holley
12/23/2024, 5:44 PMI have gone through those steps. I'm just using a webhook module in make.com @Vapi
https://cdn.discordapp.com/attachments/1320808266418229250/1320809336267608064/image.png?ex=676af30d&is=6769a18d&hm=1e24081895d34185f4055bd149aba430175a1a333dd6a0591dfde9031369edc6&
v
Vapi
12/23/2024, 5:44 PM@brandon holley
If you have already gone through the basic troubleshooting steps and are still experiencing issues with the webhook module in make.com, here are a few additional suggestions:
1. **Check Webhook Response**: Ensure that the response from your agent to the webhook is correctly formatted and contains the expected status codes. A response that is not in the expected format could trigger a warning.
2. **Review Webhook Settings**: Double-check the settings of the webhook in make.com, including the response structure that make.com is expecting. Make sure that the response from your agent aligns with these settings.
3. **Inspect Data Flow**: Look at the data flow in make.com's scenario editor to ensure that the data from the webhook is being passed correctly to subsequent modules.
4. **Monitor Real-time Runs**: Use the real-time monitoring feature in make.com to watch the scenario execute step by step. This can help identify exactly where the failure is occurring.
5. **Test with a Simplified Scenario**: Create a simplified scenario with just the webhook and a basic action to see if the issue persists. This can help isolate the problem.
6. **Reach Out to Community Forums**: Sometimes, community forums or user groups for make.com can provide insights from other users who might have faced similar issues.
7. **Contact make.com Support**: If none of the above steps resolve the issue, reaching out to make.com support might be the best course of action. They can provide more detailed assistance and may have access to logs that can shed light on the problem.
Remember to provide as much detail as possible when seeking help, including the steps you've already taken, the exact warning message, and any relevant configuration details. If you need further assistance or have more questions, feel free to ask.
b
brandon holley
12/23/2024, 6:05 PM@Vapi Incident @User @User I talked to quite a few people and we are all experiencing the same thing. Webhook tools are not operating properly
s
Shubham Bajaj
01/05/2025, 10:10 PM@brandon holley Sorry for the late response. Are you still experiencing this problem? If so, could you send over a recent call ID so I can take a look?
Shubham Bajaj
01/11/2025, 4:54 PMBecause of no response closing this ticket.