Skip to main content
Noxus integrates with Atlassian products (Jira and Confluence) using API token authentication for secure, organization-wide access.

Supported Atlassian Services


Authentication: API Token

Description

Atlassian integrations use API tokens for authentication. An API token is a secure credential that allows Noxus to access your Atlassian resources without storing your password.

When to Use

Ideal For

  • Automated issue management
  • Documentation workflows
  • Project tracking automation
  • Team collaboration flows

Characteristics

  • Permission Type: User-level API token
  • Setup: Generate token in Atlassian account
  • Access Scope: Based on user’s permissions
  • Best For: Automation and integrations

Authentication Flow


Setup Process

1

Go to Atlassian Account

Navigate to id.atlassian.com
2

Access Security

Go to Security → API tokens
3

Create Token

Click Create API token
4

Name Your Token

Enter a label (e.g., “Noxus Integration”)
5

Copy Token

Copy the token value immediately (it won’t be shown again)
Store the API token securely. You won’t be able to retrieve it after leaving the page.

Jira Integration

Capabilities

Create and Update Issues:
  • Create new issues with custom fields
  • Update issue status and assignees
  • Add comments and attachments
  • Link related issues
  • Set priority and labels
Search and Query:
  • Search issues with JQL
  • Filter by project, status, assignee
  • Get issue details and history
  • Track issue changes
Project Management:
  • List all accessible projects
  • Get project details and configuration
  • Access project boards
  • Manage project components
  • View project workflows
Automated Workflows:
  • Transition issues between statuses
  • Assign issues based on criteria
  • Create sub-tasks automatically
  • Update custom fields
  • Sync with external systems

Nodes

Work item nodes take a Work item key such as ENG-123, typed or bound. The current versions return typed fields and records instead of one block of text, and a request Jira rejects fails the run with Jira’s reason. Get Jira Comments, Search Jira Users and List Jira Projects take Start at and output Next Start At for the next batch (0 once everything is read). Example: an incident flow runs Create Work Item with Work type Bug, then Add Jira Attachment with the error log, then Link Work Items to relate the new bug to its parent problem.

Common Use Cases

Create work items from email

Turn a customer email into a Jira work item and tell the team.

Keep Jira in step with other tools

When another system reports a change, update the matching work item.

Send a weekly report

On a schedule, list the work items, summarise them and email the summary.

Confluence Integration

Capabilities

Create and Edit Pages:
  • Create pages in any space
  • Update page content
  • Add labels and metadata
  • Manage page hierarchy
  • Version tracking
Content Operations:
  • Read page content
  • Export to different formats
  • Search across spaces
  • Attach files
Space Management:
  • List accessible spaces
  • Get space details
  • Create new spaces (if permissions allow)
  • Manage space permissions
  • Access space content
Content Search:
  • Search across all spaces
  • Filter by space, label, or content type
  • Full-text search
  • Recently updated content
  • Access page metadata

Pages, blog posts and attachments

The list nodes return each page or blog post as an object with its id, title, space_key, space_name, version and created date, so later nodes can use a single field. Page and blog post IDs are also in the address of the page in Confluence.
Get Confluence Attachments only lists the attachments until you turn on Download files, under advanced settings. The node then adds a files output with each attachment as a file you can pass to other nodes. Attachments larger than Max file size (100 MB by default, under advanced settings) are still listed but left out of the files, and the run shows a warning.

Spaces, pages, search, comments and labels

Get Space, List Spaces, Get Page, Search Content, Get Confluence Comments and Get Labels return each item as an object instead of text; Search Content results carry a type of page, blogpost, space or user. List Spaces, Search Content, Get Confluence Comments and Get Labels take Max results (up to 1000) and a Page token, and output a Next page token for the next batch. Update Page and Add Label output success as a boolean, and Add Confluence Comment outputs the new comment’s ID. When Confluence rejects a request, the run fails with Confluence’s reason instead of reporting success false, an empty ID or an empty list. Example: a review flow runs Search Content with a CQL query, loops over the results whose type is page, and runs Add Label with needs-review on each; a page the connection can’t edit stops the run with Confluence’s reason.

Common Use Cases

Write documentation pages

Draft a page from incoming content and publish it to a space.

Feed a knowledge base

When a page changes, add its latest version to a knowledge base.

Answer questions from Confluence

Search Confluence for a question asked in Teams and answer in the chat.

Security Best Practices

API Token Management

  • Rotate tokens regularly (every 90-180 days)
  • Use separate tokens for different integrations
  • Revoke unused tokens
  • Monitor token usage

Access Control

  • Use accounts with appropriate permissions
  • Don’t use admin accounts unless necessary
  • Review Jira/Confluence permissions
  • Audit automation activities

Troubleshooting

Possible Causes:
  • Invalid API token
  • Token expired or revoked
  • Incorrect email address
  • Wrong site URL
Solutions:
  • Generate a new API token
  • Verify email matches token owner
  • Check site URL format (e.g., company.atlassian.net)
  • Test connection with Atlassian API directly
Possible Causes:
  • Insufficient Jira/Confluence permissions
  • Project/space access restrictions
  • Issue type not allowed
  • Field restrictions
Solutions:
  • Verify user has required permissions
  • Check project/space access settings
  • Review issue type scheme
  • Confirm field permissions
Possible Causes:
  • Too many API requests
  • Concurrent flow executions
  • Bulk operations
Solutions:
  • Implement delays between requests
  • Use batch operations where available
  • Reduce flow execution frequency
  • Contact Atlassian about rate limits

Next Steps

Developer Tools

GitHub, Linear, and more

Collaboration

Slack, Notion, and team tools

All Integrations

Browse the complete catalog