Hello, I set up VAPI and got it working at first but now it seems to not work every single time. and upon reviewing the make no matter what i try to say to vapi for booking an appointments, tomorrow, thursday, it sends a date of 2023-october and some date. so my make integration is not working, is it just me and is there some way to reset and/or fix this?

@Eric Chong | HSFM Hello! I'm glad to hear you got VAPI working initially, but I'm sorry to hear you're experiencing inconsistencies now. It sounds like there might be an issue with the date parsing within your integration. Here are a few steps you can take to troubleshoot and potentially resolve the issue: 1. Check Your Date Parsing Logic: Review the part of your code or integration that handles date extraction from the user's speech. Ensure that it's correctly interpreting the dates and not defaulting to October for some reason. 2. Review Logs: If your system keeps logs, check them for any errors or warnings that occur when the system tries to parse dates. This might give you insight into what's going wrong. 3. Update Your Models: If you're using any machine learning models for date parsing, make sure they are up to date and trained on relevant data. 4. Reset Your Integration: If you have the option to reset or reinitialize your integration, doing so might clear any temporary issues. 5. Contact Support: If you've tried these steps and are still facing issues, it might be best to reach out to the support team for more personalized assistance. You can email them at [support@vapi.ai](support@vapi.ai). If you'd like, I can assist you in sending an email to the support team to get more help on this issue. Would you like me to do that for you?

Attempting to set up your VAPI system and got it working and successfully booked the first time but have been getting errors ever sinde and i thought it was my problem but it seems like theres a weird error on my account causing the API to pass a date through thats a year old, so i book for tomorrow but the value that comes through is october 2023, can you help to reset and/or look into my account? assistant ID: 218781a4-fe50-4ffe-ab47-5def64e93ba4 tool ID: 83033b43-4d45-4934-be5d-75abd97a56e1

Hey @Eric Chong | HSFM To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help me figure out what went wrong!

timestamp 1732076781353 CallID af287080-a0b2-4be4-9e23-f7d3ec436905 I expected to get 'tomorrow at 9:30' (which is today) It sent: argumentsCollection timeZone America/Los_Angeles appointmentTime 2023-11-01T09:30:00 Bundle 1Collection messageCollection timestamp 1732076781353 type tool-calls toolCallsArray toolCallListArray toolWithToolCallListArray 1Collection type make functionCollection async false serverCollection messagesArray toolCallCollection id call_6sw0c3ht0WZ0OQcotbqZQJH3 type function functionCollection name ghlBooking argumentsCollection timeZone America/Los_Angeles appointmentTime 2023-11-01T09:30:00

@Eric Chong | HSFM you are not including the variables required to fill current date and time in the assistant to get the current date and time do check this doc section

advanced-date-and-time-usage

https://docs.vapi.ai/assistants/dynamic-variables#advanced-date-and-time-usage. Do let me know if you face any difficulty or require further help.

I've tried adding this but its giving me an error: DataError Error: 400 Bad Request {"message":"Unexpected non-whitespace character after JSON at position 243 (line 13 column 1)","error":"Bad Request","statusCode":400} Origin HTTP Automatic error handler If you want to handle this error automatically, choose one of the following options. This will create a new error-handler route in your scenario. You can then expand the route in any way you like. { "assistantId": "218781a4-fe50-4ffe-ab47-5def64e93ba4", "phoneNumberId": "ebb4d96a-1903-418e-b67f-e5da72464653", "customer": { "number": "{{1.phone}}", "name": "{{1.first_name}}" }, "metadata": { "referredBy": "{{1.

Referred By

}}" } } {{{{now}} | date: "%b %d, %Y, %I:%M %p", "{{1.timezone}}"}} https://cdn.discordapp.com/attachments/1308650480821338123/1309372552753188904/image.png?ex=674157b7&is=67400637&hm=a9fefab49a3ed6166485f80a562d46d244cdd2853df34ef8ebd060ecb8511003&

You don't need to pass

""appointmentTime"": ""now" | date:}}%Y-%m-%dT%H:%M:%SAmerica/Los_Angeles"

inside your prompt as visible in the docs.

Yes, I understand what you are saying but I've attempted to, and I'm getting the error above, can you tell me how it needs to be formatted?do you know how this needs to be formatted

@Eric Chong | HSFM heres' the curl for creating and using defualt dynamic variables. Now coming to using with make you have to pass them as type of string only. Do let me know if you have more doubts. *FYI: * Make is correct about

toString

curl -X POST https://api.vapi.ai/call \
     -H "Authorization: Bearer token-here" \
     -H "Content-Type: application/json" \
     -d '{
  "assistantId": "insert-assistant-id-here",
  "assistantOverrides": {
    "variableValues": {
      "currentDateTimeInUTC": "{{\"now\" | date: \"%b %d, %Y, %I:%M %p\", \"America/New_York\"}}"
    },
    "metadata": {
      "referredBy": "<insert-refered-by-here> {{\"now\" | date: \"%b %d, %Y, %I:%M %p\", \"America/New_York\"}}\n"
    }
  },
  "phoneNumberId": "insert-phone-number-id-here",
  "customer": {
    "numberE164CheckEnabled": false,
    "number": "insert-customer-number-here",
    "name": "insert-customer-name-here"
  }
}'

hello brother, did you manage to fix this issue?

@Eric Chong | HSFM closing this ticket because of no response.