Zendesk

Install corsair and @corsair-dev/zendesk, add the Zendesk plugin, and connect with an API key. Then call methods like corsair.zendesk.api.comments.list() from your app. Corsair syncs data per tenant.

Yes. Zendesk requires an API key from your Zendesk 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 Zendesk, GitHub, Notion, Stripe, and the rest. Trigger Zendesk from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for customer support platform for tickets, help centers, chat, and service team workflows. Common builds include sync jobs, admin tooling, and agents that call Zendesk APIs from your backend. Local DB entities let you query synced Zendesk 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 Zendesk 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/zendesk in the open repo. When Zendesk 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 Zendesk data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Zendesk data on your behalf.