Actions18
Overview
The node provides advanced integration with the Linear API, specifically enabling retrieval of multiple labels ("Label" resource, "Get Many" operation). It allows users to fetch a list of labels from Linear, optionally filtered by team ID, and supports returning either all matching labels or a limited subset.
This is useful in scenarios where you want to synchronize or analyze label data from Linear projects, automate workflows based on label metadata, or display label information in other systems. For example, you might use this node to get all labels associated with a particular team to generate reports or trigger actions based on label usage.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching labels or only up to a specified limit |
| Limit | Maximum number of labels to return when "Return All" is false (minimum 1, maximum 100) |
| Filters | Collection of filters to narrow down results: |
| Team ID | Filter labels by the ID of the team they belong to |
Output
- The output is an array of JSON objects, each representing a label retrieved from Linear.
- Each label object contains properties such as its ID, name, description, color, and associated team information.
- The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Linear API.
- Uses the official Linear SDK (
@linear/sdk) to interact with the Linear service. - The node expects proper configuration of the Linear API credentials within n8n.
Troubleshooting
Common issues:
- Providing an invalid or expired API key will cause authentication failures.
- Specifying a non-existent team ID filter may result in zero labels returned.
- Requesting more than 100 labels without setting "Return All" to true will limit results to 100 due to API constraints.
Error messages:
- Errors thrown by the Linear SDK or network issues will be surfaced as node errors.
- If the node encounters an error but "Continue On Fail" is enabled, it returns an error object in the output JSON instead of stopping execution.
Resolution tips:
- Verify that the API key credential is valid and has sufficient permissions.
- Double-check team IDs used in filters.
- Use "Return All" carefully to avoid large data loads impacting performance.