Actions18
Overview
The node provides advanced integration with the Linear API, specifically enabling operations on various Linear resources such as issues, members, teams, labels, projects, and comments. For the Issue - Get operation, it retrieves detailed information about a specific issue by its ID.
This operation is useful when you want to fetch the current state, details, or metadata of an existing issue in Linear. For example, you might use this node to:
- Retrieve issue details for reporting or display in dashboards.
- Fetch issue data before updating or adding comments.
- Integrate issue information into other workflows or systems.
Properties
| Name | Meaning |
|---|---|
| Issue ID | The unique identifier of the issue to retrieve. This is required to specify which issue to get. |
Output
The output is a JSON object representing the retrieved issue's full details as returned by the Linear API. It includes all standard fields of an issue such as title, description, status, assignee, labels, priority, creation date, and any other metadata associated with the issue.
Example structure (simplified):
{
"id": "string",
"title": "string",
"description": "string",
"stateId": "string",
"assigneeId": "string",
"priority": number,
"labelIds": ["string"],
"teamId": "string",
"createdAt": "string",
"updatedAt": "string",
...
}
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the Linear API.
- Uses the official Linear SDK client internally to communicate with the Linear service.
- The node expects proper configuration of the Linear API credentials within n8n.
Troubleshooting
- Missing or invalid Issue ID: If the provided Issue ID is empty or incorrect, the node will fail to retrieve the issue. Ensure the Issue ID is valid and corresponds to an existing issue in your Linear workspace.
- Authentication errors: If the API key credential is missing, invalid, or lacks permissions, the node will throw authentication errors. Verify that the API key is correctly configured and has access rights.
- Network or API errors: Temporary network issues or API rate limits may cause failures. Check connectivity and consider retrying later.
- Error messages: The node throws descriptive error messages if required parameters are missing or if the API returns errors. Review the error message for guidance on fixing input parameters or credentials.