---
title: 'GET /pipeline/{pipeline-id}'
description: 'Get pipeline details'
---

# GET /pipeline/{pipeline-id}

Get pipeline details

| Detail | Value |
|---|---|
| Operation ID | `cicd.getPipeline` |
| Method | `GET` |
| Path | `/pipeline/{pipeline-id}` |
| Connector | [CircleCI](./) |

## Parameters

_No parameters._

## Using this endpoint in a workflow

1. Add an **API Call** node to your workflow.
2. Pick your CircleCI connection from the Connection dropdown.
3. In the Operation dropdown, select `cicd.getPipeline`.
4. Fill in the parameter fields that appear. Use `{{...}}` to reference upstream values.

## What it returns

The `API Call` node writes the response to the workflow context:

```
{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}
```

Reference response fields downstream as <code v-pre>{{nodeId.data.path}}</code>. The exact response shape is documented on the upstream CircleCI API reference.