Google Calendar tools ignore shared calendarId, always use primary calendar
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?
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?
