Get Project: 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
Project Key projectKey	string	Required	Jira project key — uppercase letters identifying a project.

Sample request

{
  "projectKey": "e.g. PROJ"
}

Returns

{
  "id": "10000",
  "key": "PROJ",
  "name": "My Project",
  "projectTypeKey": "software"
}

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

FAQ

Questions about Get Project.

What does the Get Project action do in Jira?

Returns details of a Jira project: name, key, lead, issue types, components, and versions. Used to enrich a trigger or validate a project reference.

What inputs does Get Project require?

Required: Project Key. Every input accepts a static value or a variable from any upstream node in your workflow.

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 Get Project support batch operations?

Yes. Run Get Project 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