Skip to main content
The Confluence API tool gives Neo agents direct access to the Atlassian Confluence Cloud REST API — list spaces, fetch and edit page content, manage attachments, search with CQL, and create new pages on behalf of customers.
Automatically enabled when you configure Confluence permissions in your agent workflow. No manual toggle needed. See the Confluence integration page for connection setup.

​
What It Does

  • List spaces (knowledge bases, global, personal)
  • Fetch full page content in storage XHTML or Atlassian Document Format (ADF)
  • Create, update, and delete pages and blogposts
  • Manage attachments on pages and blogposts (upload, delete)
  • Add, update, or remove labels on pages and spaces
  • Create comments on pages
  • Look up users (resolve @mentions and author IDs to display names)
  • Run CQL (Confluence Query Language) searches across all content the agent can see

​
Permission Groups

Each group can be set to Disabled, Read Only, or Read/Write. When set to Read/Write, an additional Allow Delete toggle controls whether the agent can issue DELETE requests on that group.

​
Access Profiles

All five groups Read Only. The agent can browse anything the connecting OAuth user has Confluence permission to see — but cannot make changes. The typical setting for documentation-aware ticket-resolution agents.
Pages and Attachments Read/Write; Spaces, Search, and Users Read Only. The agent can create and update pages and upload attachments — ideal for agents that maintain runbooks and client documentation autonomously — but cannot restructure spaces or delete records.
All five groups Read/Write with Allow Delete enabled. The agent can create, update, and delete pages, blogposts, comments, labels, and attachments. Whole-space DELETE is still structurally blocked (see Safety Controls).

​
Safety Controls

​
How to Configure

1

Connect Confluence

Connect Confluence from the Neo dashboard. The flow is a single click + Atlassian consent — no developer app to register.
2

Configure permissions on the agent

In your agent workflow’s Integrations tab, choose an access profile (Read Only, Documentation Manager, Full Access) or customize each permission group individually.
Start with Read Only when you just need an agent that surfaces documentation during ticket resolution. Move to Documentation Manager when you want the agent to maintain its own runbooks. Only enable Full Access + Allow Delete after validating the agent’s write behavior on a test workflow first.