How can I integrate multiple google calendars atta...
# support
h
lets say i have 3 agents that are for different customers and those 3 bots have to use 3 different calendars, how do i manage that, right now i connect my google calendar integration but i only attach it to one account, do i just click the connect button again and login to a different account and then specify the calendar id?
v
Thank you for your question! To clarify, are you looking to have each bot use a completely separate Google account (with its own calendar), or do you want all bots to access different calendars under a single Google account? This will help me provide the most accurate integration steps for your setup. Source: - [Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar)
h
@Vapi Support Bot each bot has 1 calendar on separate google accounts, so 3 google accounts 1 for each bot
v
To integrate multiple Google Calendars (each from a different Google account) for separate bots, connect each Google account one at a time via **Dashboard > Provider Keys > Tools Provider > Google Calendar**—logging in with the appropriate account each time. Then, when creating a calendar tool for each bot, specify the correct
calendarId
and assign the tool to the corresponding assistant. Example:
Copy code
json
{
  "type": "google.calendar.event.create",
  "name": "scheduleForBotA",
  "metadata": { "calendarId": "botA_calendar_id" }
}
Repeat for each bot/account. This ensures each bot uses its own Google Calendar integration. [See documentation](https://docs.vapi.ai/tools/google-calendar) Source: - [Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar)
h
@Vapi Support Bot I get this error Missing Nango configuration for tool type: google.calendar.event.create
t
Your integration doesn't have permission to create a new calendar event, which means, it can't book Appt but
h
@Tay Do you know how to enable that?
t
Can you please send a DM? Let's get on a call, review your current setup and find a permanent fix to this problem.
@Haaris-Blackframe