LinkedIn

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

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

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

Teams use Corsair for professional network for profiles, company pages, posts, and b2b social marketing. Common builds include sync jobs, admin tooling, and agents that call LinkedIn APIs from your backend. Local DB entities let you query synced LinkedIn 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 LinkedIn 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/linkedin in the open repo. When LinkedIn 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 LinkedIn data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store LinkedIn data on your behalf.