Skip to main content
You’ll create: an incoming OAuth 2.0 application link in Confluence Data Center. We’ll be able to read: page content and space information that the connecting user can already see in Confluence.
This connector is for self-hosted Confluence Data Center. For Atlassian-hosted Confluence, use the Confluence connector. The two are configured independently and can be enabled side by side.

​
Requirements

  • Confluence Data Center 7.12 or later — the incoming OAuth 2.0 application link this connector uses does not exist in earlier releases. Voltai does not check the version; if the External application → Incoming option is missing from your admin UI, your instance is too old.
  • The instance is served over HTTPS and reachable from Voltai at its base URL — for example https://wiki.example.com, or https://intranet.example.com/confluence when Confluence runs under a context path.
  • A Confluence administrator to create the application link.

​
Steps

1

Open application links

In Confluence, go to Administration → General configuration → Application links and click Create link.
2

Choose an incoming external application

Select External application, then Incoming, and continue.
3

Name it and set the redirect URL

Give it a name (for example, “Voltai”) and set Redirect URL to the redirect URI.
4

Grant read permission

Under Permission, choose Read. Voltai never requests write access.
5

Copy the credentials

Save. Confluence shows a Client ID and Client secret. They remain visible in the application link’s details if you need them again later.

​
Send us

​
Things to know

  • Each user connects individually from Settings → Integrations and approves read access on Confluence’s own consent screen. Results are limited to what that user can already see in Confluence.
  • Voltai requests the READ scope only and renews tokens automatically. It searches pages with CQL and reads page bodies as plain text.
  • Page attachments are not fetched. Only the page body is read, so a diagram or spreadsheet attached to a page is not visible to the assistant. This matches the Atlassian-hosted Confluence connector and differs from Jira Data Center, which does read issue attachments.
  • Very long pages are truncated before the assistant sees them, so a large page may be cited from its earlier sections only.
  • Searches match space keys (for example ENG), not space display names.
  • If the application link is deleted or a user’s Confluence account is deactivated, that user’s Integrations card shows Connection expired with a Reconnect button.

​
Troubleshooting

We have not yet stored your base_url and credentials. Send them to your Voltai contact using the table above.
Confluence no longer accepts the stored token. Click Reconnect. If it fails again, ask your Confluence admin to confirm the application link still exists.
A 404 usually means the base_url we hold is missing the context path (for example /confluence). Confirm the value with your Voltai contact. Missing results otherwise reflect your own Confluence permissions.