List Projects: Linear action

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
Limit first	string	Optional	Limit. e.g. "50"

Sample request

{
  "first": "50"
}

Returns

{
  "data": {
    "projects": {
      "nodes": [
        {
          "id": "proj-uuid",
          "url": "https://linear.app/team/project/q1-launch",
          "lead": {
            "name": "John Doe"
          },
          "name": "Q1 Launch",
          "state": "started",
          "teams": {
            "nodes": [
              {
                "key": "ENG",
                "name": "Engineering"
              }
            ]
          },
          "startDate": "2025-01-01",
          "targetDate": "2025-03-31",
          "description": "Ship new onboarding flow"
        }
      ]
    }
  }
}

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

FAQ

Questions about List Projects.

What does the List Projects action do in Linear?

Lists projects in your Linear workspace with name, state, lead, and target date. Used to populate a project picker or for roadmap reporting.

What inputs does List Projects require?

List Projects 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 Projects support batch operations?

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

More actions