How to Connect Jira and Confluence to an AI Agent

· DoubleX

Quick answer

To connect Jira and Confluence to an AI agent, open the Connectors screen in DoubleX Agentes, choose Jira and Confluence, sign in with your Atlassian account, and pick a personal, team, or company connection. Then limit the agent to read-only actions, require confirmation for changes, and test with a simple request.

Connecting Jira and Confluence to an AI agent takes a few minutes, but the choices you make along the way decide what the agent can see and change. This guide focuses on setup and permission control: who can connect, which connection type fits, how to keep the agent read-only, and how to confirm it works. For ideas on what to do once it is connected, see What You Can Automate in Jira and Confluence With AI.

What does the Jira and Confluence connector let the agent do?#

The connector lets an agent search and edit Jira issues and Confluence pages through Atlassian Rovo. A connector is a system linked to the platform, and the agent uses that system's tools on your behalf.

In practice, that means an agent can look up issues, read the content of a Confluence page, and, if you allow it, update issues or edit pages. What it can actually reach is still limited by the permissions of the Atlassian account used for the connection.

What do you need to prepare before connecting?#

You need an Atlassian account that can already see the Jira projects and Confluence spaces you want the agent to use, plus a DoubleX Agentes account. The agent never sees more than that Atlassian account can see.

Before you start, check these items:

ItemWhat to check
Atlassian accountYou can sign in and open the target Jira projects and Confluence spaces
ScopeYou know which projects and spaces the agent should use
Access levelYou decided whether the agent should only read or also edit
Connection ownerYou know whether it is a personal, team, or company connection
DoubleX Agentes roleYou are an owner or administrator if the connection will be shared

How do you connect step by step on the Connectors screen?#

You connect from the Connectors screen by selecting Jira and Confluence and authorizing your Atlassian account. Then you attach the connector to the agent that will use it.

  1. Create your DoubleX Agentes account if you do not have one yet. It is free and needs no card. If you want help deciding where to start, take the diagnostic first (see the Quickstart).
  2. Open the Connectors screen and select Jira and Confluence.
  3. Choose the connection type: personal, team, or company (more on that in the next section).
  4. Sign in with your Atlassian account and approve the access request.
  5. Open the Agents screen, pick the agent that will use Jira and Confluence, and add the connector to it.
  6. In the agent's settings, choose which actions it may run in this system (see the read-only section below).
  7. Ask for a first request to confirm the connection works.

Developers can also manage connectors through the API; see the Connectors API reference.

Personal, team, or company connection: which one should you choose?#

Choose personal when the access should belong to one person, team when a group shares the same access, and company when the whole organization should use the same connection. A personal connection only applies to that person, like their own email.

Connection typeBest forWatch out for
PersonalIndividual work, testing, or when the agent should see only what you seeOthers cannot reuse it
TeamA squad or area that works in the same projects and spacesEveryone on the team shares that access
CompanyShared agents used across areasUse an account with carefully scoped permissions

A good default is to start with a personal connection for your first tests. Once the agent behaves the way you want, move to a team or company connection and give each agent only the systems it needs.

How do you keep the agent read-only and require confirmation before changes?#

For each agent, you choose which systems it uses and which actions it can run in each one. Turn off the actions that change data and the agent can only read. Even when changes are allowed, the agent asks for confirmation before sending, deleting, or altering anything and shows the steps it took.

A safe setup looks like this:

  1. Attach Jira and Confluence only to the agents that need them.
  2. Allow the search and read actions first.
  3. Leave the actions that create or edit issues and pages turned off until you have reviewed a few results.
  4. When you enable editing, keep confirmation on so a person approves each change.

The company content is not used to train models, and every request is recorded in the task history. Connection credentials are stored encrypted.

How do you test the connection and check the history in Tasks?#

Test with a read-only request on a small, known project, then open the Tasks screen to see exactly what the agent did. Every request becomes a task with the full history: the request, each tool the agent used, and the result.

Copy and adapt these first requests:

  • "Search Jira for open issues in the project PAY and list the five most recent with their status."
  • "Find the Confluence page about our release process and summarize it in five bullet points."
  • "List the Jira issues assigned to me that were updated this week."
  • "Which Confluence pages mention the word 'onboarding'? Give me the titles only."

Then open Tasks and check three things: the agent called the Jira or Confluence tool, the results match what you see in Atlassian, and no write action was attempted. If something is missing, review the Atlassian account's access and the actions enabled for the agent. To add company context for better answers, see Brain.

Frequently asked questions#

Who can connect Jira and Confluence?#

Anyone with an Atlassian account and access to the projects and spaces they want to use can create a personal connection. Sharing a connection with a team or the company depends on your role in DoubleX Agentes, so check with an owner or administrator.

Can the agent see projects my Atlassian account cannot access?#

No. The agent works through the connected account, so it is limited to what that account can see in Jira and Confluence.

Can I make the agent read-only?#

Yes. For each agent you choose which actions it can run in each system, and you can leave the ones that change data turned off.

Will the agent change issues or pages without asking?#

No. Before sending, deleting, or changing something in your systems, the agent asks for confirmation and shows the steps it took. Everything is also recorded in the task history.

Can I connect other tools the same way?#

Yes. The flow is similar for other connectors, such as Box or Jam: choose the system on the Connectors screen, authorize it, and set permissions per agent.

Related guides

More Jira e Confluence guides