Linear Advanced icon

Linear Advanced

Enhanced integration with Linear API
Join our community

Actions18

Overview

This node integrates with the Linear API to manage teams and related entities. Specifically, for the Team resource with the Get Many operation, it retrieves multiple team records from a Linear workspace. Users can choose to fetch all teams or limit the number of results returned.

This node is beneficial in scenarios where you want to:

  • List all teams in your Linear workspace for reporting or synchronization.
  • Retrieve a subset of teams based on pagination or limits to optimize performance.
  • Automate workflows that depend on team data, such as assigning issues or generating team-based reports.

Example use case: Automatically fetching all teams to update an external system or dashboard with current team information.

Properties

Name Meaning
Return All Boolean option to return all team records available or only up to a specified limit.
Limit Maximum number of team records to return when "Return All" is false. Value between 1-100.

Output

The output consists of an array of JSON objects, each representing a team retrieved from Linear. Each JSON object contains the team's details such as its ID, name, description, and other metadata as provided by the Linear API.

No binary data is output by this operation.

Example output item (simplified):

{
  "id": "team_id",
  "name": "Team Name",
  "description": "Description of the team",
  "key": "team_key"
}

Dependencies

  • Requires an API key credential for authenticating with the Linear API.
  • Uses the official Linear SDK (@linear/sdk) to interact with the API.
  • The node expects the user to configure the Linear API credentials within n8n before execution.

Troubleshooting

  • Common Issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Requesting too many records without proper limits may lead to timeouts or rate limiting by the Linear API.
    • Providing invalid parameter types (e.g., non-boolean for "Return All") may cause unexpected errors.

  • Error Messages:

    • Errors thrown by the node typically indicate issues like missing required parameters or API request failures.
    • If the error message mentions "Team ID is required," it means a specific team ID was expected but not provided (not applicable for Get Many).
    • For API rate limits or network errors, retry after some time or check API usage quotas.

Links and References

This summary focuses exclusively on the Team resource's Get Many operation as requested.

Discussion