Actions18
Overview
This node provides advanced integration with the Linear API, allowing users to interact programmatically with various Linear resources such as issues, comments, labels, members, projects, and teams. Specifically for the Team - Get operation, it retrieves detailed information about a specific team by its ID.
Common scenarios where this node is beneficial include:
- Automating project management workflows by fetching team details dynamically.
- Integrating Linear team data into other systems or dashboards.
- Enriching issue or project data with team metadata during automation.
For example, you can use this node to fetch a team's name, description, and other metadata by providing the team’s unique ID, then use that data downstream in your workflow for reporting or conditional logic.
Properties
| Name | Meaning |
|---|---|
| Team ID | The unique identifier of the team to retrieve. This is a required string input. |
Output
The output is a JSON object representing the requested team’s details as returned by the Linear API. It typically includes fields such as the team’s ID, name, key, description, and possibly other metadata related to the team.
Example structure (simplified):
{
"id": "string",
"name": "string",
"key": "string",
"description": "string",
// additional team properties...
}
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Linear API via an API key credential configured in n8n.
- Uses the official Linear SDK client internally to communicate with the Linear API.
- The node expects valid API credentials with permissions to read team data.
Troubleshooting
- Missing or invalid Team ID: If the provided Team ID is empty or incorrect, the node will fail to retrieve the team. Ensure the Team ID is correct and exists in your Linear workspace.
- API authentication errors: If the API key credential is missing, expired, or lacks necessary permissions, the node will throw an authentication error. Verify your API key and permissions.
- Network or API downtime: Temporary network issues or Linear API outages may cause failures. Retry after some time or check Linear's status page.
- Error messages: Errors thrown by the node will include descriptive messages from the Linear SDK or API. Use these messages to identify issues such as invalid parameters or permission problems.