Resources · n8n integration

CircleCI n8n integrationAutomate CircleCI with n8n.

Want your builds to start themselves and report back? The CircleCI n8n integration carries 3 operations, all on one Pipeline resource: read a pipeline, list many, start a new one. CircleCI has no trigger node, so the workflow opens with a Schedule Trigger, a Webhook, or another tool's trigger.

Try the CircleCI integration on n8nSee the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the CircleCI n8n integration actually give you?

The CircleCI n8n integration puts your pipelines on the same canvas as the rest of your tooling. n8n ships a CircleCI node with 3 operations, all of them on the Pipeline resource, authenticated by a Personal API Token stored once as a credential. From any workflow you can look a pipeline up, pull back a list of them, or kick a new one off, then send the result wherever it needs to go.

Start with the smallest one. A workflow already knows a pipeline number, maybe because it just started that pipeline itself, and it needs the pipeline's own record from CircleCI rather than a guess. pipeline.get fetches that single pipeline, and the rest of the branch decides what to do with it: post the outcome into a Slack channel, or hold a release step until the record is in hand.

The listing operation covers the reporting side. Point pipeline.getAll at a project, set Branch under Filters to the branch you actually care about, turn Return All on so n8n walks every page of results instead of stopping at Limit, and you have a full run of pipelines in one node. A Schedule Trigger every morning plus a write into Google Sheets gives the team a build log that nobody has to assemble by hand.

Then the one that moves things. pipeline.trigger starts a pipeline on demand, with Branch or Tag under Additional Fields deciding what gets built. That turns a deploy into a workflow step: an internal form, an approval in Slack, or an event coming from GitHub can all end in a pipeline that runs without anyone opening the CircleCI UI.

Anything the CircleCI API does beyond these 3 operations is still reachable from n8n. The HTTP Request node calls any endpoint of the CircleCI API and reuses the same credential through predefined authentication, so a workflow can mix the dedicated node for the common path with one raw call for the rest.

One structural point to plan around: there is no CircleCI trigger node, so nothing here listens on its own. Every workflow in this section starts somewhere else, then reaches CircleCI. Our n8n review goes into how that shapes a build around a tool with actions but no events.

Connect

How do you connect CircleCI to n8n?

  1. 01

    Create the CircleCI account side first

    You need a CircleCI account and a Personal API Token, which is the only authentication method the CircleCI credential in n8n accepts. The token is created from your CircleCI user settings, following CircleCI's own instructions for creating a personal API token. Copy it at the moment it is shown: a token you cannot read back is a token you have to replace.

  2. 02

    Store the token as a credential in n8n

    In n8n, open the Credentials menu and create a CircleCI credential, which is the saved login n8n reuses on your behalf. Paste the Personal API Token into its field and save. The credential exists once and is offered in the dropdown of every CircleCI node you add afterwards, on n8n Cloud or on a self-hosted instance, with no difference in how the workflow behaves.

  3. 03

    Point the node at a real project

    Add the CircleCI node, pick the credential, then set Provider to the source control system the project lives on, GitHub or Bitbucket. Project Slug takes the project written as org-name/repo-name, exactly the shape of the n8n-io/n8n placeholder shown in the field. Run pipeline.getAll once with a small Limit to confirm the pairing before you build anything on top.

Actions

What can the CircleCI node do?

The CircleCI node exposes 3 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceGetGet ManyTrigger
Pipeline✓✓✓

Pipeline

3 operations
01

Get a pipeline

pipeline.get

What you see in n8n

Notes & use cases

Returns one specific pipeline from CircleCI, the one identified by its number on a given project, so a workflow can read its record rather than assume anything.

Key parameters

  • Provider: the source control system behind the project, github or bitbucket.
  • Project Slug: the project as org-name/repo-name, matching the n8n-io/n8n placeholder.
  • Pipeline Number: the number of the pipeline you want, usually pulled in with an expression from an earlier node's output rather than typed by hand.
Use cases
a release workflow that starts a pipeline, waits, then reads that exact pipeline back before it announces anything to the rest of the team.
02

Get many pipelines

pipeline.getAll

What you see in n8n

Notes & use cases

Brings back a set of pipelines for a project instead of a single one, which is what you want whenever the question is about a period rather than a run.

Key parameters

  • Project Slug: the project in org-name/repo-name form, with Provider set to GitHub or Bitbucket.
  • Return All: on, n8n follows the API pages until every pipeline is collected; off, Limit caps how many come back.
  • Branch, under Filters: narrows the list to one vcs branch, so a main-only report stays main-only.
Use cases
a weekly summary of pipelines per branch, exported as rows for whoever tracks build activity.
03

Trigger a pipeline

pipeline.trigger

What you see in n8n

Notes & use cases

Starts a new pipeline on the project you name. CircleCI becomes something a workflow does. Nobody has to remember the button on a Friday afternoon.

Key parameters

  • Project Slug: the project, in org-name/repo-name form.
  • Branch, under Additional Fields: the branch to build, whose HEAD commit is used for the pipeline.
  • Tag, under Additional Fields: the tag to build instead, pointing at the commit used. Branch and tag are mutually exclusive, so send one or the other, never both.
Use cases
a deploy request submitted in an internal form that ends as a tagged pipeline, with no console access handed out.
Need help

Need help automating CircleCI with n8n?

A person reads every message.

FAQ

CircleCI and n8n, answered

01Is the CircleCI n8n integration free to use?
Yes on the n8n side. The CircleCI node ships with n8n, so there is nothing to install and nothing extra to pay for the node itself, whether you run n8n Cloud or a self-hosted instance under the Community Edition and its Sustainable Use licence. A workflow built on one runs identically on the other, which matters if you prototype on Cloud and move to your own server later. What a CircleCI account itself costs is between you and CircleCI, and this page does not speak for their pricing. Budget the n8n side as included, and the CircleCI side as whatever plan you already hold.
02What credentials do you need to connect CircleCI to n8n?
One thing: a Personal API Token. That is the single supported authentication method for the CircleCI credential in n8n, and it assumes you already have a CircleCI account. You generate the token from CircleCI, following their documentation on creating a personal API token, then paste it into a CircleCI credential in the n8n Credentials menu. From then on the credential is reusable, so every CircleCI node in every workflow picks it from a dropdown instead of holding its own copy of the secret. Rotating the token later means editing one credential rather than hunting through workflows.
03What are the limits of the CircleCI node in n8n?
Two things to know. First, listing is paginated: Get many pipelines returns everything only when Return All is on, otherwise Limit fixes how many items come back, which is a setting to check whenever a report looks shorter than reality. Second, the node covers 3 operations, all on the Pipeline resource. Anything else in the CircleCI API is reached from the HTTP Request node, which calls any endpoint and reuses the same credential through predefined authentication. In practice you build the common path with the dedicated node and drop to HTTP Request for the one call the catalogue does not list.
04Can n8n react to a CircleCI build in real time?
Not on its own, because CircleCI has no trigger node in n8n. A workflow that involves CircleCI always starts from another entry point: a Schedule Trigger firing on a fixed interval, an n8n Webhook, meaning a URL that an outside service calls, or the trigger of another tool you already use. The usual pattern for build awareness is a Schedule Trigger plus Get many pipelines, comparing what comes back against what you saw last time. The usual pattern for acting on a code event is a webhook from your source control that ends in Trigger a pipeline.
05n8n or Make for automating CircleCI?
It depends on where you want the workflow to live. Make is hosted by Make, with no self-hosting option, and billed per operation, so cost tracks volume and your data passes through their platform. n8n runs on n8n Cloud or on your own server through Docker or npm, which is the deciding factor for teams whose build tooling and secrets have to stay inside their own infrastructure. Both give you a visual canvas. Choose on hosting, data control, and how your cost should scale, not on which logo looks friendlier in a comparison table.
Same platform

Other docs you might need on this stack.

Browse all integrations