Skip to content

Start building

Integration · Developer

AI agents for CircleCI

Trigger CircleCI pipelines on a branch with parameters, follow their workflows and jobs, and rerun a workflow, with a personal API token.

Actions
5
Read
3
Write
2

Actions

What your agents can do in CircleCI

5 actions. Each one is a tool your agents can call and a step your workflows can run.

Read 3

Look things up. Nothing changes.

  • Get a pipeline

    Reads one pipeline by its ID: number, state (created, errored, setup-pending, setup, pending), project slug, what triggered it, the branch, tag and commit, errors in setting it up.

  • List a pipeline's workflows

    Lists the workflows a pipeline ran, as items: each with its ID, name, status (running, success, failed, error, failing, on_hold, canceled, not_run …), and when it started and stopped.

  • List a workflow's jobs

    Lists the jobs in a workflow, as items: each with its ID, name, job number, type (build or approval), status.

Write 2

Create, change or send.

  • Trigger a pipeline

    Starts a pipeline for a project on a branch, with optional pipeline parameters (declared under parameters: in the project's config), using the project's pipeline definition.

  • Rerun a workflow

    Runs a workflow again as a new workflow: all of it, or from its failed jobs only with from_failed.

A person can approve first

Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

API key

Paste an API key from your CircleCI account.

What you enter

  • Personal API token

Kept safe

  • Credentials are stored encrypted with your organization's own keys.
  • They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
  • Calls go only to the tool's own servers.

How we protect your data

Ideas

Ideas to start with

Starting points made only from the actions above. Mix them with any other tool your agents can use.

  • 01

    Ask about your CircleCI data

    Ask a question in plain words. The agent can get a pipeline, list a pipeline's workflows or list a workflow's jobs in CircleCI, then answers with what it found.

  • 02

    Let an agent update CircleCI

    Have the agent trigger a pipeline in CircleCI as part of a larger task. Turn on approval and a person signs off on each change first.

  • 03

    Share what it finds in Slack

    Give one agent CircleCI and Slack: it can get a pipeline in CircleCI and post a summary to a Slack channel in the same run.

FAQ

CircleCI and MyDeepAgents

Can MyDeepAgents connect to CircleCI?

Yes. The CircleCI connector has 5 actions: 3 read and 2 make changes. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect CircleCI?

Paste an API key from your CircleCI account. You'll need: Personal API token. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.

Can an agent change data in CircleCI without asking?

Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs.

Can I use CircleCI in workflows as well as agents?

Yes. Every CircleCI action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put CircleCI to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.