Confluence Connector

Connect your Confluence Cloud workspace to upload and process pages directly as an external knowledge base. Supports page content and attachments (PDFs, Office files, text files, images, and more). Authentication is handled via Atlassian OAuth 2.0 with automatic token refresh.

Setup

Step 1: Create an OAuth 2.0 App in Atlassian

Go to developer.atlassian.com/console/myapps and click Create > OAuth 2.0 integration
Under Authorization, add a callback URL:
- Local: http://localhost:7091/api/connectors/callback?provider=confluence
- Production: https://yourdomain.com/api/connectors/callback?provider=confluence

Step 2: Configure Permissions

In your app settings, go to Permissions and add the Confluence API. Enable these scopes:

read:page:confluence
read:space:confluence
read:attachment:confluence

Step 3: Get Your Credentials

Go to Settings in your app to find the Client ID and Secret. Copy both.

Step 4: Configure Environment Variables

Add to your backend .env file:


CONFLUENCE_CLIENT_ID=your-atlassian-client-id
CONFLUENCE_CLIENT_SECRET=your-atlassian-client-secret

Add to your frontend .env file:


VITE_CONFLUENCE_CLIENT_ID=your-atlassian-client-id

Variable	Description	Required
`CONFLUENCE_CLIENT_ID`	Client ID from your Atlassian OAuth app	Yes
`CONFLUENCE_CLIENT_SECRET`	Client secret from your Atlassian OAuth app	Yes
`VITE_CONFLUENCE_CLIENT_ID`	Same Client ID, used by the frontend to show the Confluence option	Yes
`CONNECTOR_ALLOWED_ORIGINS`	Comma-separated frontend origins allowed to receive the sign-in result, e.g. `https://docsgpt.example.com`. Not needed when the frontend shares the API origin, or in local dev when the callback is on `localhost`/`127.0.0.1` and the frontend runs on port 5173	When the frontend is on its own origin

Step 5: Restart and Use

Restart your application, then go to the upload section in DocsGPT and select Confluence as the source. You’ll be redirected to Atlassian to sign in, then can browse spaces and select pages to process.

Troubleshooting

Option not appearing — Verify VITE_CONFLUENCE_CLIENT_ID is set in the frontend .env, then restart.
Sign-in popup closes but the account never connects — The frontend origin is not allowed to receive the result. Add it to CONNECTOR_ALLOWED_ORIGINS in the backend .env.
Authentication failed — Check that the callback URL matches exactly, including ?provider=confluence.
No accessible sites — Ensure the authenticating user has access to at least one Confluence Cloud site.
Permission denied — Verify that the Confluence API scopes are enabled in your Atlassian app settings.