I want guidance regarding webhook issues and error...
# support
v
@maaz hasan It sounds like you're encountering a warning in your webhook scenario related to checking availability. To assist you better, I'll need a bit more information about the warning message you're receiving. Could you please provide me with the specific warning text or describe the issue in more detail? This will help me understand the context and offer you the most accurate advice.
You can continue this conversation by mentioning me in the message.
m
I sent you screenshots of warning @Vapi
v
@maaz hasan Please ask support for more info on this.
m
Where is it ? This support
@Vapi
v
@maaz hasan I apologize for any confusion. As a text-based support bot, I'm unable to view screenshots. However, I'm here to help you with any issues you're facing with your webhook scenario. Could you please describe the warning message you're seeing, or provide the text of the warning? Once I have more details, I'll do my best to assist you in resolving the issue.
m
You will assist me if I'm having it in make.com but I'm using vapi for it
@Vapi
v
@maaz hasan I'm here to assist you with your VAPI-related queries. If you're integrating VAPI with a scenario in make.com and encountering a warning, please describe the warning message or the issue you're facing. With more details about the problem, I can provide you with guidance on how to resolve it or suggest the next steps to take. If the issue is specific to make.com's platform and not directly related to VAPI, it might be best to consult make.com's support resources or documentation for platform-specific troubleshooting.
m
Referenced module 'webhooks-webhook response [6] is not accessible
This is the warning @Vapi
v
@maaz hasan Thank you for providing the warning message. The warning "Referenced module 'webhooks-webhook response [6] is not accessible" typically indicates that there is an issue with the configuration of your webhook scenario in make.com (formerly Integromat). Here are a few steps you can take to troubleshoot this issue: 1. **Check Module Accessibility**: Ensure that the module 'webhooks-webhook response [6]' is correctly configured and accessible within your scenario. It might be disabled or not properly set up. 2. **Review Scenario Design**: Look at the flow of your scenario to make sure that the webhook response is being triggered after the webhook is called. There should be a logical sequence that leads to the webhook response. 3. **Check Permissions**: If you're using an account with limited permissions, make sure you have the necessary rights to access and modify the webhook module. 4. **Review Webhook Settings**: Double-check the webhook URL and settings to ensure they match what's expected by the service you're integrating with VAPI. 5. **Test the Webhook**: Try sending a test request to your webhook URL to see if it's functioning correctly outside of the make.com scenario. If you've gone through these steps and the issue persists, it might be a good idea to reach out to make.com's support team for further assistance, as the problem could be specific to their platform. If the issue is related to VAPI and you need assistance with the VAPI configuration or have questions about how to use VAPI within make.com, please provide more details, and I'll do my best to assist you.
c
Ummm...This is a "Make" support problem, not vapi You trying to force an A.I that does not know about Make is going to get you no-where.
m
Yes I understand that's why I stop
s
@maaz hasan This issue is not related to Vapi instead you have to ask Make support team for this..
3 Views