Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt

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

Neo Agent integrates with Atlassian Confluence Cloud to automatically synchronize your spaces and pages, and to give agents direct API access to your Confluence content. Once connected, Neo indexes your knowledge base for search, and agents can search and read Confluence pages during ticket resolution.
One-click connection. Connecting Confluence takes about 30 seconds. There’s nothing to install on your side and no developer account to set up — just sign in to Atlassian and grant access.

​
Connect Confluence

1

Open the Integrations page

In the Neo Dashboard, open Integrations → find the Confluence tile in the Documentation section and click it.
2

Click Connect Confluence

A popup opens to auth.atlassian.com with a consent screen showing the permissions Neo is requesting.
You’ll see a small “unverified app” notice from Atlassian. That’s expected — it appears for any OAuth integration not listed in the Atlassian Marketplace. Your data is still protected by the standard OAuth flow and the permissions you grant.
3

Sign in and pick your site

Sign in with the Atlassian account that has access to the Confluence site you want to connect.If your account has access to multiple Atlassian sites, you’ll see a dropdown to choose which site to authorize.Click Accept to grant the permissions.
4

Done

The popup closes and the dashboard flips to a green “Confluence connected” card showing your site URL.
Neo automatically starts the first sync. The next scheduled sync also kicks in so your pages stay current without manual action.

​
Multiple Atlassian sites

If your Atlassian account has access to more than one site and you granted access to several during consent, Neo shows a picker right in the dashboard with the site name, URL, and cloud ID for each. Pick the one Neo should sync. You can change your mind later by clicking Disconnect and reconnecting against a different site.

​
What gets synced

ContentStatus
Pages in knowledge bases and global spacesSynced — title, body, author, last modified, labels
Personal spacesSkipped — these are per-user, not organizational documentation
Drafts and trashed pagesSkipped
AttachmentsMetadata only (file name, URL) — file contents not indexed
CommentsNot synced
Page bodies are converted to clean text for search — headings, lists, tables, code blocks, and panels are all preserved. Labels become searchable tags, and Atlassian user IDs are resolved to display names so “created by” shows the person’s actual name. Once synced, your Confluence content is searchable alongside ITGlue, Hudu, and any other documentation sources you’ve connected.

​
Re-sync and trigger sync manually

Neo re-syncs Confluence on a schedule automatically. To pull in changes immediately:
  1. Open the Confluence tile in Integrations.
  2. Click Trigger sync.
The status row shows the progress of the current run. You can also click the refresh icon to re-check status.

​
Agent access to Confluence

When you enable the Confluence API tool on an agent, it can search and read Confluence content directly while resolving tickets. Agent access is read-only — agents can browse pages and run searches but can’t edit, delete, or create Confluence content. This is enforced at the tool level regardless of what Atlassian permissions Neo holds.

​
Permission groups

You can scope agent access by toggling individual permission groups:
Permission GroupWhat it controls
PagesRead pages and blogposts (body, version, parent/child links)
SpacesList and read space metadata
SearchRun CQL search across pages, blogposts, attachments
AttachmentsRead attachment metadata on pages and blogposts
UsersResolve user profiles for content authors

​
Quick-start profiles

Read Only

All 5 groups enabled. The agent can browse anything the connecting user has Confluence permission to see — the typical setting.

Search Only

Only Search enabled. The agent surfaces matches via CQL but doesn’t fetch page bodies directly — minimal exposure when you only want Confluence as a discovery surface.

​
Disconnect

Open the Confluence tile and click Disconnect. This clears Neo’s stored tokens and turns off Confluence sync. Your Confluence data and pages aren’t affected. If you also want to revoke Neo’s grant on the Atlassian side, visit id.atlassian.com/manage-profile/apps and remove the Neo Agent entry.

​
Reconnect

Click Reconnect to refresh the OAuth grant — useful if Neo notifies you that the connection has expired or you want to re-grant permissions. The flow is identical to the initial connect.

​
Security

  • Tokens are stored in Azure Key Vault, encrypted at rest, never logged in plaintext.
  • Refresh tokens rotate every time Neo refreshes its access — the previous token is invalidated immediately.
  • Agent access is read-only and enforced at the tool layer regardless of the OAuth scopes Neo holds.
  • All API traffic is over HTTPS.
  • You can revoke Neo’s access at any time from id.atlassian.com/manage-profile/apps.