DocumentationWorkflowsHTTP and developer tools
Linear node
Create, list, and update Linear issues right from your workflow, via Linear's official GraphQL API (one endpoint for everything). Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
8 min readUpdated
What this node does
Create, list, and update Linear issues right from your workflow, via Linear's official GraphQL API (one endpoint for everything).
Use Linear as a clearly defined step in an anymize workflow.
- Processes one input.
- Provides one output for following steps.
- Runs as a regular step in the flow.
Set up the node
- 01Open a workflow and add Linear from the node catalog.
- 02Complete the required fields and map values from previous steps.
- 03Run the node with a small test record and inspect its output.
- 04Connect the successful output and activate the workflow after an end-to-end test.
Operations and modes
Choose the required function in Action. The panel then shows the relevant settings.
- Create issue
- List issues
- Update issue
Settings
| Field | Meaning | Area |
|---|---|---|
| Linear API key | References only the name of the workflow secret, the key itself is resolved securely at runtime. Create the key under Linear → Settings → Security & access → Personal API keys. | Protected |
| Action | Choices: Create issue, List issues, Update issue | Standard |
| Team ID | The Linear team ID (UUID). Optional filter for "List issues", required for "Create issue". | Standard |
| Title | Title of the issue. | Standard |
| Description | Optional description (Markdown supported). | Standard |
| Max count | How many issues to load at most (default 50, max 250). | Standard |
| Issue ID | The ID or identifier (e.g. ENG-123) of the issue to update. | Standard |
| Title | Title of the issue. | Standard |
| Description | Optional description (Markdown supported). | Standard |
| State ID | Optional, the ID of the new issue state (workflow state). Leaves the state unchanged if empty. | Standard |
| Run once per item | Off (default): the node runs once for the whole input. On: if it receives several items (e.g. from Split Out), it runs once PER item, and {{ $json }} is that one item each time. This is how you work through a file list entry by entry. | Standard |
| If one item fails | "Skip" writes an `error` field for the failed item and keeps processing the rest, instead of losing the whole run to a single unreadable file. | Standard |
| Pause between items (milliseconds) | Wait before every run except the first. 1000 = 1 second per item. Useful when the other side would otherwise throttle you. Maximum 300000 (5 minutes). | Standard |
Inputs and outputs
| Input | Meaning | Type |
|---|---|---|
| Standard | Receives the complete result from the previous step. | JSON |
| Output | Meaning | Type |
|---|---|---|
| Standard | Makes the result available to the next step as JSON. | JSON |
This node can process lists item by item. Error handling and the delay between items are available in advanced settings.
Example and test run
Create a bug report as a Linear issue: begin with a small, recognizable record. Inspect the output and only map fields that are present there.
Test-run example
{
"action": "create_issue",
"team_id": "team-eng",
"title": "Checkout wirft 500 bei Rabattcode",
"description": "Reproduziert mit Code SUMMER10 im Staging. Stacktrace im Anhang."
}Access and security
Before activation, review which data enters this step and what its output contains.
Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.
Troubleshooting
- No output: inspect the latest run and confirm that the previous node returned the expected fields.
- Empty variable: open the previous step output and use a field name from the real test data.
- List processed once: enable per-item execution in advanced settings.