Skip to main content
Research Preview
Research Preview: The Confluence integration is set as Research Preview and is under active development. Functionality and results may evolve as we continue to improve the feature. We recommend reviewing and validating outputs before use, and advise against using these features in production or business-critical workflows.
Connect Confluence to Qodo so the Spec Agent can use documentation stored in Confluence when reviewing pull requests. By default, Qodo looks for a Confluence link in the pull request description. When the description contains a Confluence page URL, the Spec agent compares the implementation against the requirements in that page. Qodo can also follow one additional hop. If the pull request description links to a ticket, such as a Jira or Linear ticket, and the ticket description contains a Confluence page URL, Qodo can use that page as the specification. A Confluence URL directly included in the pull request description takes precedence over a Confluence page found through a linked ticket.
If your existing Confluence integration cannot read pages, disconnect and reconnect the integration in the Qodo portal to refresh its permissions.

​
Prerequisites

Before connecting Confluence, ensure you have:
  • Confluence administrator permissions.
  • A Git provider connected to Qodo and the Qodo app installed. For more information, see Install Qodo.

​
Integrate Confluence with Qodo

  1. Log in to the Qodo portal.
  2. Navigate to Integrations > Documentation & design.
  3. Under Confluence, click + Add connection.
  4. Sign in to your Atlassian account.
  5. Select the Confluence workspace you want to connect.
  6. Review the requested permissions and click Allow.
  7. After authorization completes, the integration status changes to Connected. Confluence integration with Connected status
When you connect Confluence, Qodo automatically enables the Spec agent. You do not need to enable it manually.

​
Verify the integration

After connecting Confluence:
  1. Create or update a Confluence page that contains product requirements, technical specifications, or implementation details.
  2. Create or update a pull request in a repository connected to Qodo, and add a link to the relevant Confluence page in the PR description.
  3. Wait for the Qodo review to complete.
  4. Open the Qodo Review Results in the pull request.
When a pull request includes a specification link in its description, the Spec agent analyzes the implementation against the requirements in the linked page and generates 📎 Requirement gap findings as part of the review. Pull request with Qodo Review Results and a Requirement gap finding For more information about requirement gap findings, see View requirement gaps in your findings.

​
Troubleshooting

​
No documentation findings appear

If you do not see documentation-based findings in the pull request review:
  • Verify that the PR description contains a link to the relevant Confluence page.
  • Verify that the Confluence integration is connected in the Qodo portal.
  • Verify that the repository is connected to Qodo through your Git provider.
  • Verify that the Spec Agent is enabled.
  • Ensure the pull request has completed a Qodo review.
  • Confirm that the relevant documentation exists in Confluence.
Not every pull request produces documentation findings. The Spec agent generates requirement gaps only when it identifies documentation that is relevant to the changes in the pull request and detects missing or incomplete implementation.