Skip to content
Connector Scout
–saved records

Gemini · Atlassian (Jira and Confluence)

Does Atlassian (Jira and Confluence) connect to Gemini?

Yes, but Google Cloud documents this as two separate Gemini Enterprise connectors, not one Atlassian connector: a Jira Cloud connector and a Confluence Cloud connector. Google offers no single combined Atlassian or Rovo connector here. Jira Cloud supports search, read, and issue/project/worklog actions such as create comment, update issue and change status; Confluence Cloud supports search, read, and page/space/attachment actions such as create page and upload attachment.

Verified availableDocumentation verifiedLast verified 9 Sept 2026via Gemini Enterprise Jira Cloud + Confluence Cloud connectorsNative connector
Compare connections

Quick answer

Yes — Atlassian (Jira and Confluence) connects to Gemini as a native connector, verified against official documentation on 9 Sept 2026. Documentation confirms search, read, create and update access, while delete remains not confirmed — which is different from unavailable. Yes, but Google Cloud documents this as two separate Gemini Enterprise connectors, not one Atlassian connector: a Jira Cloud connector and a Confluence Cloud connector.

Relationship
Official, delivered through Gemini Enterprise Jira Cloud + Confluence Cloud connectors
Confirmed access
Search, Read, Create and Update · delete not confirmed
Plan or account
A Gemini Enterprise subscription
Setup and admin
Separate Gemini Enterprise Jira Cloud and Confluence Cloud data stores, each configured by an administrator
Last verified
9 Sept 2026
Best fit or limit
Google documents Jira Cloud and Confluence Cloud as two separate Gemini Enterprise connectors; there is no single combined Atlassian or Rovo connector, so a site missing one connection will not surface that product's content.

Connected through Gemini Enterprise Jira Cloud + Confluence Cloud connectors

Atlassian (Jira and Confluence) is a service inside the single Gemini Enterprise Jira Cloud + Confluence Cloud connectors connection on Gemini. You do not install it as a separate app.

What it is

Connector Scout groups Jira and Confluence under one Atlassian entry for browsing, but Google Cloud does not offer a single Atlassian connector for Gemini Enterprise. It documents two independent data-store connectors — Jira Cloud and Confluence Cloud — each configured, authorized and enabled separately by an administrator, and there is no combined Atlassian or Rovo connector in Google's current documentation. The Jira Cloud connector documents natural-language search and read across issues and projects, plus actions covering comments (create, update), issues (create, update, change status, assign, link), attachments (upload), and projects and worklogs (create, update), along with additional read-only actions. The Confluence Cloud connector separately documents search and read across pages and spaces, plus actions to create and update pages, create a blog post, create a space, and upload or download attachments, along with additional read-only actions. Because the two connectors are documented, licensed and enabled independently, an organization could have one without the other, and capabilities from one must never be attributed to the other.

Connection type Two separate Google Cloud connectors for Gemini Enterprise — Jira Cloud and Confluence Cloud — not a single Atlassian connector and not a connected app in the Gemini app

What it can do

What it cannot do

Not confirmed means official documentation does not assign this capability to this specific connection. It is not a claim that the capability is impossible.

Every status is defined the same way across the site — see how connector capabilities are defined and evidenced.

Availability and requirements

Both connectors are documented independently in Google Cloud's Gemini Enterprise connector catalog. Google's Connected Apps documentation for the consumer and Workspace Gemini app does not list Jira or Confluence.

Account requirements

  • A Gemini Enterprise subscription
  • Administrator access to configure a Jira Cloud data store, a Confluence Cloud data store, or both
  • A Jira Cloud site and/or Confluence Cloud site with the connector authorized

How to connect

Setup path Separate Gemini Enterprise Jira Cloud and Confluence Cloud data stores, each configured by an administrator

  1. 1. Decide which Atlassian products to connect

    Because Google documents Jira Cloud and Confluence Cloud as separate connectors, an administrator must set each one up independently.

  2. 2. Create the Jira Cloud data store

    Follow Google Cloud's Jira Cloud connector documentation to authorize the Jira site.

  3. 3. Create the Confluence Cloud data store

    Follow Google Cloud's Confluence Cloud connector documentation to authorize the Confluence site.

  4. 4. Enable the documented actions for each connector

    Choose which Jira issue/project/worklog actions and which Confluence page/space/attachment actions are available to end users.

Permissions, privacy, and admin controls

Required for each connector separately. An administrator creates and authorizes a Jira Cloud data store and, independently, a Confluence Cloud data store inside a Gemini Enterprise app; there is no user-level toggle in the Gemini app and enabling one does not enable the other.

  • Because Jira Cloud and Confluence Cloud are authorized and enabled independently, review each connector's permission scope on its own rather than assuming shared Atlassian-wide access controls.
  • Write actions (creating issues, pages, comments and worklogs, changing status, uploading attachments) post directly into shared Jira and Confluence spaces, so administrators should scope which actions are enabled before broad rollout.

Platform context

  • This connector belongs to Gemini Enterprise on Google Cloud, not to the ordinary Gemini app. It is configured by an administrator as a data store or federated-search connector, requires identity configuration on the source platform, and inherits the authenticated principal's permissions. Individual users cannot enable it from the consumer or Google Workspace Gemini experience, and several connector modes carry preview, allowlist or regional restrictions that must be checked in Google's current documentation.

Documented limitations

  • Google documents Jira Cloud and Confluence Cloud as two separate Gemini Enterprise connectors; there is no single combined Atlassian or Rovo connector, so a site missing one connection will not surface that product's content.
  • This is a Gemini Enterprise connector; Google does not document Jira or Confluence as connected apps in the Gemini app at gemini.google.com.
  • Neither connector documents a delete action for issues, pages, projects or spaces.
  • Available actions depend on what an administrator enables per connector, so end users may see a narrower set than Google's full documented list for either product.

Best use cases

  • Searching Jira for open issues related to a project during planning
  • Reading a Confluence page to summarize documented requirements
  • Creating a Jira issue and assigning it directly from a Gemini Enterprise request
  • Creating or updating a Confluence page to record research findings

Example prompts

  • “Find open Jira issues assigned to the platform team for this sprint.”
  • “Create a Jira issue for the bug we just found and assign it to the on-call engineer.”
  • “Summarize the Confluence page describing our incident response process.”
  • “Create a Confluence page documenting today's architecture review.”

Troubleshooting

  • Confluence content isn't showing up even though Jira search works

    Jira Cloud and Confluence Cloud are separate Gemini Enterprise connectors; confirm an administrator has also configured and authorized the Confluence Cloud data store.

  • Neither Jira nor Confluence appears in my Gemini app settings

    That is expected. Both connectors are documented for Gemini Enterprise, not for Connected Apps in the Gemini app.

Official sources

Verification history

Last verified 9 Sept 2026 · next review 9 Oct 2026 · Connector Scout editorial research

  1. 9 Sept 2026Promoted from research pending to documentation verified against Google Cloud's current Gemini Enterprise Jira Cloud and Confluence Cloud connector documentation. Corrected the record to represent two separate Google-documented connectors rather than a single Atlassian connector.

Documentation verified — editorial disclosure

Documentation verified means Connector Scout confirmed the connection and listed capabilities against official provider documentation. It does not mean Connector Scout completed hands-on testing in a live account.

Independence notice

Connector Scout is not affiliated with Google or Atlassian. Confirm security-sensitive details against the vendor’s own documentation before rolling out access.