Canva

Install corsair and @corsair-dev/canva, add the Canva plugin, and connect with OAuth. Then call methods like corsair.canva.api.assets.delete() from your app. Corsair stores tokens, and syncs data per tenant.

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

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

Teams use Corsair for design platform for creating graphics, presentations, and visual content collaboratively. Common builds include sync jobs, admin tooling, and agents that call Canva APIs from your backend. Local DB entities let you query synced Canva 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 Canva 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/canva in the open repo. When Canva 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 Canva data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Canva data on your behalf.