Google Calendar - Multiple Calendars Management
# support
f
I've set up multiple Google Calendars, each intended for a different doctor in a hospital. My goal is to use a separate calendar for booking appointments for each doctor, ensuring they remain independent. However, despite specifying different calendar IDs in the tool section, the system always checks and books appointments in the primary calendar of the connected account. It seems to ignore the specified calendar ID and defaults to the primary calendar every time. Is there a solution to ensure that each booking function correctly uses its assigned calendar ID?
k
Verify that the calendarId is correctly set for each doctor’s calendar in the tool configuration, assign the appropriate tools to the assistant, and test the setup to confirm the correct calendar is being used. Video tutorial

https://youtu.be/tpxI2lTnjC8?si=Ab9GHkilS1sQMTkfâ–¾

n
Hey @Fouzantanveer I have the same problem as you. Have you been able to resolve it?
v
Actionable Step: Double-check that the
calendarId
is explicitly set in the tool configuration for each doctor's calendar and that each tool is correctly assigned to the assistant. For example:
Copy code
json
{
  "type": "google.calendar.event.create",
  "calendarId": "doctor1_calendar_id",
  ...
}
After updating, test the setup by booking an appointment and verify which calendar receives the event. If the issue persists, consider reaching out to Vapi support or sharing your configuration for further troubleshooting, as the documentation expects the
calendarId
to be respected if set correctly[^1]. [^1]: [Vapi Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar) Source: - [Vapi Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar)
v
Hey @nedyalkoboydev @fouzantanveer ! 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!
3 Views