Does n8n have a native Jira node?

Yes. n8n includes a Jira Software node supporting issue create/read/update/delete, comments, attachments, and user lookups. There is also a Jira Software Trigger node that fires on issue events — created, updated, status changed, assigned, commented — via Jira webhooks. Authentication uses Jira API tokens with your Atlassian account email.

How do you connect n8n to Jira?

Generate an API token at id.atlassian.com → Security → API tokens → Create. In n8n, create a Jira Software credential: enter your Atlassian email, paste the API token, and set your Jira Cloud domain (e.g. yourorg.atlassian.net). This credential works for both the Jira node and the Jira Trigger node. For Jira Data Center (self-hosted), use the Personal Access Token method instead.

What is the difference between n8n Jira integration and Jira's built-in automation?

Jira's built-in Automation (formerly Jira Automation Rules) is great for Jira-internal logic — auto-assigning issues, updating fields based on triggers, creating sub-tasks. n8n goes further by connecting Jira to external systems: posting Slack alerts when a high-priority bug is created, syncing Jira issues to Salesforce cases or Zendesk tickets, creating Jira issues from incoming emails or webhooks, and logging sprint velocity to Google Sheets. Use Jira Automation for within-Jira logic, n8n for anything that crosses system boundaries.

How do you create Jira issues automatically from n8n?

Use the Jira Software node with Operation: Issue → Create. Required fields: Project Key (e.g. 'ENG'), Issue Type (e.g. 'Bug', 'Task', 'Story'), and Summary. Optional: Description, Assignee, Priority, Labels, Sprint (via custom field). You can trigger this from any upstream node — a Webhook receiving an alert from your monitoring system, a Slack command node, or an email trigger — to create a Jira issue with the relevant context already filled in.

Can n8n trigger workflows when a Jira issue status changes?

Yes, via the Jira Software Trigger node. Configure it in n8n to listen for 'jira:issue_updated' events. In your Jira settings (System → Webhooks), create a webhook pointing to your n8n trigger URL. The payload includes the issue key, the old and new status, the user who made the change, and the full issue fields. Add an IF node in n8n to filter for specific transitions, such as 'In Progress → Done' or 'To Do → In Progress'.

How do you sync Jira issues to another project management tool with n8n?

Use the Jira Trigger to fire on issue create or update. Then write to the target system via its n8n node — Monday.com, Asana, Notion, or a Google Sheet. Map the Jira fields (summary, description, status, assignee, priority) to the target system's fields. Store the target system's record ID back on the Jira issue as a custom field so future updates can look up the correct record without another search.

n8n Jira Integration: Automate Issues & Alerts

At a Glance — n8n Jira Integration

Native node included: Jira Software node (issues, comments, attachments, users) + Jira Software Trigger node (issue events via Jira webhooks)
Auth: API token — id.atlassian.com → Security → API tokens → Create; enter your Atlassian email + token + Jira Cloud domain in n8n (e.g. yourorg.atlassian.net)
Status-change trigger: Jira Trigger on jira:issue_updated → IF node checking current.status vs previous.status to filter for specific transitions
n8n vs Jira Automation: Jira Automation handles within-Jira logic; n8n is for cross-system workflows — Slack alerts, Salesforce sync, Zendesk tickets, Google Sheets dashboards
Creating issues: Jira node → Issue → Create; required: Project Key, Issue Type, Summary; optional: Assignee, Priority, Labels, Sprint (via custom field ID)
Syncing to other PM tools: Map Jira fields to target system on trigger; store the target record ID back on the Jira issue as a custom field for future update lookups

n8n vs Jira's Built-in Automation

Jira includes its own automation engine — rule-based automations that can assign issues, update fields, send emails, and trigger Slack messages based on Jira events. For actions that stay within Jira (or within Atlassian's ecosystem), the built-in automation is the right tool. It requires no external setup and runs without maintenance.

n8n is the right choice when the automation crosses into systems outside Jira: creating a Jira issue from a Salesforce case, syncing sprint velocity to a Google Sheet, posting customized Slack alerts with data pulled from a database, or creating Jira issues when your monitoring system fires an alert. n8n also lets you write custom logic — conditional branching, data transformation, multi-step workflows — that Jira's rule engine cannot express.

Connecting Jira to n8n

Jira uses API tokens for authentication. Generate one at id.atlassian.com → Security → API tokens → Create API token. Give it a descriptive name like "n8n Integration" and copy the token immediately — it is not shown again.

In n8n, create a Jira Software credential:

Host: your Jira Cloud URL (e.g. https://yourorg.atlassian.net)
Email: your Atlassian account email
API Token: the token you just created

This credential works for both the Jira node (actions) and the Jira Trigger node (events). For Jira Data Center (on-premise), use a Personal Access Token generated in your profile settings.

Finding project keys and field IDs

When creating issues, you need the Project Key (the 2-5 letter code visible in every issue URL, e.g. ENG, PROJ) and the Issue Type ID. To find all issue type IDs for a project, use the n8n Jira node with Operation: Issue Type → Get All, passing your project key. Custom field IDs follow the format customfield_10001 — check your Jira admin under Issues → Custom Fields to find them.

Workflow: External Alert → Jira Issue

The most common n8n + Jira workflow is automated issue creation from external systems — a monitoring alert, a support ticket escalation, an error log entry, or a customer form submission creates a Jira issue automatically.

Webhook Trigger — receive alert from your monitoring system (Datadog, PagerDuty, Sentry, etc.)
Set node — extract severity, message, affected service, timestamp
IF node — only create a Jira issue for HIGH or CRITICAL severity alerts (skip low-severity noise)
Jira node (Issue → Create) — project key: ENG, issue type: Bug, summary from alert title, description from full alert message, priority mapped from severity level, labels: [monitoring, auto-created]
Slack node — post to #incidents: "Jira issue [ENG-1234] created: [alert title]" with link to the issue

The issue link in Slack lets your on-call engineer jump directly to the Jira ticket without searching — a small but meaningful improvement to incident response time.

Workflow: Jira Status Change → Slack Alert

Jira's built-in Slack integration sends generic notifications. n8n lets you craft specific, contextual alerts — only for certain projects, statuses, or teams.

Jira Trigger node — event: jira:issue_updated. In Jira admin, create a webhook pointing to this node's URL. Set a JQL filter on the webhook (e.g. project = ENG AND issuetype = Bug AND priority = High) so only relevant events reach n8n.
IF node — check {{ $json.changelog.items }} for a field change where field === 'status'
Set node — extract old status (fromString), new status (toString), issue key, assignee, and summary
IF node — filter for specific transitions: "In Progress → Done" to notify on completions, or "To Do → In Progress" to alert when someone picks up the issue
Slack node — post targeted message: "🟢 [ENG-1234] moved to Done by [assignee]: [summary]"

Workflow: Weekly Sprint Report to Slack

Replace the manual sprint report meeting prep with an automated summary delivered every Monday morning:

Schedule Trigger — every Monday at 8 AM
HTTP Request node — call the Jira API: GET /rest/agile/1.0/board/{boardId}/sprint?state=active to get the current sprint
HTTP Request node — get all issues in the sprint: GET /rest/agile/1.0/sprint/{sprintId}/issue?jql=...
Code node — count issues by status (To Do, In Progress, Done), calculate completion percentage, list blocked issues
Slack node — post weekly summary: sprint name, days remaining, X done / Y in progress / Z to do, any blocked tickets

This runs automatically without anyone having to pull the numbers. The team sees the summary in Slack before standup.

Workflow: Salesforce Case → Jira Issue (and Back)

When your support team logs a case in Salesforce that requires engineering work, creating the Jira issue manually is a common source of delay and data entry errors. This workflow connects them:

Salesforce → Jira: Salesforce Trigger on Case create with a specific field value (e.g. "Needs Engineering"). Extract case ID, customer name, description, severity. Create Jira issue in the ENG project with this context. Write the Jira issue key back to the Salesforce case as a custom field.

Jira → Salesforce: Jira Trigger on issue status change to "Done". Look up the Salesforce case by the Jira issue key stored in its custom field. Update the Salesforce case status to "Resolved" and add a note with the Jira resolution details.

See also: n8n Salesforce integration for more on connecting Salesforce with n8n.

Need Jira Automation Built?

Entech Solutions builds n8n workflows connecting Jira to Salesforce, Slack, Zendesk, and your full DevOps stack. See our n8n Jira automation service page, or get in touch to discuss your use case.