How to list issues in Linear

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Team ID teamId	string	Optional	Linear team UUID. Find via List Teams.
Limit first	string	Optional	Limit. e.g. "50"

Sample request

{
  "teamId": "e.g. team-uuid",
  "first": "50"
}

Returns

{
  "data": {
    "issues": {
      "nodes": [
        {
          "id": "uuid",
          "url": "https://linear.app/team/issue/ENG-123",
          "state": {
            "name": "In Progress"
          },
          "title": "Fix payment flow",
          "priority": 2,
          "identifier": "ENG-123"
        }
      ]
    }
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Issues.

What does the List Issues action do in Linear?

Lists recent issues from Linear with filters for team, state, assignee, project, and label. Used for digests, sprint reviews, or warehouse exports.

What inputs does List Issues require?

List Issues has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Linear returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Issues support batch operations?

Yes. Run List Issues inside a Loop node to process arrays. TinyCommand handles Linear's rate limits automatically so you don't have to throttle manually.

More actions