--- title: "CircleCI Integration" description: "Trigger and inspect CircleCI pipelines, workflows, and jobs, and manage project environment variables from your flows over the CircleCI API v2." url: https://flowrunner.ai/integrations/circleci date_modified: 2026-08-01T02:40:32-07:00 --- # CircleCI [Developer Tools](https://flowrunner.ai/integrations/category/developer-infrastructure) Trigger and inspect CircleCI pipelines, workflows, and jobs, and manage project environment variables from your flows over the CircleCI API v2. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 21 actions · API key · available [CircleCI website](https://circleci.com/) · [Platform Documentation](https://circleci.com/docs/api/v2/) · Capability data verified 2026-08-12 1. Code merges to a release branch and a flow picks it up 2. Agent resolves the project slug and the branch to build 3. Agent calls Trigger Pipeline to start the test pipeline 4. Agent polls Get Pipeline Workflows until the build reaches a terminal state 5. Agent posts the build result and any failing tests to the deploys channel 6. An engineer approves the deploy pipeline before the agent triggers it against production ## What This Integration Enables FlowRunner agents use CircleCI to run CI/CD from inside a larger flow instead of from the dashboard. An agent can kick off a test or deploy pipeline when code merges or a form is submitted, poll pipeline, workflow, and job status to gate downstream steps on a green build, and cancel or rerun stuck or failed workflows. It can collect job artifacts and test metadata for reporting or notifications, and manage project environment variables and inspect checkout keys. What it does not do on its own is trigger the pipeline that ships to production. That trigger waits for the engineer who owns the release. ### Without FlowRunner **Manual triggering**: An engineer opens CircleCI and starts each build by hand **Dashboard polling**: Someone refreshes the pipeline page waiting for it to go green **Deploy by habit**: A production deploy fires with no explicit approval step ### With FlowRunner **Auto-triggered builds**: The agent starts the test pipeline when code merges **Gated on green**: The agent waits for the build result and gates the next step on it **Approved deploys**: The production deploy pipeline waits for an engineer to approve ## Use Case Scenarios ### Merge-to-build with a production deploy gate Code merges to a release branch. The agent calls Trigger Pipeline to start the test pipeline, then polls Get Pipeline Workflows until it finishes. On green, it does not deploy. It posts the result to the deploys channel and asks an engineer to approve the production deploy. Only after the approval does the agent trigger the deploy pipeline. Tests run automatically; the ship stays a decision. ### Failure to a page The agent watches a running pipeline with Get Pipeline Workflows. When a workflow reaches a failed state, it opens an incident in the on-call tool with the failing workflow details and posts a link to the run. A broken build reaches the on-call engineer through the channels they already watch. ### Test summaries after every run After a pipeline finishes, the agent calls Get Test Metadata and Get Job Artifacts to pull the test results and build output, then posts a summary of failing tests and the artifact links to the team channel. The team sees what changed without opening the dashboard. ## Human-in-Loop Highlight The human-in-loop moment in CircleCI is the production deploy gate. Triggering test pipelines, polling status, and rerunning failed workflows are all safe to automate, so the agent runs them by rule. Triggering a pipeline that deploys to production is not, so the agent stops. When a build is green and a deploy is on the table, the agent posts the pipeline result to the deploys channel and asks: "app pipeline #914 is green on release/2.7. Trigger the production deploy?" A named engineer approves. Only then does the agent call Trigger Pipeline against the deploy workflow. The agent runs CI on its own. A person owns the deploy to production. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 21 actions ### Pipelines 7 - **Trigger Pipeline** Start a pipeline on a project. Used to kick off a build or deploy when code merges. Run it behind a human gate when it deploys to production. - **Get Pipeline** Retrieve a pipeline by ID. - **Get Pipeline by Number** Retrieve a pipeline by its per-project number. - **List Project Pipelines** List the pipelines for a project. - **List My Pipelines** List the pipelines triggered by the authenticated user. - **Get Pipeline Config** Retrieve the compiled and source configuration for a pipeline. - **Get Pipeline Workflows** List the workflows in a pipeline and their status. Used to gate a step on a green build. ### Workflows 4 - **Get Workflow** Retrieve a single workflow by ID. - **Get Workflow Jobs** List the jobs in a workflow and their status. - **Cancel Workflow** Cancel a running workflow. - **Rerun Workflow** Rerun a workflow from the start or from its failed jobs. ### Jobs 4 - **Get Job Details** Retrieve a job's details within a project. - **Cancel Job** Cancel a running job. - **Get Job Artifacts** List the artifacts a job produced, with download URLs. - **Get Test Metadata** Retrieve the test results recorded for a job. ### Project 5 - **Get Project** Retrieve a project by slug. - **List Env Vars** List a project's environment variables. Values are masked to the last four characters. - **Create Env Var** Set a project environment variable. - **Delete Env Var** Delete a project environment variable. - **List Checkout Keys** List a project's checkout keys. ### Account 1 - **Get Current User** Retrieve the authenticated user. Used as a connection check. ## Frequently Asked Questions ### What can FlowRunner do with CircleCI? FlowRunner agents can run Trigger Pipeline, Get Pipeline, and Get Pipeline by Number in CircleCI, plus 18 more actions. ### Does connecting CircleCI to FlowRunner require OAuth? No. CircleCI connects to FlowRunner with an API key, no OAuth flow required. ### Can CircleCI trigger a FlowRunner workflow automatically? CircleCI doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at CircleCI?** This integration exposes CircleCI to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/circleci. Site index: https://flowrunner.ai/llms.txt