Hey all, I’m working on integrating Google Calendar with a VAPI assistant, and I could use some input from anyone who's been down this path. What I’ve Got: Google OAuth2 credentials are set up in my server. Users authorize via our frontend; we store access + refresh tokens securely I want each assistant to have calendar access specific to each user What I’m Trying to Figure Out: What exactly should go in authorizationId for google.calendar.oauth2-authorization in VAPI API? Can VAPI use our existing stored tokens, or does it force its own OAuth flow? What's the difference between dashboard-level Provider Keys and the credentials array in the assistant config api? Is there any clean way to make this multi-user without touching the VAPI dashboard? Would love to avoid rebuilding the wheel or jamming everything through external API calls if there’s a cleaner native method. Thanks in advance.. hoping someone’s already wrestled this beast and can share a battle plan tldr; how can we use vapi api to integrate google calendar without using the external tools, as vapi already has credentials fields in the api and we can link the assistant with the google calendar tool.

cc: @Kings_big💫

Here's the screenshot of what I am talking about. https://cdn.discordapp.com/attachments/1376270130324967605/1376427377084858388/Screenshot_2025-05-26_at_10.09.00_AM.png?ex=68354963&is=6833f7e3&hm=d7205988f2cb1193cc6f3aa652cda4090a7e5bb3167e609b0ac5531d72293399&

Vapi requires using its own OAuth flow for Google Calendar, with authorizationId referencing credentials set in the dashboard; existing tokens can’t be reused, but you can dynamically assign user-specific credentials in the assistant’s credentials array via API for multi-user setups without touching the dashboard manually.