Connecting Jira with n8n: authentication, actions, and the Confluence question

n8n connects to Jira through its own app node that manages issues, attachments, comments, and users, while authentication runs either via Cloud OAuth2, Cloud API token, or server credentials. For Confluence, however, there is no dedicated n8n node, so knowledge pages are only reachable through the generic HTTP Request node. This article shows which of the three Jira methods fits your instance, what the Jira node can actually do, and where n8n users most often run into errors in practice. As of: August 2026.

Which authentication method fits your Jira instance?

The right method depends primarily on whether you run Jira Cloud or a server installation. All three variants are documented in the n8n credentials for Jira.

• SW Cloud OAuth2: Intended for Jira Software Cloud. You create an OAuth 2.0 integration in the Atlassian Developer Console, add the callback URL from n8n, and enable the scopes read:jira-user, read:jira-work, write:jira-work, manage:jira-webhook, manage:jira-user, and offline_access. In n8n, you then enter the client ID, client secret, and the domain, for example examplecompany.atlassian.net.
• SW Cloud API Token: Also for Jira Cloud, but without your own OAuth app. You generate the token on the Atlassian profile page and enter your email address, token, and domain in n8n. According to n8n documentation, newly generated tokens can take up to a minute before they work.
• SW Server Account: For Jira Software server installations, a classic set of credentials consisting of email, password, and the Jira access URL is enough, with no further setup needed in Atlassian administration.

Which actions does the Jira node cover?

The Jira node covers four areas: issues, attachments, comments, and users. For issues, you can create, delete, retrieve individually or as a list, view the changelog, execute status transitions, and trigger email notifications. Attachments can be added, retrieved, and removed, comments can be added, updated, and deleted, and for users, creating, deleting, and retrieving are possible. Filter queries run via Jira Query Language (JQL) rather than simple parameter fields, which takes some getting used to. If the node does not cover an operation, the n8n documentation for the Jira node itself refers to the HTTP Request node, which can reuse the same stored credentials.

Why is there no Confluence node, and how do you solve it anyway?

n8n currently does not offer a dedicated Confluence node, even though many teams want to maintain Jira tickets and Confluence knowledge pages in the same process. The usual solution is the HTTP Request node, which talks to the Confluence REST API of an Atlassian instance. n8n has not documented exactly which endpoints, scopes, and permissions are needed for this, so check that directly in Atlassian's own Confluence API documentation before you put a workflow into production. For simple cases like "create a new page when a Jira ticket is closed," an HTTP Request node with the same credentials as the Jira node is usually enough; for more complex page structures, it is worth doing a test run against a sandbox instance before going live.

Which errors come up most often in practice?

In the n8n community, there are mainly three error patterns that make getting started harder. Jira Data Center users report 403 errors when connecting a personal access token, even though the token is valid in Jira itself. Others report that dropdown lists in the Jira node fail with "Could not load list, please check credentials," even though the credentials generally work and the list loads on the next attempt. A third group runs into trouble trying to store Atlassian service accounts instead of personal accounts; saving the credentials then fails with "Forbidden." A look at the n8n community before your own rollout often saves time in such cases, because similar cases have usually already been discussed. If you don't want to build and maintain a reliable Jira automation yourself, NordFlux takes care of it as a fixed-price project, see n8n automation by NordFlux.

Frequently asked questions about Jira and Confluence in n8n

Can I also create Confluence pages automatically with n8n?

Not through a dedicated node, but through the HTTP Request node against the Confluence REST API. n8n does not document this path in detail, so you need to look up endpoints and permissions yourself in the Atlassian documentation. For simple use cases like creating a page when a ticket is closed, the effort involved is manageable.

Which Jira authentication works best for Jira Cloud?

For most teams, the SW Cloud API token method is the most pragmatic starting point, because it works without your own OAuth app. The OAuth2 variant is worthwhile when several users are meant to use the same workflow or when fine-grained scopes are needed.

What should you do about "Forbidden" or 403 errors when connecting Jira credentials?

First check whether the token or account is actually intended for the chosen authentication method; a personal access token from Data Center, for example, does not fit every field. Comparable cases have been documented multiple times in the n8n community, and comparing them with your own setup often helps faster than trying things out from scratch.

Can the Jira node handle complex filter queries?

Yes, but only via Jira Query Language (JQL), not through simple dropdown parameters. Anyone already familiar with JQL from the Jira interface can reuse the same queries in the node.