VapiUser
05/21/2025, 10:10 PMVapi Support Bot
05/21/2025, 10:11 PMjson
{
"tools": [
{
"type": "google.calendar.event.create",
"name": "scheduleAppointment",
"description": "Use this tool to schedule appointments and create calendar events."
},
{
"type": "google.calendar.availability.check",
"name": "checkAvailability",
"description": "Use this tool to check calendar availability."
}
]
}
Note: You must ensure the assistant uses the right user's OAuth token for calendar actions. The docs do not specify how to programmatically associate tokens per assistant, so you may need to manage this mapping in your backend.
[See Google Calendar integration docs](https://docs.vapi.ai/tools/google-calendar)
Source:
- [Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar)VapiUser
05/21/2025, 10:14 PMVapi Support Bot
05/21/2025, 10:15 PMtools
array:
json
{
"tools": [
{
"type": "google.calendar.event.create",
"name": "scheduleAppointment",
"description": "Use this tool to schedule appointments and create calendar events."
},
{
"type": "google.calendar.availability.check",
"name": "checkAvailability",
"description": "Use this tool to check calendar availability."
}
]
}
4. Important: You must ensure your backend maps each assistant to the correct user's OAuth token for calendar actions, as the docs do not specify a built-in way to do this programmatically.
For more details, see the [Google Calendar integration documentation](https://docs.vapi.ai/tools/google-calendar).
Source:
- [Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar)VapiUser
05/21/2025, 10:19 PMKyle
05/23/2025, 12:29 AMVapiUser
05/23/2025, 5:11 AMVapi Support Bot
05/23/2025, 5:11 AMtools
array of the assistant's configuration.
4. Store each user's OAuth token in your backend and map it to their assistant. When an assistant needs to access Google Calendar, your backend should retrieve the correct token for that user and use it for the API call. For example:
python
# Pseudocode
user_token = get_token_for_assistant(assistant_id)
calendar_api_call(token=user_token, ...)
Note: Vapi does not provide a built-in way to associate tokens per assistant, so this mapping and secure storage must be managed in your backend logic.
If you need to handle token storage, retrieval, or refreshing, you'll need to implement those details according to your backend's requirements.
Source:
- [Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar)AhmedAli
05/26/2025, 2:42 AMVapi Support Bot
05/26/2025, 2:44 AMAhmedAli
05/26/2025, 3:14 AMVapi Support Bot
05/26/2025, 3:15 AMAhmedAli
05/26/2025, 5:10 AMVapi Support Bot
05/26/2025, 5:11 AMcredentials
or authorizationId
fields. All Google Calendar actions use the account connected in the Vapi Dashboard under Provider Keys. If you need per-user access, you must handle OAuth and Google Calendar API calls in your own backend, not through Vapi's built-in tools.
There is no documented way to use credentials
or authorizationId
for Google Calendar integration at this time.
[See official documentation for details.](https://docs.vapi.ai/tools/google-calendar)
Source:
- [Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar)Vapi Support Bot
05/26/2025, 5:12 AMcredentials
and authorizationId
fields are not documented for use with Google Calendar user tokens—**all calendar actions use the account connected in the Vapi Dashboard under Provider Keys**.
If you need per-user calendar access, you must implement your own OAuth flow and interact with the Google Calendar API directly from your backend.
[See official documentation for details.](https://docs.vapi.ai/tools/google-calendar)
Source:
- [Google Calendar Integration Documentation](https://docs.vapi.ai/tools/google-calendar)