Asana

Install corsair and @corsair-dev/asana, add the Asana plugin, and connect with an API key or OAuth. Then call methods like corsair.asana.api.projects.addFollowers() from your app. Corsair verifies webhooks, stores tokens, and syncs data per tenant.

Yes. Asana supports an API key or OAuth. Use credentials or OAuth scopes that match what you automate. Create them in the Asana developer console, then paste into Corsair or connect through managed auth in Hub.

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

Teams use Corsair for work management platform for tasks, projects, teams, and cross-functional collaboration. Common builds include sync jobs, admin tooling, and agents that call Asana APIs from your backend. Webhook handlers react to Asana events and fan out to Slack, email, or other plugins in the same tenant. Local DB entities let you query synced Asana 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 Asana 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/asana in the open repo. When Asana 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 Asana data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Asana data on your behalf.