Cal.com

Install corsair and @corsair-dev/cal, add the Cal.com plugin, and connect with an API key. Then call methods like corsair.cal.api.bookings.cancel() from your app. Corsair verifies webhooks, and syncs data per tenant.

Yes. Cal.com requires an API key from your Cal.com account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

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

Teams use Corsair for open scheduling platform for booking meetings, availability, and calendar integrations. Common builds include sync jobs, admin tooling, and agents that call Cal.com APIs from your backend. Webhook handlers react to Cal.com events and fan out to Slack, email, or other plugins in the same tenant. Local DB entities let you query synced Cal.com 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 Cal.com 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/cal in the open repo. When Cal.com 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 Cal.com data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Cal.com data on your behalf.