ActionCircleCIUpdated September 2026
How do I fetch CircleCI pipeline details?
Short answer: You can get pipeline in CircleCI by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the CircleCI Get Pipeline action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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.
Triggered by
Apps that pair well as the trigger for Get Pipeline.
Any of these apps can fire this action as part of a workflow.
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 run history shows the failed step with its input and the error message CircleCI returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Get Pipeline support batch operations?
Run Get Pipeline inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within CircleCI's rate limits.
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.
ActionList Pipelines
Returns paginated pipelines for a project with state and branch filters. Useful for "what shipped this week" reports and for CI-health monitoring workflows.
ActionTrigger 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.