Start free
ActionCircleCIUpdated June 2026

How do I list recent CircleCI pipelines?

Short answer: You can list pipelines in CircleCI by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the CircleCI List Pipelines action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this actionAll 4 CircleCI actions
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Project Slug
project_slug
stringRequiredProject Slug. Example: gh/acme-corp/my-project
Branch
branch
stringOptionalBranch. Example: main
Sample request
{
  "project_slug": "e.g. gh/acme-corp/my-project",
  "branch": "e.g. main"
}
Returns
{
  "items": [
    {
      "id": "abc-123",
      "state": "created",
      "number": 42,
      "created_at": "2025-01-15T12:00:00Z"
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Pipelines.

Any of these apps can fire this action as part of a workflow.

Gmail → CircleCI
1 Gmail triggers
Slack → CircleCI
13 Slack triggers
Google Sheets → CircleCI
2 Google Sheets triggers
HubSpot → CircleCI
18 HubSpot triggers
FAQ

Questions about List Pipelines.

What does the List Pipelines action do in CircleCI?
Returns paginated pipelines for a project with state and branch filters. Useful for "what shipped this week" reports and for CI-health monitoring workflows.
What inputs does List Pipelines require?
Required: Project Slug. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if CircleCI returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does List Pipelines support batch operations?
Yes. Run List Pipelines inside a Loop node to process arrays. TinyCommand handles CircleCI's rate limits automatically so you don't have to throttle manually.
More actions

Other CircleCI actions.

Action
Cancel Workflow
Stops an in-flight workflow. Useful for "downstream check failed, short-circuit the rest of the pipeline" cascading workflows or for emergency stop on accidental production deploys.
Action
Get Pipeline
Returns a pipeline by ID with its workflows, jobs, and current state. The standard lookup for workflows that triggered a pipeline and need to poll for completion before proceeding.
Action
Trigger Pipeline
Starts a CI run with optional branch and parameter overrides. Useful for "Linear issue moved to deploy → trigger production pipeline" or "rollback requested → trigger pipeline with deploy_version=X parameter" patterns.