CIRCLECI n8n INTEGRATION: AUTOMATE CIRCLECI WITH N8N

This action retrieves detailed information about a specific pipeline in your CircleCI project. It's essential for building workflows that need to check pipeline status, fetch configuration details, or gather metadata about specific builds before making decisions in your automation.

Key parameters:

• Credential to connect with: Select your CircleCI account credentials from the dropdown. This is required for authenticating with the CircleCI API.
• Provider: Choose the VCS provider (GitHub, Bitbucket) associated with your project. Required to specify the correct context for your request.
• Project Slug: Enter your project identifier in the format org-name/repo-name (e.g., my-company/backend-api). This required field tells CircleCI which project to query.
• Pipeline Number: Input the specific pipeline number you want to retrieve. This required numeric value identifies the exact pipeline instance.

Practical use cases:

• Fetch pipeline details after a webhook notification to determine if deployment should proceed
• Build a monitoring dashboard that displays real-time pipeline information
• Create conditional workflows that branch based on pipeline configuration or status
• Archive pipeline metadata to external databases for compliance tracking

This action programmatically initiates a new build pipeline in CircleCI. It's the cornerstone action for creating event-driven CI/CD workflows where external triggers—rather than code commits—need to start your build processes.

Key parameters:

• Credential to connect with: Select your authenticated CircleCI account from the dropdown menu. Required for API access.
• Provider: Specify your version control provider. Required to correctly identify your project's location.
• Project Slug: Enter your project identifier as org-name/repo-name. This required text field determines which project's pipeline to trigger.
• Additional Fields: Expand this optional section to specify branch names, pipeline parameters, or custom environment variables to pass to your build.

Practical use cases:

• Trigger deployment pipelines when a Slack command is received (e.g., /deploy production)
• Automatically start builds when issues are marked as "Ready for QA" in Jira
• Create scheduled pipelines using n8n's Cron node for nightly builds or periodic tasks
• Implement ChatOps workflows where team members can trigger specific pipelines through messaging platforms

💡 TIP: When using the "Additional Fields" section, you can pass dynamic parameters from earlier nodes in your workflow. This lets you create flexible deployments where the branch or environment is determined by the triggering event.

This action retrieves multiple pipeline records from a CircleCI project, perfect for building reporting workflows, monitoring dashboards, or batch processing scenarios where you need to analyze pipeline history.

Key parameters:

• Credential to connect with: Select your CircleCI credentials from the dropdown. Required for authentication.
• Provider: Choose your VCS provider from the dropdown. This may be optional depending on your setup.
• Project Slug: Enter your project in org-name/repo-name format. This required field specifies which project's pipelines to fetch.
• Return All: Toggle this on to retrieve all available pipelines without pagination limits. Useful for comprehensive reporting but may increase execution time.
• Limit: When "Return All" is off, this numeric field sets the maximum number of pipelines to return (default typically 100). Optional but recommended for performance.
• Filters: Add filtering criteria to narrow down results based on specific parameters like branch or status. Optional but powerful for targeted queries.

Practical use cases:

• Generate weekly CI/CD reports by fetching all pipelines and calculating success rates
• Build a Slack bot that responds with recent pipeline statuses for a project
• Create alerting workflows that check for failed pipelines and notify the team
• Sync pipeline history to analytics tools like BigQuery or Snowflake for trend analysis