CircleCI

Nullify can recognize CircleCI build statuses reported to GitHub on its fix pull requests. This relies on an existing GitHub connection and CircleCI publishing commit statuses with the build URL.

CircleCI is not currently enabled in the shared connector catalog, and the general autofix workflow has no CircleCI failed-build log fetcher. Do not assume storing a token enables the log-driven iteration available for Buildkite or Jenkins. Confirm any tenant-specific rollout with Nullify before provisioning credentials.

Existing credential configuration

The Admin API retains these operations for existing setups:

Operation	Effect
GET /admin/integrations/circleci	Reports whether a token has been configured.
POST /admin/integrations/circleci/token	Stores or replaces an apiToken.
DELETE /admin/integrations/circleci	Removes the stored token.

A configured: true response confirms storage, not successful API access, build-log ingestion, or a working autofix feedback loop. The token is stored encrypted and is not returned by the status endpoint. If Nullify has enabled a supported use for your tenant, use a dedicated account and verify that workflow before revoking an old token during rotation.

Removing the token does not change your CircleCI pipelines or disconnect GitHub. GitHub can continue receiving and displaying CircleCI statuses independently of this stored credential.