Ashby

Install corsair and @corsair-dev/ashby, add the Ashby plugin, and connect with an API key. Then call methods like corsair.ashby.api.apiKey.info() from your app. Corsair verifies webhooks, and syncs data per tenant.

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

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