List Pipelines: CircleCI action

Inputs

The fields this action accepts.

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

Field	Type	Required	Description
Project Slug project_slug	string	Required	Project Slug. Example: gh/acme-corp/my-project
Branch branch	string	Optional	Branch. 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.

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. Tiny Command handles CircleCI's rate limits automatically so you don't have to throttle manually.

More actions