I'm using Vapi's native Google Calendar tools (check availability and create event) with a valid Google Provider Key. My client shared their business calendar with full permissions, and I'm using the shared calendar ID (not the primary one) in the tool configuration and tool call. However, even when passing the correct calendarId in the request payload, Vapi seems to ignore it and defaults to my primary calendar instead. This leads to incorrect availability checks and events being created in the wrong calendar. Steps already taken: The shared calendar is fully visible and editable from my Google account. The calendarId is correctly set in the tool parameters. I reconnected the Google Provider Key to ensure permissions are refreshed. The shared calendar is public and accessible. This is critical for production use — is this a known limitation or am I missing a step?

Based on similar issues reported, Vapi might be defaulting to the primary calendar despite your configuration. Try updating your tool configuration using the API instead of the UI, as this has resolved similar issues:

bash
curl -X PUT https://api.vapi.ai/api/tools/{toolId} \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "parameters": {
      "calendarId": "shared_calendar_id@group.calendar.google.com"
    }
  }'

This bypasses potential UI bugs that prevent settings from being properly saved. Sources: - [Discord discussion about Vapi defaulting to provider values](https://discord.com/channels/1211482211119796234/1331719181732679751) - [Discord discussion about Vapi UI bugs](https://discord.com/channels/1211482211119796234/1336339138898694184)

Hey! 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 us figure out what went wrong!

Hi Shubham, Thanks for getting back to us. We're currently experiencing an issue where the Calendar tools in Vapi (Check Availability / Create Event) only seem to read from the Primary calendar, even when we explicitly configure a different calendarId (e.g., a shared calendar or a secondary one connected via the Provider Key). To help with your investigation: Call ID: df.donbenitoopticos@gmail.com Timestamp: The issue has been consistent; last tested on 2 may 2025, 01:29 Expected behavior: The assistant should read availability and create events in the calendar specified in the tool which is a secundary calendar named above Actual behavior: The assistant only queries the Primary calendar of the connected Google account, ignoring the calendarId passed through the API or UI It seems Vapi may be overriding our settings and defaulting to the connected Primary calendar despite correct configuration. Looking forward to any insight or workaround you might offer! Best regards,

Hey, what you have shared in place of call ID, it's an email address. You can find the recent call ID related to your issue from here.

No, it is my CalendarID, look https://cdn.discordapp.com/attachments/1367814022703087627/1369646405999923383/image.png?ex=681c9e1d&is=681b4c9d&hm=2bc42350a06086b1f5ffc4d910283d1cde3dbac57170f51ee3596ac5f18aec7a&

To investigate the issue and provide assistance, I require the call ID. Could you kindly share it with me?

Similarly having this issue on my end as well

Try updating your Google Calendar tool configuration using the API instead of the UI, as this can bypass UI bugs that may cause the

calendarId

to be ignored. Use the following command, replacing the placeholders with your actual values:

bash
curl -X PUT https://api.vapi.ai/api/tools/{toolId} \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "parameters": {
      "calendarId": "your_shared_calendar_id@group.calendar.google.com"
    }
  }'

This approach has resolved similar issues for other users when the UI did not save the

calendarId

correctly. Source: - [Vapi Google Calendar Tool Documentation](https://docs.vapi.ai/tools/google-calendar)

This ticket has been marked as solved, and as a result, you will no longer receive any further responses. Kindly create a new support ticket to escalate your inquiry.