Gmail

Install corsair and @corsair-dev/gmail, add the Gmail plugin, and connect with OAuth. Then call methods like corsair.gmail.api.drafts.create() from your app. Corsair verifies webhooks, stores tokens, and syncs data per tenant.

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

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

Teams use Corsair for google email service for sending, reading, organizing messages, labels, and inbox automation. Common builds include sync jobs, admin tooling, and agents that call Gmail APIs from your backend. Webhook handlers react to Gmail events and fan out to Slack, email, or other plugins in the same tenant. Local DB entities let you query synced Gmail 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 Gmail 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/gmail in the open repo. When Gmail 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 Gmail data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Gmail data on your behalf.