Confluence

Install corsair and @corsair-dev/confluence, add the Confluence plugin, and connect with an API key or OAuth. Then call methods like corsair.confluence.api.pages.get() from your app. Corsair stores tokens, and keeps each tenant isolated.

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

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

Teams use Corsair for team wiki and documentation platform for knowledge bases and collaborative page editing. Common builds include sync jobs, admin tooling, and agents that call Confluence APIs from your backend.

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 Confluence 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/confluence in the open repo. When Confluence 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 Confluence data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Confluence data on your behalf.