Actions18
Overview
The node provides advanced integration with the Linear API, specifically enabling operations on various Linear resources such as issues, members, teams, comments, labels, and projects. For the Issue resource with the Get Many operation, it retrieves multiple issues from Linear based on optional filters like team ID, assignee ID, and state ID. Users can choose to return all matching issues or limit the number of results.
This node is beneficial for workflows that need to bulk fetch issue data from Linear for reporting, synchronization, or automation purposes. For example, a user might want to retrieve all open issues assigned to a specific team or user to generate a status report or trigger follow-up actions.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching issues or only up to a specified limit |
| Limit | Maximum number of issues to return when "Return All" is false (minimum 1, maximum 100) |
| Filters | Collection of optional filters to narrow down the issues: |
| Team ID | Filter issues by a specific team ID |
| Assignee ID | Filter issues assigned to a specific user ID |
| State ID | Filter issues by a specific workflow state ID |
Output
The output consists of an array of JSON objects, each representing an individual issue retrieved from Linear. Each issue object contains detailed information about the issue, including but not limited to its ID, title, description, priority, state, assignee, labels, and associated team.
No binary data is output by this operation.
Example output item structure (simplified):
{
"id": "string",
"title": "string",
"description": "string",
"priority": 1,
"stateId": "string",
"assigneeId": "string",
"labelIds": ["string"],
"teamId": "string",
...
}
Dependencies
- Requires an API key credential for authenticating with the Linear API.
- The node uses the official Linear SDK (
@linear/sdk) to interact with the Linear API. - Proper configuration of the Linear API credentials in n8n is necessary before using this node.
Troubleshooting
Common Issues:
- Missing or invalid API key credential will cause authentication failures.
- Providing invalid filter IDs (e.g., non-existent team or assignee IDs) may result in empty results or errors.
- Exceeding the maximum allowed limit (over 100) will be rejected by the node's input validation.
Error Messages:
"The operation "getMany" is not supported for resource "issue" via JSON parameters."
This indicates misuse of JSON parameters for unsupported operations; ensure correct operation names."Invalid JSON parameters. Please provide valid JSON."
Occurs if JSON input is malformed; verify JSON syntax.- Network or API errors from Linear will propagate as node errors; check API availability and credentials.
To handle errors gracefully, enable the node's "Continue On Fail" option to process subsequent items even if some fail.