Overview
The LinearEnhanced node for n8n allows you to interact with the Linear API, specifically to retrieve information about issues. The "Issue: Get" operation fetches detailed data for a specific issue in your Linear workspace by its Issue ID. This is useful for automating workflows that need to look up or process issue details, such as syncing issue data to other systems, generating reports, or triggering actions based on issue status.
Example scenarios:
- Fetching issue details to include in an automated notification.
- Retrieving issue data for further processing or integration with project management tools.
- Using issue information as part of a conditional workflow in n8n.
Properties
| Name | Meaning |
|---|---|
| Authentication | Selects the authentication method. Options: API Token |
| Issue ID | The unique identifier of the issue to retrieve. Required for "Get" and "Delete" actions. |
Output
The output is a JSON object containing all available fields for the specified issue from the Linear API. The structure typically includes (but is not limited to):
{
"id": "string",
"title": "string",
"description": "string",
"state": { /* state object */ },
"assignee": { /* user object */ },
"createdAt": "string",
"updatedAt": "string",
// ...other issue fields as provided by Linear
}
- The exact fields depend on the Linear API's response for an issue.
- If an error occurs and "Continue On Fail" is enabled, the output will be:
{
"error": "Error message"
}
Dependencies
- External Service: Requires access to the Linear API.
- API Key: You must provide a valid Linear API token via n8n credentials (
linearEnhancedApi). - n8n Configuration: No special environment variables are required beyond standard credential setup.
Troubleshooting
Common Issues:
Invalid API Token: If the API token is incorrect or expired, you may see an error like:
"The security token included in the request is invalid"- Resolution: Check and update your Linear API credentials in n8n.
Missing or Invalid Issue ID: If the Issue ID is missing or does not exist, the node may return an error from the Linear API.
- Resolution: Ensure the Issue ID is correct and exists in your Linear workspace.
Network/Connectivity Errors: If n8n cannot reach the Linear API, you may receive network-related errors.
- Resolution: Verify network connectivity and that the Linear API is accessible from your n8n instance.