Skip to main content

Documentation Index

Fetch the complete documentation index at: https://www.bugzy.ai/docs/llms.txt

Use this file to discover all available pages before exploring further.

Confluence integration gives Bugzy read-only access to your team’s documentation. When generating test plans or exploring your application, the documentation-researcher subagent searches Confluence pages for product specs, requirements, and feature descriptions — producing more accurate and comprehensive tests.

​
What Confluence enables

  • Documentation search — Bugzy searches Confluence pages using CQL (Confluence Query Language) for product context
  • Page content retrieval — Full page content is read and used during test planning and generation
  • Space browsing — The agent can list spaces and navigate page hierarchies
Confluence integration is read-only. Bugzy searches and reads pages but never creates or modifies content.

​
Setup

1

Navigate to connections

Go to Dashboard > Projects > [Your Project] > Connections.
2

Connect Confluence

Click Connect Confluence. This opens the Atlassian OAuth flow managed by Nango.
3

Authorize access

Select your Atlassian site and grant the requested permissions.
4

Access is automatic

Confluence OAuth grants access to all spaces the connected user can see. No additional sharing configuration is needed.

​
Access model

Unlike Notion’s per-page sharing model, Confluence uses the connected user’s existing permissions:
  • The connected user’s Confluence permissions determine what Bugzy can access
  • Connect as a user with read access to the spaces Bugzy should search
  • Space-level restrictions are respected — Bugzy cannot access restricted spaces the connected user cannot see

​
What the agent can do

ActionDescription
Search pagesSearch with CQL queries or plain text across all accessible spaces
Read page contentRetrieve full page content converted to plain text
List spacesBrowse available Confluence spaces
Navigate childrenList child pages under a parent page

​
Troubleshooting

Permission errors (403) — The connected user does not have access to the requested space or page. Verify the user has read permissions in Confluence, or reconnect with a user who has broader access. No search results — Verify the space key is correct in queries. Ensure content exists and is not in a restricted space the connected user cannot see. “Forbidden” errors — The OAuth token may lack required permissions. Disconnect and reconnect Confluence from the project connections page to re-authorize.