List Projects: Jira 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
Max Results maxResults	string	Optional	Max Results. e.g. "50"
Order By orderBy	options	Optional	Order By. Options: Last Updated (newest), Name (A-Z), Key (A-Z)

Sample request

{
  "maxResults": "50",
  "orderBy": "{{trigger.orderBy}}"
}

Returns

{
  "total": 15,
  "values": [
    {
      "id": "10001",
      "key": "PROJ",
      "name": "My Project",
      "projectTypeKey": "software"
    }
  ]
}

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 Jira?

Lists all Jira projects accessible to the authenticated user with key, name, and lead. The standard first step before scoping work to a project.

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 Jira 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 Jira's rate limits automatically so you don't have to throttle manually.

More actions