Tool Creation Failed
# support
its using the make automation
v
message has been deleted
@! John Jahshan I'm sorry to hear you're having trouble creating tools on VAPI. To better assist you, could you please provide me with more details about the issue you're encountering? For example, are you receiving any specific error messages, or is there a particular step in the process where things seem to go wrong? This information will help me understand the problem and guide you towards a solution.
You can continue this conversation by mentioning me in the message.
u
yeah it says tool creation failed
yeah it says tool creation failed @Vapi
v
@! John Jahshan I understand that you're experiencing a "tool creation failed" error. This could be due to a variety of reasons such as incorrect parameters, network issues, or a problem with the VAPI service itself. To help you resolve this, I'll need a bit more information: 1. Can you confirm that you are following the correct procedure for creating a tool using the 'make automation' feature? 2. Have you checked if all the required fields and parameters are correctly filled in? 3. Is this the first time you're encountering this issue, or has tool creation worked for you in the past? Once I have more context, I'll do my best to assist you further. If the issue persists, it may be necessary to reach out to VAPI's support team for more in-depth troubleshooting.
u
1. i beleive it is correct 2. all fields were added, webhook url, information, and parameter was created 3. yes it works on another account i have, just trying to make it on a new accout @Vapi
v
@! John Jahshan Thank you for providing additional details. Since tool creation works on another account but not on the new one, it's possible that there may be an issue specific to the new account settings or permissions. Here are a few steps you can take to troubleshoot the issue: 1. **Check Account Permissions**: Ensure that the new account has the necessary permissions to create tools. There might be different access levels or restrictions on the new account. 2. **Verify API Key**: Make sure that you are using the correct API key for the new account. If the key is incorrect or has not been set up properly, it could prevent tool creation. 3. **Review Quotas and Limits**: Some accounts have quotas or limits on the number of tools that can be created. Check if you've reached any such limits on the new account. 4. **Double-Check Parameters**: Although you've mentioned that all fields were added, it's worth reviewing them once more to ensure there are no typos or formatting issues. 5. **Try a Different Browser or Clear Cache**: Sometimes, browser-related issues can cause unexpected behavior. Try using a different browser or clear the cache of your current browser. 6. **Contact Support**: If none of the above steps resolve the issue, it may be best to contact VAPI support directly. They can provide account-specific assistance and investigate any potential bugs or service outages. If you'd like, I can assist you in reaching out to the support team. Would you like me to initiate that process for you?
s
We are aware about it and we are working on it
p
same issue for me. do we have an eta on a fix? thx
s
Will be fixed by tomorrow.
m
any update on this? I just joined and am getting the same error when trying to create a new tool using a make.com webhook url
j
@Sahil I am getting the tool creation failed error again
@Sahil I figured it out - it needs to be https. could you make it indicate that?
s
Adding @Shubham Bajaj to this thread
he will help you out
s
Hey @! John Jahshan / @jsieber-eip just checking if this is resolved for you?
j
yeah- it didnt specify it needed to be an https call via the ui @Shubham Bajaj , wanted to let you know though that your api documentation on the endpoints might need to be regenerated. some weirdness occurs. example: says enabled defaults to false, and defaults to true https://cdn.discordapp.com/attachments/1254251809308934204/1305927711939629198/image.png?ex=6734cf75&is=67337df5&hm=5a09ddce9d680a70d2357d128e3cf5734242e57296294f4fcde0ac3449444e07&
u
Yup this is all good to go, this is a while back, thanks though
s
It's false, looking into ti.
4 Views