All integrationsCode Repositories

CircleCI

Trigger CircleCI pipeline runs on any branch or tag with parameters, watch runs, workflows and jobs through to their outcome, cancel or rerun workflows, collect job artifacts, and manage the environment variables in projects and contexts.

actions
20

Actions

Steps a workflow can run in CircleCI.

  • List organizationsList the CircleCI organizations you belong to, or find one by its slug (such as gh/acme). Returns each organization's id, name and version-control provider.
  • List projectsList an organization's CircleCI projects, the projects you follow, or find one project by its slug (such as gh/acme/api). Narrow an organization's projects by name and sort by name or recent activity.
  • List pipelinesList a project's pipelines - the configurations it builds from - with each one's name, repository and config file path.
  • Get pipelineGet one pipeline: its name, description, the repository it checks out and where its config file is read from.
  • Trigger pipeline runStart a new run of a project's pipeline on a branch or tag, optionally with pipeline parameters. The config is read from the same branch or tag unless you name another. Returns the new run's id to watch with Get pipeline run or List workflows.
  • List pipeline runsList a project's recent pipeline runs, or your own recent runs across every project, newest first. Each run includes its outcome, branch, commit, and its workflows with their jobs.
  • Get pipeline runGet one pipeline run: its phase (queued, started, ended), current outcome, any errors, what triggered it and the commit it built.
  • List workflowsList the workflows of a pipeline run, with each one's phase and outcome.
  • Get workflowGet one workflow's phase and outcome - for example to wait until it has finished.
  • Cancel workflowCancel a running workflow. CircleCI cancels it in the background, so check it with Get workflow afterwards.
  • Rerun workflowRerun a finished workflow as a new workflow: every job, only the failed jobs and what depends on them, or jobs you choose. Optionally with SSH enabled for debugging. Returns the new workflow's id.
  • List jobsList the jobs of a workflow with each one's number, type, phase, outcome and timings.
  • Get jobGet one job with every step it ran - each step's command, outcome, exit code and timings - to see where a build failed.
  • List job artifactsList the files a job stored as artifacts - test reports, coverage, build outputs - with a download URL for each.
  • List project environment variablesList the names of a project's environment variables. CircleCI only ever shows the values masked.
  • Set project environment variableAdd an environment variable to a project, for its builds to read - for example to rotate a deploy token.
  • Delete project environment variableRemove an environment variable from a project by name.
  • List contextsList an organization's contexts - the shared sets of environment variables jobs can use - optionally narrowed by part of a name.
  • Set context environment variableCreate or replace an environment variable in a context, so every job using that context gets the new value.
  • Delete context environment variableRemove an environment variable from a context by name.

Automate CircleCI with Lodol.

Connect CircleCI and ask your AI for your first workflow.

Free plan, no credit card