Google Calendar

Install corsair and @corsair-dev/googlecalendar, add the Google Calendar plugin, and connect with OAuth. Then call methods like corsair.googlecalendar.api.calendar.getAvailability() from your app. Corsair verifies webhooks, stores tokens, and syncs data per tenant.

Yes. Google Calendar needs an OAuth app with scopes that match what you automate. Register the app in Google Calendar, configure redirect URLs, then connect through Corsair or managed OAuth in Hub.

Yes. One Corsair client can hit Google Calendar, GitHub, Notion, Stripe, and the rest. Trigger Google Calendar from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for scheduling service for creating events, managing calendars, and checking availability. Common builds include sync jobs, admin tooling, and agents that call Google Calendar APIs from your backend. Webhook handlers react to Google Calendar events and fan out to Slack, email, or other plugins in the same tenant. Local DB entities let you query synced Google Calendar records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Google Calendar API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/googlecalendar in the open repo. When Google Calendar ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Google Calendar data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Google Calendar data on your behalf.