This document explains the Linear Issue Reader node, which enables automated issue retrieval from Linear workspaces.

​

Node Inputs

​

Required Fields

• Filters: Select filtering criteria to narrow down which issues to retrieve:

  • Team: Filter by specific teams (e.g., “Engineering”, “Marketing”)
  • Status: Filter by issue status (e.g., “In Progress”, “Done”, “Backlog”)
  • Priority: Filter by priority level (e.g., “High”, “Urgent”, “Medium”)
  • Labels: Filter by custom labels (e.g., “Bug”, “Feature”)
  • Assignee: Filter by team member assignments

• Issue Information: Choose which data fields to retrieve:

  • Description: The detailed explanation of the issue
  • Identifier: The unique issue ID (e.g., “ENG-123”)
  • Title: The issue title/summary
  • URL: Link to the issue in Linear
  • Assignee: Team member assigned to the issue
  • Status: Current status of the issue
  • Project: The project the issue belongs to

​

Optional Field

• Number of Issues: Limit the total number of issues to retrieve
  • Default: 10
  • Set a number to limit or increase results

​

Configure Inputs

All parameters can be set as dynamic inputs to the node. This option is accessible under “Show more options” or when you hover over the node.

This makes the node adaptable for Loop Mode operations and conditional workflows.

​

Node Output

The node produces data for each selected information field:

• If Number of Issues is set to 1: Output is in Text format
• If Number of Issues is greater than 1: Output is in List format (string[])

​

Node Functionality

The Linear Issue Reader node retrieves issues based on specified filters, enabling automated project tracking and analysis.

Key features include:

• Multiple filtering options for precise issue selection
• Custom field selection to retrieve only necessary data
• Issue count control to manage data volume
• Team and project-based filtering
• Secure authentication with Gumloop

​

Example Workflows

​

1. Weekly Project Status Report

Linear Issue Reader → Ask AI → Google Docs Writer
Setup:
- Filters: Team="Product", Status="In Progress", Labels="Q2 Goals"
- Issue Information: Title, Status, Assignee, Project
- Number of Issues: 50
Purpose: Generate weekly status report of active product initiatives

​

2. Engineering Team Workload Analysis

Linear Issue Reader → Extract Data → Google Sheets Writer
Setup:
- Filters: Team="Engineering", Status≠"Done"
- Issue Information: Assignee, Priority, Status, Project
Purpose: Analyze current workload distribution across engineering team

​

3. Bug Tracking Alert System

Linear Issue Reader → If-Else → Slack Message Sender
Setup:
- Filters: Labels="Bug", Priority="High", Status="Todo"
- Issue Information: Title, URL, Description
- Configure as trigger (runs hourly)
Purpose: Alert team about high-priority unaddressed bugs

​

4. Sprint Planning Assistant

Linear Issue Reader → Categorizer → Ask AI → Airtable Writer
Setup:
- Filters: Status="Backlog", Team="Design" 
- Issue Information: All fields
Purpose: Categorize and prioritize backlog issues for upcoming sprint

​

Loop Mode Pattern

The Linear Issue Reader works effectively in Loop Mode when you need to process issues individually:

Input: List of Assignee names from Google Sheet
Process: Retrieve issues for each Assignee (Loop Mode)
Output: Assignee-specific issue reports

​

Important Considerations

1. Requires Authentication with Linear - Set up in the Credentials page
2. Must select minimum one information field
3. Output format depends on Number of Issues setting (1 = Text, >1 = List)
4. For best performance, use specific filters when dealing with large Linear workspaces

In summary, the Linear Issue Reader node streamlines issue tracking and analysis from Linear workspaces. It’s particularly valuable for teams that need to generate reports, monitor project status, or create dashboards based on Linear data.