Actions18
Overview
The node provides advanced integration with the Linear API, specifically enabling retrieval of multiple projects ("Get Many" operation on the "Project" resource). It allows users to fetch a list of projects from their Linear workspace, optionally filtered by team ID, and control how many results are returned.
This node is beneficial in scenarios where you want to automate workflows involving project management data from Linear, such as syncing project lists to other tools, generating reports, or triggering actions based on project attributes.
For example, you can use this node to:
- Retrieve all projects for a specific team to display in a dashboard.
- Fetch a limited number of recent projects for quick processing.
- Filter projects by team to segment data according to organizational structure.
Properties
| Name | Meaning |
|---|---|
| Return All | Boolean flag indicating whether to return all matching projects or limit the number. |
| Limit | Maximum number of projects to return if "Return All" is false (minimum 1, maximum 100). |
| Filters | Collection of filters to narrow down the projects: |
| Team ID | Filter projects by the specified team ID. |
Output
The output consists of an array of JSON objects, each representing a project retrieved from Linear. Each project object contains the project's details as provided by the Linear API, such as its ID, name, description, and associated team information.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Linear API.
- The node uses the official Linear SDK client internally to communicate with the Linear service.
- Proper configuration of the API key credential in n8n is necessary for successful execution.
Troubleshooting
Common Issues:
- Invalid or missing API key credential will cause authentication failures.
- Providing an invalid team ID filter may result in no projects being returned.
- Requesting more than 100 projects without setting "Return All" to true will only return up to 100 due to the enforced limit.
Error Messages:
- Errors thrown by the Linear API (e.g., permission denied, not found) will be surfaced as node errors.
- If the node encounters unexpected input or API response issues, it throws descriptive errors indicating the problem.
- If "Return All" is false and "Limit" is outside the allowed range (1-100), the node may throw validation errors.
Resolution Tips:
- Ensure the API key credential is valid and has sufficient permissions.
- Verify that the team ID used in filters exists and is accessible.
- Use "Return All" carefully when expecting large datasets to avoid performance issues.