Assistant field in the Vapi "make outbound phone c...
# support
p
Hi, I'm trying to trigger an outbound call from Hubspot using Make.com and the VAPI module. Its currently failing with [400] Bad Request. I have all the following fields populated correctly (I think) Assistant Id Customer Phonenumber Customer Name Phone Number ID I don't have the 'Assistant" field populated. Do I need to populate this field, and if so, what do I enter in it ? Any help would be appreciated
v
@Phil Hello! It sounds like you're on the right track with setting up your outbound call. The 'Assistant' field typically refers to the specific assistant instance that will handle the call. If you have the 'Assistant Id' populated, that should usually suffice, as it uniquely identifies the assistant to be used for the call. However, if you're receiving a [400] Bad Request error, it could be due to a few reasons: 1. **Incorrect Assistant Id**: Double-check that the Assistant Id you've entered is correct and corresponds to an existing assistant in the VAPI system. 2. **Invalid Phone Number Format**: Ensure that the customer's phone number is in the correct format, including the country code if necessary. 3. **Missing or Incorrect Phone Number ID**: The Phone Number ID should correspond to a number you own or have configured in the VAPI system that will be used to make the call. 4. **Required Fields**: Make sure all required fields are not only populated but also contain the correct type of data expected by the VAPI module. The 'Assistant' field you mentioned might not be necessary if you've already provided the 'Assistant Id'. However, if the VAPI module you're using in Make.com requires this field, it should be the name or identifier of the assistant that is configured within VAPI to handle the calls. If you're unsure about what to enter for the 'Assistant' field or if it's required, please check the documentation for the VAPI module you're using in Make.com, or reach out to their support for clarification. If you've verified all the details and are still facing issues, please provide more information or any specific error messages you're receiving, and I'll do my best to assist you further.
You can continue this conversation by mentioning me in the message.
p
@Vapi Thanks. It was down to the + not being in the phone number. One other query. How can I also pass details such as name , email to the VAPI bot ?
v
@Phil I'm glad to hear that the issue with the phone number format has been resolved! To pass additional details such as a customer's name and email to the VAPI bot, you would typically include these as custom parameters in the payload of your API request when initiating the call. The exact structure of the payload may vary depending on the capabilities of the VAPI platform you're using, but here's a general example of what it might look like:
Copy code
json
{
  "assistantId": "your-assistant-id",
  "customerPhoneNumber": "+1234567890",
  "customerName": "John Doe",
  "customerEmail": "john.doe@example.com",
  "phoneNumberId": "your-phone-number-id"
}
In this example,
customerName
and
customerEmail
are additional fields that you can include in your API request. Make sure to check the VAPI documentation or the integration settings on Make.com to confirm the exact field names and format required. Once these details are passed to the VAPI bot, you can use them within your voice application to personalize the call experience, such as by addressing the customer by name or referencing their email during the conversation. If you need further assistance with the specific syntax or method for passing these details in your setup, please consult the documentation for the VAPI module you're using or reach out to their support team for more detailed guidance.
p
OK. Where would I put this in the VAPI module in make.com ? Or would I have to send an HTTP POST with this JSON at the same time ?
l
You are going to input this on make on the https post
And as for sending passing Details to your vapi you are going to do that in make
What database do you make use of?
s
@Phil just checking, is it resolved for you?