Developer Tools & DevOps
Connect CircleCI to Your AI Agents
Enable your Wkil agents to trigger pipelines, monitor workflow status, and investigate job failures through CircleCI.
Authentication: API key
What you can do
- Trigger and monitor CI/CD pipeline runs
- Investigate job failures and flaky tests
- Manage project environment variables and contexts
Available capabilities may vary by authentication and workspace configuration.
Actions supported by the connector
65 verified tools
Trigger Pipeline
Start a new CI/CD pipeline run.
Get Workflow Summary
Check the status summary of a workflow run.
Get Job Details
Retrieve details and logs for a specific job.
List Pipelines for Project
Retrieve recent pipeline runs for a project.
Get Flaky Tests
Identify tests that fail inconsistently across runs.
Get Job Artifacts
Retrieve build artifacts produced by a job.
List Project Environment Variables
Retrieve the environment variables configured for a project.
Create Project Environment Variable
Add a new environment variable to a project.
Get Project Workflows
Retrieve the workflows configured for a project.
List Self-Hosted Runners
Retrieve self-hosted runners registered to the organization.
View all verified tools (search)
Create ContextCreate Context (GraphQL)Create Context RestrictionCreate Organization Orb AllowlistCreate Organization ProjectCreate Organization GroupCreate Project Environment VariableCreate Usage Export JobDelete Context (GraphQL)Delete Context RestrictionDelete Namespace and Related OrbsDelete Namespace AliasDelete Organization Orb Allowlist EntryDelete Organization GroupDelete ProjectDelete Project Environment VariableGet ContextGet Current UserGet Flaky TestsGet Job ArtifactsGet Job DetailsGet Orb DetailsGet Orb VersionGet OrganizationGet Organization GroupGet Pipeline ConfigGet Pipeline DefinitionGet ProjectGet Project WorkflowsGet Test MetadataGet Usage Export JobGet User InformationGet Workflow SummaryList Context Environment VariablesList Insights BranchesList Insights SummaryList Namespace OrbsList Orb CategoriesList OrbsList Organization GroupsList Pages SummaryList Pipeline DefinitionsList PipelinesList Pipelines for ProjectList Project Environment VariablesList Project SchedulesList Self-Hosted RunnersList User CollaborationsList Workflows by Pipeline IDList Workflows Jobs WorkflowsList Workflows Test MetricsQuery ContextQuery Namespace ExistsQuery Orb Category IDQuery Orb ExistsQuery Orb IDQuery Orb Latest VersionQuery Orb SourceQuery Plan MetricsRemove Context Environment Variable (GraphQL)Rename NamespaceStore Environment VariableTrigger PipelineUpsert Context Environment VariableValidate Orb Config
Practical agent use cases
- An agent triggers a pipeline after a code change and reports back the workflow summary once it finishes.
How it works with Wkil
- 1Choose the integrationAdd CircleCI to your agent from inside the Wkil platform.
- 2Grant the permissions it needsDefine precisely what the agent can access and perform.
- 3Test, then run itTest actions before they go live, with human approval where needed.
Permissions always stay in your control — you can scope access and require human approval before any sensitive action.
FAQ
Can an agent debug a failed build?
An agent can pull job details, logs, and flaky-test data to help diagnose a failure, though fixing code still needs a human or a coding agent.

