Connect a user's Google or Microsoft calendar to Recall.ai (Calendar V2) and auto-schedule bots for their meetings

Documented steps

1. Google: in Google Cloud Console enable the Google Calendar API, create an OAuth 2.0 client, and request scopes calendar.events.readonly (sensitive) plus userinfo.email. The redirect URI must be on your own domain, never Recall's. Ref: https://docs.recall.ai/docs/calendar-v2-google-calendar
2. Microsoft: register an Azure Entra app for 'accounts in any organizational directory and personal Microsoft accounts', add a Web redirect URI on your domain, create a client secret, and grant Microsoft Graph delegated permission Calendars.Read. Ref: https://docs.recall.ai/docs/calendar-v2-microsoft-outlook
3. Run the provider's OAuth authorization-code flow for the end user and capture a long-lived refresh_token.
4. Create the connection via Recall's Create Calendar endpoint with {oauth_client_id, oauth_client_secret, oauth_refresh_token, platform: 'google_calendar' | 'microsoft_outlook'} and store the returned calendar id. Ref: https://docs.recall.ai/docs/calendar-v2-integration-guide
5. For user-scoped frontend access, POST https://<region>.recall.ai/api/v1/calendar/authenticate/ with {user_id} to mint a short-lived token (expires after 1 day; 300 req/min). Ref: https://docs.recall.ai/reference/calendar_authenticate_create
6. Subscribe to Calendar V2 webhooks: calendar.update (status changes such as disconnected; payload carries calendar_id) and calendar.sync_events (payload carries calendar_id and last_updated_ts). Ref: https://docs.recall.ai/docs/calendar-v2-webhooks
7. On calendar.sync_events, GET https://<region>.recall.ai/api/v2/calendar-events/?calendar_id=<id>&updated_at__gte=<last_updated_ts> and skip entries where is_deleted is true. Ref: https://docs.recall.ai/reference/calendar_events_list
8. Apply your own auto-join rules (external attendees, acceptance status, meeting platform), then POST https://<region>.recall.ai/api/v2/calendar-events/{id}/bot/ with {deduplication_key, bot_config}; meeting_url and join_at are inherited from the calendar event unless overridden. Ref: https://docs.recall.ai/reference/calendar_events_bot_create
9. Use a consistent deduplication_key formula - '{start_time}-{meeting_url}' for one bot per meeting across attendees, or append '-{event_id}' for one bot per calendar.
10. To change or cancel, re-POST the same schedule endpoint (last config wins) or call Delete Bot From Calendar Event; avoid the generic Update Scheduled Bot endpoint for calendar-linked bots. Ref: https://docs.recall.ai/docs/scheduling-guide
11. Handle disconnection: calendar.update fires with a disconnected status when the calendar is removed or the refresh token is revoked - re-fetch the calendar object and prompt the user to reconnect.