Get Pipeline: 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
Pipeline ID pipeline_id	string	Required	Pipeline ID. Example: abc-123-def

Sample request

{
  "pipeline_id": "e.g. abc-123-def"
}

Returns

{
  "id": "abc-123",
  "vcs": {
    "branch": "main"
  },
  "state": "created",
  "number": 42,
  "trigger": {
    "type": "webhook"
  }
}

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

FAQ

Questions about Get Pipeline.

What does the Get Pipeline action do in CircleCI?

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.

What inputs does Get Pipeline require?

Required: Pipeline ID. 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 Get Pipeline support batch operations?

Yes. Run Get Pipeline 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