What is the Jira node called in n8n?

Jira Software. It works with issues, issue attachments, issue comments and users. The Jira Trigger handles incoming Jira webhooks.

Which credential should I use for Jira Cloud?

SW Cloud API token (email plus API token) is the quickest. SW Cloud OAuth2 needs an Atlassian app with every requested scope enabled. Jira Server uses SW Server account.

Why does Get All return my whole Jira?

Without a JQL filter, Issue → Get Many returns every issue you can see. Always add JQL such as project = KEY.

Do Jira steps convert automatically?

Not yet. They arrive as marked placeholders with the project, issue type and fields; most are one Jira Software node.

Pipedream Jira steps in n8n

Updated 2026-10-21 · 3 min read · n8n: Jira Software (Native n8n node)

Jira workflows on Pipedream move work between tools: a support ticket or a failed CI run creates an issue, an issue update posts to Slack or Teams. n8n's native Jira Software node and Jira Trigger cover the same ground for issues and comments.

The n8n side

Jira Software node (n8n-nodes-base.jira):

Resource	Operations
Issue	Create, Delete, Get, Get Many, Update, Changelog, Notify (email), Status (transitions)
Issue Attachment	Add, Get, Get All, Remove
Issue Comment	Add, Get, Get All, Remove, Update
User	Create, Delete, Get

Jira Trigger: registers a webhook in Jira for the events you select (issue created, updated, deleted, comments and more).

What maps where

Pipedream (app `jira`)	In n8n	Status
Create Issue	Jira Software → Issue → Create	manual
Update Issue, Assign Issue	Issue → Update (assignee field)	manual
Transition Issue	Issue → Status (list transitions), then Update with the status	manual
Add Comment To Issue	Issue Comment → Add	manual
Add Attachment To Issue, Add Multiple Attachments	Issue Attachment → Add (binary input)	manual
Check Issues Against JQL, Search Issues with JQL	Issue → Get Many with JQL	manual
Add Watcher To Issue	HTTP Request `POST /rest/api/3/issue/{key}/watchers`	manual
New Issue Created / Updated / Deleted Event (Instant), New Event	Jira Trigger with the same events	manual
Code step with `this.jira.$auth.oauth_access_token` and `cloud_id`	Code node; values become variables listed in the report	automatic, review

Jira actions are not in the converter's automatic list. Each arrives as a placeholder with the project key, issue type, summary and fields in a comment.

Credentials

n8n's Jira page lists:

SW Cloud API token – your Atlassian email and an API token. A new token can take about a minute to start working.
SW Cloud OAuth2 – an Atlassian OAuth app. Every scope n8n requests must be enabled on the app; defaults are read:jira-user, read:jira-work, write:jira-work, manage:jira-webhook. User Create and Delete also need manage:jira-configuration via Custom Scopes.
SW Server account – email, password and domain for Jira Server / Data Center.

Pipedream's Jira connection used OAuth with a Cloud ID; in n8n with an API token you use the site URL (https://yourteam.atlassian.net) instead.

Typical migration: GitHub issue to Jira

Pipedream: GitHub New or Updated Issue → Jira Create Issue → GitHub Create Issue Comment (link back). n8n: GitHub Trigger (Issues, converted automatically) → Jira Software → Issue → Create → HTTP Request (GitHub comment, converted automatically).

Pitfalls

JQL first. Get Many without JQL returns every visible issue; add project = KEY and a date filter.
Rich text. Jira Cloud API v3 uses Atlassian Document Format for descriptions and comments. Plain text from Pipedream may need wrapping; n8n's node handles simple text, but formatted content needs ADF JSON via HTTP Request.
Custom fields are addressed by ID (customfield_10010). Copy IDs from the Pipedream props.
Rate limits. Jira Cloud uses an hourly points quota plus burst limits (100 requests per second for GET/POST, 50 for PUT/DELETE) and per-issue write limits (20 per 2 seconds). Over the limit you get 429 with Retry-After. Bulk updates need a Wait node.
Webhook duplicates. Leave the Pipedream workflow off once the Jira Trigger is active, or both will react.

How to move your Jira workflows

Export the workflows from Pipedream.
Upload on /convert; the free report lists each Jira step with its fields.
Download the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

More: Pipedream to n8n guide, code step checker for jira.js code. Related: GitHub, ClickUp, Microsoft Teams.

FAQ

What is the Jira node called in n8n?: Jira Software. It works with issues, issue attachments, issue comments and users. The Jira Trigger handles incoming Jira webhooks.
Which credential should I use for Jira Cloud?: SW Cloud API token (email plus API token) is the quickest. SW Cloud OAuth2 needs an Atlassian app with every requested scope enabled. Jira Server uses SW Server account.
Why does Get All return my whole Jira?: Without a JQL filter, Issue → Get Many returns every issue you can see. Always add JQL such as project = KEY.
Do Jira steps convert automatically?: Not yet. They arrive as marked placeholders with the project, issue type and fields; most are one Jira Software node.