← All integrations

CircleCI

65 operations0 webhooks

Continuous integration and delivery platform for automated testing and deployment pipelines.

Supported operations

  • CreateWrite

    Create a context (REST)

  • Create RestrictionWrite

    Add a restriction to a context

  • Delete RestrictionDestructive

    Remove a restriction from a context

  • GetRead-only

    Retrieve a context by id

  • List Env VarsRead-only

    List a context's environment variables

  • Upsert Env VarWrite

    Add or update a context environment variable (REST)

FAQ

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

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

Teams use Corsair for continuous integration and delivery platform for automated testing and deployment pipelines. Common builds include sync jobs, admin tooling, and agents that call CircleCI APIs from your backend. Local DB entities let you query synced CircleCI 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 CircleCI 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/circleci in the open repo. When CircleCI 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 CircleCI data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store CircleCI data on your behalf.