Actions18
Overview
This node integrates with the Linear API to manage issues within a Linear workspace. Specifically, the "Issue - Create" operation allows users to create new issues in a specified team. This is useful for automating issue tracking workflows, such as creating bug reports, feature requests, or task items directly from other systems or triggers.
Practical examples include:
- Automatically creating an issue when a customer support ticket is received.
- Generating tasks in Linear from form submissions or monitoring alerts.
- Creating issues programmatically during CI/CD pipelines for failed builds or deployments.
Properties
| Name | Meaning |
|---|---|
| Team ID | The unique identifier of the team where the issue will be created. |
| Title | The title or summary of the issue. |
| Description | A detailed description of the issue, supporting markdown formatting. |
| Additional Fields | Optional extra fields to specify more details about the issue: |
| - Priority | The priority level of the issue. Options: Urgent (1), High (2), Normal (3), Low (4). |
| - State ID | The ID of the workflow state to assign the issue to. |
| - Assignee ID | The ID of the user to whom the issue should be assigned. |
| - Label IDs | Comma-separated list of label IDs to tag the issue with. |
Output
The output is an array of JSON objects, each representing the newly created issue. Each object contains all the properties of the created issue as returned by the Linear API, including but not limited to:
- Issue ID
- Title
- Description
- Priority
- State information
- Assignee details
- Labels assigned
- Creation and update timestamps
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Linear API.
- Uses the official
@linear/sdkpackage to interact with the Linear service. - The node expects proper configuration of the Linear API credentials within n8n.
Troubleshooting
- Missing Required Fields: If "Team ID" or "Title" are not provided, the node will throw an error indicating these are required.
- Invalid Label IDs Format: Label IDs must be provided as a comma-separated string; incorrect formatting may cause issues.
- API Authentication Errors: Ensure that the API key credential is valid and has sufficient permissions to create issues.
- Network or API Downtime: Temporary failures connecting to the Linear API can cause errors; retrying later may help.
- Operation Not Available: Some operations like adding comments are currently disabled and will throw explicit errors if attempted.