Jira Node

The Jira node connects workflows to the Jira REST API for project, issue, comment, attachment, user, notification, and transition automation. The default operation is Search Issues.

Overview

Credential

Create a Jira credential in the Credentials Tab. Stored config keys are email, api_token, base_url, deployment, auth_mode, and optional api_version. For Jira Cloud, email stores the Atlassian account email and api_token stores the Atlassian API token. For Jira Data Center / Server, those same keys store the Basic auth username and password, or, with auth_mode: pat, api_token stores a personal access token sent as a Bearer token and email is not used. See Third-Party Integrations for setup steps.

Personal access tokens require Jira Data Center / Server 8.14 or later. Switching authentication method clears the stored secret, so enter the new password or token when you switch.

Use Test Connection to verify the credential against the current Jira user.

Operations

Expression-capable text fields support expressions such as $input.text. jiraIncludeBinary is a boolean toggle and does not support expressions, but it can be marked as agent-provided when the Jira node is attached to an Agent tool handle.

Issue and update fields

• Project Key is the short project key such as ENG. Use List Projects to discover keys.
• Issue Key or ID accepts keys such as ENG-123 or numeric issue IDs. Use Search Issues or List Projects to discover values.
• Transition ID comes from List Transitions. Each transition object includes an id field.
• Comment ID and Attachment ID come from List Comments, List Attachments, or prior create/get responses.
• Account ID / Username is the Jira Cloud accountId value or the Jira Data Center / Server username. Get Myself or Get User can help you discover it.
• Issue description and comment body text are sent as Atlassian Document Format on REST API v3; when the credential deployment is Data Center / Server, they are sent as plain text. In v3, newline characters become separate paragraphs.
• Get Issue Changelog uses Jira Cloud's paginated changelog endpoint. For Data Center / Server, it reads expanded issue changelog data and applies the configured offset/limit to the returned histories.
• On Update Issue, leave optional fields empty to preserve their current values.
• Set Description or Assignee Account ID / Username to null on update to clear those fields. Labels cannot be cleared with null.
• Recipients JSON on Notify Issue defaults to {"assignee":true} when omitted. Common keys include assignee, reporter, watchers, and voters (for example {"assignee":true,"watchers":true}).
• Add Attachment accepts raw base64 or data URL content and is limited by the platform file size setting (default 99 MB).

Pagination

• Search Issues uses cursor pagination via jiraNextPageToken for Jira Cloud. Read pagination.nextPageToken from the previous run and pass it into the next Search Issues node.
• Search Issues uses offset pagination via jiraStartAt for Jira Data Center / Server. Read pagination.startAt, pagination.maxResults, and pagination.total to calculate the next page.
• List Projects, Get Issue Changelog, List Comments, and List Attachments use offset pagination with jiraLimit and jiraStartAt. Paged results return pagination.startAt, pagination.maxResults, pagination.total, and pagination.isLast.
• List Attachments fetches all attachments from the issue first, then slices the result client-side. Pagination fields still describe the returned page, but large issues may incur an extra fetch cost.
• List Transitions does not paginate.

Key Fields

Examples

Create an issue from upstream input:

• Operation: createIssue
• Project Key: ENG
• Issue Type: Task
• Summary: $input.title
• Description: $input.description
• Labels: ["automation"]

Update an issue and clear the assignee:

• Operation: updateIssue
• Issue Key or ID: ENG-123
• Summary: $input.title
• Assignee Account ID / Username: null

Search issues with custom fields and cursor pagination:

• Operation: searchIssues
• JQL: project = ENG AND updated >= -30d ORDER BY updated DESC
• Issue Fields: ["key","summary","status"]
• Limit: 25
• Next Page Token: $searchJira.pagination.nextPageToken

Search issues on Data Center with offset pagination:

• Operation: searchIssues
• JQL: project = ENG ORDER BY updated DESC
• Limit: 25
• Start At: 25

Transition an issue after listing available transitions:

• Operation: listTransitions
• Issue Key or ID: ENG-123
• Then run Transition Issue with Transition ID: $listTransitions.transitions[0].id

Notify watchers about an issue update:

• Operation: notifyIssue
• Issue Key or ID: ENG-123
• Subject: Issue updated
• Text Body: $input.text
• Recipients JSON: {"assignee":true,"watchers":true}

Output

Every successful operation sets:

• $jira.success
• $jira.operation

Get Myself exposes user.

Paginated list operations expose count, a collection field, and pagination:

List Transitions exposes transitions and count without pagination.

Issue mutations and reads expose the Jira issue payload plus key where applicable.

Comment get/create/update expose comment; delete exposes deleted.

Transition Issue exposes transition as { transitionId }, plus the refreshed issue and key.

Attachment add exposes attachments and count. Get Attachment exposes attachment; List Attachments exposes attachments, count, and pagination. When Include Binary is enabled, each attachment object may include content_base64. Delete exposes deleted.

User get/create expose user; delete exposes deleted.

Notify Issue exposes notified.

Common access patterns:

• $searchJira.issues[0].key
• $searchJira.pagination.nextPageToken
• $createJiraIssue.key
• $listTransitions.transitions[0].id
• $getAttachment.attachment.content_base64

Related

• Credentials Tab
• Third-Party Integrations
• Node Types
• Expression DSL