Actions18
Overview
This node integrates with the Linear API to perform advanced operations on various Linear resources, including projects. Specifically, for the Project - Get operation, it retrieves detailed information about a single project by its unique ID. This is useful when you want to fetch up-to-date project data from Linear within an automated workflow.
Common scenarios include:
- Fetching project details to display or process in other systems.
- Using project metadata to trigger conditional logic in workflows.
- Synchronizing project information between Linear and other tools.
Example: You have a project ID and want to retrieve its name, description, status, and related metadata to update a dashboard or send notifications.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project to retrieve. This is required to specify which project’s details to fetch. |
Output
The node outputs JSON data representing the requested project object as returned by the Linear API. The structure typically includes fields such as:
id: The project’s unique identifier.name: The project’s name.description: A textual description of the project.state: Current state/status of the project.team: The team associated with the project.- Other metadata fields provided by Linear’s project schema.
The output is a single JSON object per input item containing all available project details. There is no binary data output for this operation.
Dependencies
- Requires an active connection to the Linear API via an API key credential configured in n8n.
- Uses the official Linear SDK (
@linear/sdk) internally to communicate with the API. - The node expects valid project IDs that exist in the connected Linear workspace.
Troubleshooting
- Invalid Project ID: If the provided project ID does not exist or is malformed, the node will throw an error indicating the project could not be found. Verify the ID is correct.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to access project data.
- API Rate Limits: Excessive requests may lead to rate limiting by Linear. Implement retry logic or reduce request frequency if needed.
- Network Issues: Connectivity problems can cause failures; check network access to Linear’s API endpoints.