Actions18
Overview
The node "Linear Advanced" provides an enhanced integration with the Linear API, allowing users to perform various operations on Linear resources such as issues, members, teams, labels, projects, and comments. Specifically for the JSON Request - Execute operation, it enables executing any supported resource-operation combination by passing a JSON object that specifies the resource, operation, and parameters dynamically.
This flexibility is beneficial when you want to programmatically control which Linear API actions to perform without configuring each operation separately in the node UI. For example, you can create an issue, update a project, or get many members by specifying the appropriate JSON payload.
Practical examples:
- Creating an issue by providing team ID, title, and description in JSON.
- Retrieving details of a specific member by member ID.
- Fetching multiple projects filtered by team ID with pagination options.
Properties
| Name | Meaning |
|---|---|
| JSON Parameters | A JSON object containing the resource, operation, and parameters to execute. The structure must include: - resource: The Linear resource to operate on (e.g., "issue", "member", "team", "label", "project").- operation: The action to perform on the resource (e.g., "create", "get", "getMany", "update").- parameters: An object with the necessary parameters for the specified operation.Example: json { "resource": "issue", "operation": "create", "parameters": { "teamId": "TEAM_ID", "title": "Issue Title", "description": "Issue Description" } } |
Output
The output is an array of items where each item contains a json field representing the result of the executed operation. The structure of the json output depends on the resource and operation performed:
- For create operations, the output includes the newly created resource's data.
- For get operations, the output includes the requested resource's details.
- For getMany operations, multiple items are outputted, each representing one resource instance.
- For update operations, the output includes the updated resource's data.
- For addLabel operation on issues, the output confirms success and echoes the issue and label IDs.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Linear API.
- Uses the official Linear SDK (
@linear/sdk) to interact with the Linear API. - Requires proper configuration of the API key credential in n8n to authorize requests.
Troubleshooting
- Invalid JSON parameters error: If the JSON provided in the "JSON Parameters" property is malformed or not valid JSON, the node will throw an error. Ensure the JSON syntax is correct.
- Missing required fields: Errors occur if mandatory fields like
resource,operation, or required parameters (e.g.,teamIdfor creating an issue) are missing in the JSON. Verify all required fields are included. - Unsupported resource or operation: If the resource or operation specified in the JSON is not supported by the node, an error will be thrown indicating the unsupported action.
- API authentication errors: If the API key credential is invalid or missing, the node will fail to authenticate with the Linear API. Check the credential setup.
- Operation temporarily unavailable: For example, the "addComment" operation on issues is currently disabled and will throw an error instructing to use a different operation.
To resolve these issues:
- Validate your JSON input carefully.
- Confirm all required parameters for the chosen resource-operation are present.
- Ensure your API key credential is correctly configured and has sufficient permissions.
- Refer to the error messages for guidance on what is missing or unsupported.
Links and References
- Linear API Documentation
- Linear SDK on npm
- n8n Documentation on Credentials
- Example JSON structure for the JSON Parameters property (from node default):
{
"resource": "issue",
"operation": "create",
"parameters": {
"teamId": "TEAM_ID",
"title": "Issue Title",
"description": "Issue Description"
}
}