Hey! I recently connected my make account to Vapi so that I could use the Vapi blocks within make. I am currently trying to create a system that tracks when a google form is submitted and then initates a follow up call. I keep getting a 400 error from Vapi not being able to make the call. Can someone inform me on what I need to fix? Do I need something in the customer ID or assistant fields? If so what do I need to put? https://cdn.discordapp.com/attachments/1254915313837932646/1254915314324602930/Screenshot_2024-06-24_174311.png?ex=667b3a76&is=6679e8f6&hm=3fb4c482803e87ca0e711b627f7f26c0c728e127a12ff6062e6bf1b64e087617& https://cdn.discordapp.com/attachments/1254915313837932646/1254915314550968330/Screenshot_2024-06-24_174425.png?ex=667b3a76&is=6679e8f6&hm=f060c76fe1dc06ec1e1efef398e8542d48ad8fddefc6d90948576b68cbeaf625& https://cdn.discordapp.com/attachments/1254915313837932646/1254915314777456690/Screenshot_2024-06-24_174449.png?ex=667b3a76&is=6679e8f6&hm=8aa069f5cab36c3c35d928f23953acdfd896f4743bcadf0957ef8b665c915c46&

@TommyChryst Hello! I'm glad to hear you're using VAPI with Make. A 400 error typically indicates that there's a bad request due to incorrect or missing information in your API call. To help you better, I'll need a bit more information about how you've set up your Make scenario and the VAPI block configuration. For the VAPI block, you generally need to ensure the following: 1. **Customer ID**: This should be the unique identifier for the customer you want to call. It could be a phone number or a system-specific ID if you're using a custom integration. 2. **Assistant**: This is usually the name or ID of the voice assistant or the specific call flow you've set up in VAPI to handle the call. Make sure that: - You have the correct authentication and permissions set up in VAPI. - The phone number or customer ID you're using is in the correct format. - The assistant or call flow specified exists and is properly configured in VAPI. If you're unsure about what to put in these fields, please refer to the documentation or the setup guide you followed to integrate VAPI with Make. If you need specific guidance on the fields, I can assist you further if you provide me with the details of your current setup. If you've checked all of the above and are still facing issues, it might be best to reach out to VAPI support for a more in-depth look into your account and setup.

@Vapi could you give me an example of what I should put in the assistant field?

@TommyChryst Certainly! In the assistant field, you should put the name or ID of the voice assistant that you have configured within VAPI to handle the calls. This is typically a reference to a predefined script or call flow that you've set up to interact with the caller. For example, if you have created a voice assistant in VAPI named "CustomerFollowUpAssistant" that is designed to handle follow-up calls after a Google Form submission, you would enter "CustomerFollowUpAssistant" into the assistant field. Here's a hypothetical example: - Assistant Field: "CustomerFollowUpAssistant" This tells VAPI to use the "CustomerFollowUpAssistant" call flow to handle the call when the Google Form is submitted and the Make scenario is triggered. Please ensure that the name you enter matches exactly with the name of the assistant you've created in VAPI, as it is case-sensitive and must be spelled correctly to work. If you haven't set up an assistant yet, you'll need to do that first in your VAPI dashboard. Once set up, you can use the name of the assistant you created in the assistant field of your Make scenario. If you need help setting up an assistant or finding the correct name, please refer to the VAPI documentation or ask support for more info on this.

@Vapi I tried setting the Vapi Assistant field to the name of the bot I have in the dashboard but it returns the error: Validation failed for 1 parameter(s). Invalid value in parameter 'assistant'. Value is NOT a valid object

@TommyChryst I apologize for the confusion. It seems that the VAPI is expecting an object with specific details rather than just the name of the assistant. In this case, you might need to provide the assistant's ID instead of its name. If you have the assistant's ID, it should be a string that looks something like a UUID (for example, "79f3XXXX-XXXX-XXXX-XXXX-XXXXXXXXce48"). You would typically find this ID in the VAPI dashboard on the assistant's detail page. Here's how you can use it: 1. Copy the assistant’s ID from the top of the assistant detail page in your VAPI dashboard. 2. In your Make scenario, set the assistant field to this ID. For example: - Assistant Field: "79f3XXXX-XXXX-XXXX-XXXX-XXXXXXXXce48" Make sure to replace the example ID with the actual ID of your assistant. If you're unsure where to find this ID or if you're still encountering issues, please ask support for more info on this.

@Vapi i got the same error

@TommyChryst I'm sorry to hear that the issue persists. It seems there might be a specific format or additional parameters required for the 'assistant' field that we're not addressing correctly. To resolve this, I recommend checking the VAPI documentation for the exact structure expected for the 'assistant' parameter. It's possible that the API is expecting a JSON object with more details than just an ID. Alternatively, if you have access to any example requests or templates provided by VAPI that show the correct format for the 'assistant' field, that would be very helpful in determining what the API is expecting. If you're still unable to find the correct format or if the documentation does not clarify the requirements, the best course of action would be to reach out directly to VAPI support. They will be able to provide you with the exact requirements for the 'assistant' field based on your specific setup and the version of the API you are using. Please ask support for more info on this, and they should be able to guide you through the correct configuration for your Make scenario.

Your missing your auth token or private key .

How did you resolve it? I am getting the same error. I followed your advice to the T, but getting 400 error

My problem was that I had not formatted the phone # properly. You do not need an assistant or customer ID field

Thanks, the phone# is formatted, but it is still not working

don't know if you managed but basically the phone number format should look like this: +(country_id)numbers. so let's say im in france: +(33)123456789

Stop using this - its limited. No point.

Were you able to resolve this error?

@Chowderr maybe we can take the VAPI module down if it's not going to be changed? Creating more confusion than anything else huh

It's a 50/50 thing. Makes sense and does not. 1. Most people using the module don't know how VAPI work. (dont read docs) 2. Right now the module is just not as flexible....yet 3. I think it will be updated in the future. 4. I think automating VAPI outside of any automation platform is better (depending on the API call we are talking about)

@Chowderr those all seem like arguments against having a vapi module on Make 😅 at least not yet. Not hating on anything, you all are doing amazing work. Still, a product is about users being able to use it effectively and intuitively and right now it just isn’t, regardless of it being because people don’t read docs. Instead, people are just getting confused and frustrated so it just seems like a lose-lose to keep that module alive

I try not to be bais with me answers and look at all angles. I agree it's subpar - but I understand on a tech level why it is subpar as well. I don't think your hating at all. Honest feedback. Also I don't work for VAPI. I might need a sponsor cuz everybody thinks so. I am neutral when it comes to platforms, but I do have to admit there is a significant amount of user hours/ lack of understanding as well.

Thanks for being so involved man @Chowderr ❤️

Hi everyone, I’m having issues executing an outbound call with my assistant using a Make.com scenario where I've connected HubSpot with VAPI. Everything works flawlessly when making calls to UK phone numbers. However, I keep receiving a 400 error whenever I try to call a Spanish number, which is a more typical use case for my business. I've tried various phone number formats, but the error persists. Does anyone have any suggestions or solutions?

Well what is the error you get - surely it's the number.

Its a 400 code error. Yes, its 100% number/format related. The scenario works well when a use an UK number.

hubspot problem Talk tot hem. Its not a vapi problem.

I doubt its a hubspot problem

Okay - but if it's number/format related that's coming from your CRM. If other numbers work in a CRM but a certain one does not - then it's the CRM

If I just write down a spanish number instead of feeding it from the CRM it gives me the same error

So you hard a code a number and it does not But from the CRM it works?

It works with UK numbers regardless of it coming from CRM or hardcode. It does not with Spanish numbers in either case

What does the 400 error say?

It does not say much really

Have you activated the calling country Spain on Twilio?

Hi @KarlKing No, I did not know I needed to activate anything in twilio. I am using a Vapi American phone number

I don't know what it's like if you got your phone number from Vapi. But if you have your own Twilio account (phone number imported to Vapi) then you can change permisssios on: Console > Messaging > Settings > Geo Permissions .

I have my own Twilio account, (trying to apply for a ES number), but I purchased this number in VAPI directly

You are doing something wrong in the automation for sure. Like a wrong ID or something. Do you not have the assistantID filled out?

Yes I do

I don't know what it's like if you get your phone number from Vapi directly. Perhaps Vapi can change these settings, or you can do it yourself if you have the Twilio credentials.

Just use a HTTP module and stop using the VAPI one.

i just purchased a twilio phone number and Imported it

Yeahh! 🙂 ... Good luck to you! 🙂

This is your imported number right?

Yes

Still have to find the problem for not imported right?

closing this ticket for now, for issues create a new ticket.