CircleCI integration

CI/CD: pipelines, workflows, jobs, projects, contexts, environment variables

Help CentreConnectors

Overview

CircleCI is a hosted CI/CD platform. The Automize CircleCI connector covers pipeline triggering, status reads, projects, workflows, jobs, and contexts (shared env vars).

  • Regions: CircleCI Cloud is global (circleci.com). Server (self-hosted) versions use a different base URL.
  • Plans: Free, Performance, Scale – all expose the v2 REST API.

Setting up the connection

Auth type: Bearer Token.

  1. Sign in to CircleCI → User Settings → Personal API Tokens → Create New Token.
  2. Copy the token.
  3. In Automize, open Settings → Connectors → CircleCI → Add connection. Paste token.

Find your credentials at https://app.circleci.com/settings/user/tokens.


Rate limits

CircleCI enforces per-user limits. Pipeline triggers don't have hard caps beyond your plan's CI minute budget.


Data model

Project-centric:

    Project (Github/GitLab/Bitbucket repo) ─┬─ Pipelines (per-commit-or-trigger)
                                            │     └─ Workflows (parallel or sequential)
                                            │           └─ Jobs (actual builds/tests)
                                            └─ Contexts (named env-var bundles, shared across projects)

project_slug format: vcs-type/org/repo (e.g. gh/myorg/myrepo).

Available operations

8 operations available. Click any row to jump to its detail.

OperationCategoryWhat it does
Get PipelineGeneralGet pipeline details
Get ProjectGeneralGet project details
Get WorkflowGeneralGet workflow details
List ContextsGeneralList contexts for an organization
List JobsGeneralList jobs in a workflow
List PipelinesGeneralList recent pipelines for a project
List WorkflowsGeneralList workflows for a pipeline
Trigger PipelineGeneralTrigger a new pipeline

Operations

Get Pipeline

Get pipeline details

ParameterRequiredTypeDescription
Pipeline Id pipeline_idYestext

Tips

  • Returns pipeline + status (created, running, success, failed, errored, canceled).

Get Project

Get project details

ParameterRequiredTypeDescription
Project Slug project_slugYestext

Tips

  • Returns project settings + recent build counts.

Get Workflow

Get workflow details

ParameterRequiredTypeDescription
Workflow Id workflow_idYestext

Tips

  • Returns status + per-job status.

List Contexts

List contexts for an organization

No input parameters.

Tips

  • Contexts hold shared env vars. Returns context IDs + names.

List Jobs

List jobs in a workflow

ParameterRequiredTypeDescription
Workflow Id workflow_idYestext

Tips

  • Jobs in a workflow. Returns name, status, started_at, stopped_at.

List Pipelines

List recent pipelines for a project

ParameterRequiredTypeDescription
Project Slug project_slugYestext

Tips

  • project_slug: gh/myorg/myrepo. Returns recent pipelines.
  • Filter by branch.

List Workflows

List workflows for a pipeline

ParameterRequiredTypeDescription
Pipeline Id pipeline_idYestext

Tips

  • Workflows in a pipeline. Each pipeline can have 1+ workflows defined in .circleci/config.yml.

Trigger Pipeline

Trigger a new pipeline

ParameterRequiredTypeDescription
Project Slug project_slugYestext
Branch branchYestext
Tag tagYestext
Parameters parametersYestext

Tips

  • project_slug + branch (or tag) + optional parameters dict.
  • Returns pipeline_id – use to track status.

FAQ

How do I cancel a running pipeline?
Cancel Workflow (not exposed here) – cancel by workflow_id, which cancels all its in-flight jobs. Or cancel from CircleCI UI.
Why does Trigger Pipeline return 404?
Check project_slug format: vcs-type/org/repo. Common typo – using gh/ vs github/. Use gh/, bb/, or gitlab/.
Parameters – when?
Pass parameters: {deploy: 'production', region: 'us-east-1'} on Trigger Pipeline. Reference in .circleci/config.yml via parameters: section.

Related connectors

See it working on your own data

Everything documented here ships with the platform – try the document tools free, or go live in 7 days.