Appearance
Linear
Streamlined issue tracking and project management with the Linear API.
| Detail | Value |
|---|---|
| Category | Project Management |
| Base URL | https://api.linear.app |
| Authentication | Bearer Token |
| Endpoints | 5 |
| Connector key | linear |
Using Linear in a workflow
- Go to Connections and click New Connection.
- Pick Linear from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
POST /graphql | Query issues via GraphQL |
POST /graphql | Create an issue via GraphQL mutation |
POST /graphql | Update an issue via GraphQL mutation |
POST /graphql | List projects via GraphQL |
POST /graphql | List teams via GraphQL |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
POST /graphql
Query issues via GraphQL
| Detail | Value |
|---|---|
| Operation ID | pm.queryIssues |
| Method | POST |
| Path | /graphql |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
query | string |
variables | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Linear connection from the Connection dropdown.
- In the Operation dropdown, select
pm.queryIssues. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
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 {{nodeId.data.path}}. The exact response shape is documented on the upstream Linear API reference.
POST /graphql
Create an issue via GraphQL mutation
| Detail | Value |
|---|---|
| Operation ID | pm.createIssue |
| Method | POST |
| Path | /graphql |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
query | string |
variables | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Linear connection from the Connection dropdown.
- In the Operation dropdown, select
pm.createIssue. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
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 {{nodeId.data.path}}. The exact response shape is documented on the upstream Linear API reference.
POST /graphql
Update an issue via GraphQL mutation
| Detail | Value |
|---|---|
| Operation ID | pm.updateIssue |
| Method | POST |
| Path | /graphql |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
query | string |
variables | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Linear connection from the Connection dropdown.
- In the Operation dropdown, select
pm.updateIssue. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
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 {{nodeId.data.path}}. The exact response shape is documented on the upstream Linear API reference.
POST /graphql
List projects via GraphQL
| Detail | Value |
|---|---|
| Operation ID | pm.listProjects |
| Method | POST |
| Path | /graphql |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
query | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Linear connection from the Connection dropdown.
- In the Operation dropdown, select
pm.listProjects. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
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 {{nodeId.data.path}}. The exact response shape is documented on the upstream Linear API reference.
POST /graphql
List teams via GraphQL
| Detail | Value |
|---|---|
| Operation ID | pm.listTeams |
| Method | POST |
| Path | /graphql |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
query | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Linear connection from the Connection dropdown.
- In the Operation dropdown, select
pm.listTeams. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
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 {{nodeId.data.path}}. The exact response shape is documented on the upstream Linear API reference.