Confluence Toolset

Wiki pages, documentation, and knowledge management

ReadyAtlassian

Overview

The Confluence toolset enables AI agents to interact with your Confluence workspace. Agents can create pages, update content, search documentation, manage spaces, and add comments. This toolset is ideal for automating documentation workflows and making knowledge accessible through conversational AI.

Key Capabilities

Create and update pages - Create new documentation, update existing pages
Search content - Full-text search across pages and blog posts
Space management - List spaces, get space details
Page hierarchy - Navigate child pages, version history
Comments - Add comments to pages

Available Tools

Tool	Description
`create_page`	Create a new page in a space
`update_page`	Update page title and/or content
`update_page_title`	Update only the page title
`get_page_content`	Get content of a specific page
`get_pages_in_space`	Get all pages in a space
`get_child_pages`	Get child pages of a parent page
`search_pages`	Search pages by title
`search_content`	Full-text search across all content
`get_spaces`	Get all accessible spaces
`get_space`	Get details of a specific space
`get_page_versions`	Get version history of a page
`comment_on_page`	Add a comment to a page

Configuration Guide

The Confluence toolset supports two authentication methods. In both, an admin first configures the shared instance under Workspace Settings → Actions, then each user connects their personal account under Your actions.

Method	Best for
OAuth 2.0 (3LO)	Multi-user / org-wide rollouts. One Atlassian app, per-user consent via OAuth popup.
API Token	When you cannot register an Atlassian OAuth app, or you want per-user tokens. Each user provides their own Email + API Token.

OAuth 2.0
API Token

Step 1: Access the Atlassian Developer Console

Go to developer.atlassian.com/console/myapps/ and sign in with your Atlassian account (must have admin access to your Confluence workspace).

You can use the same Atlassian OAuth application for both Jira and Confluence toolsets — just add the relevant API permissions to it.

Step 2: Create an OAuth 2.0 integration (if needed)

Click Create in the top-right corner.
Select OAuth 2.0 integration.
Enter a name (e.g., PipesHub Confluence Toolset) and accept the developer terms.
Click Create.

Step 3: Get the Redirect URI from PipesHub

Before configuring the Callback URL in Atlassian, copy the Redirect URI from PipesHub.

In PipesHub, go to Workspace Settings → Actions.
Find Confluence in the list and click + Setup for a new instance.
Copy the Redirect URI shown in the dialog.

PipesHub Configure Confluence toolset — copy the Redirect URI

Step 4: Configure the Callback URL in Atlassian

In Atlassian Developer Console, click Authorization in the left sidebar.
Click Add under OAuth 2.0 (3LO).
Paste the Redirect URI from PipesHub into the Callback URL field.
Click Save changes.

The Callback URL must match exactly. Any mismatch — trailing slash, protocol, casing — will cause authentication to fail.

Step 5: Add required scopes

In the left sidebar, click Permissions.
Add scopes for both User identity API and Confluence API.

User Identity API

Scope	Description
`read:account`	View user profiles (required for user identification)

Confluence API — Classic scopes

Scope	Description
`read:confluence-content.all`	Read all Confluence content
`write:confluence-content`	Create and update pages
`read:confluence-content.summary`	Read content summaries
`read:confluence-props`	Read content properties
`read:confluence-space.summary`	Read space summaries
`read:confluence-user`	Read user information
`read:confluence-groups`	Read group information
`search:confluence`	Search Confluence content

Confluence API — Granular scopes

Scope	Description
`read:content-details:confluence`	View content details and properties
`read:page:confluence`	View page content
`write:page:confluence`	Create and update pages
`read:blogpost:confluence`	View blog post content
`read:attachment:confluence`	View and download attachments
`read:comment:confluence`	View comments
`write:comment:confluence`	Create comments on pages
`delete:comment:confluence`	Delete comments
`read:space:confluence`	View space details
`read:user:confluence`	View user details
`read:group:confluence`	View groups and memberships
`read:permission:confluence`	View content restrictions
`read:audit-log:confluence`	View audit records
`read:folder:confluence`	View folder data
`read:email-address:confluence`	View user email addresses

Step 6: Copy Client ID and Client Secret

In the left sidebar, click Settings.
Under Authentication details, copy:
- Client ID — used as Client ID in PipesHub.
- Secret — used as Client Secret in PipesHub.

Step 7: Admin — configure the toolset in Actions

In PipesHub, return to Workspace Settings → Actions, find Confluence, and reopen the setup dialog.
Confirm the Redirect URI matches the Callback URL you saved in Atlassian in Step 4.
Enter:
- Instance Name (e.g., Confluence Production)
- Client ID — from Step 6
- Client Secret — from Step 6
- Atlassian Site URL — your Confluence site URL (e.g., https://your-domain.atlassian.net; no trailing slash)
Click Create.

Enter Client ID, Client Secret, and Atlassian Site URL in PipesHub

Atlassian Site URL is an org-level field — it points to the specific Confluence Cloud site this toolset instance will act on. Client ID and Client Secret are the org’s OAuth app credentials. Per-user tokens are issued by Atlassian when each user authenticates in the next step.

Step 8: Authenticate the toolset

Authentication uses the same OAuth flow in either location:

Admins can authenticate the shared instance directly under Workspace Settings → Actions.
Users can authenticate their own personal instance under Your actions (in the Personal section of the sidebar).

On the Confluence tile (in Actions or Your actions), click Authenticate with OAuth.
A popup opens to Atlassian’s authorization page — select your Confluence site from the dropdown.
Review the permissions and click Accept.

The popup closes and the Confluence tile shows Authenticated status.

Authorize using the same email as your PipesHub account. Using a different email causes permission issues on the PipesHub platform.

Step 9: Add Confluence to an agent

Go to the Home page.
Next to Agents, click + to create a new agent.
Give the agent a name, drag the Confluence toolset onto the canvas, connect it to the Agent Core node with your model and chat input/output, then create the agent.

Agent builder with Confluence toolset connected

The API Token method has a clear org/user split:

Admin configures only the Atlassian Site URL under Actions (org-level field).
Each user then opens Your actions and enters their own Email + API Token to authenticate the toolset for themselves.

This is different from the connector — here every user that wants to use the toolset needs their own API token, since each agent action runs under that user’s identity.

Step 1: Each user generates an API token in Atlassian

Each user that will use the toolset must generate their own API token.

Sign in to id.atlassian.com/manage-profile/security/api-tokens.
Click Create API token, set a meaningful label (e.g., PipesHub Confluence Toolset) and an expiry if you want, then click Create.

Atlassian shows the token once — click Copy and store it securely.

The API token is shown only once. If you close the dialog without copying it, create a new token.

Step 2: Admin — configure the toolset instance in Actions

The admin sets up only the org-level field (the Atlassian Site URL). No credentials are entered here — those come from each user in the next step.

In PipesHub, go to Workspace Settings → Actions.
Find Confluence and click + Setup for a new instance.
In the dialog, choose API Token as the authentication method, then enter only:
- Instance Name (e.g., Confluence Production)
- Atlassian Site URL — your Confluence site URL (e.g., https://your-domain.atlassian.net; no trailing slash)
Click Create.

Admin Actions dialog — API Token method shows only Instance Name and Atlassian Site URL

Clicking the instance settings later reopens this drawer where you can change Instance Name and Atlassian Site URL. A button below opens Your actions so each user can add their own credentials.

Step 3: Each user — add Email + API Token in Your actions

Each user that wants to use the toolset must complete this step with their own credentials.

In PipesHub, open Your actions (in the Personal section of the sidebar).
Find the Confluence instance and open it.
Enter:
- Email — your Atlassian account email (the account that created the API token in Step 1)
- API Token — the token you copied in Step 1
Click Save credentials.

Your actions — enter Email and API Token

The Confluence tile in Your actions now shows Authenticated. The toolset is connected for this user only — every other user must repeat Step 3 with their own email + token.

The Email must match the Atlassian account that owns the API token. Using a different email causes authentication to fail.

Step 4: Add Confluence to an agent

Go to the Home page.
Next to Agents, click + to create a new agent.
Give the agent a name, drag the Confluence toolset onto the canvas, connect it to the Agent Core node with your model and chat input/output, then create the agent.

FAQ

Which authentication method should I choose?

	OAuth 2.0	API Token
Best for	Multi-user / org-wide rollouts	Cases where OAuth app registration is blocked
Org-level setup	Client ID, Client Secret, Atlassian Site URL	Atlassian Site URL only
Per-user setup	OAuth popup (one click)	Each user pastes Email + API Token
Prerequisites	Atlassian Developer Console admin access	Any Atlassian account

Choose OAuth for the simplest per-user experience. Choose API Token when you cannot register an Atlassian OAuth app or when each user wants to manage their own token.

What's the difference between Confluence Connector and Confluence Toolset?

Aspect	Confluence Connector	Confluence Toolset
Purpose	Sync and index Confluence data for search	Enable agents to perform actions in Confluence
Data Flow	One-way (import data into PipesHub)	Two-way (read and write via API)
When to Use	Query/search pages, spaces, blog posts	Create pages, update content, manage spaces

Example: Use Confluence Connector to search and retrieve documentation. Use Confluence Toolset to let agents create or update Confluence pages.

Usage Tips

How do I create a page?
Ask your agent to “create a Confluence page” and provide the space name, page title, and content. The agent will handle the HTML formatting automatically. How do I search for pages?
Simply ask to “search Confluence for [topic]”. You can search across all spaces or specify a particular space. How do I update a page?
Ask to “update the [page name]” and provide the new content. The entire page content will be replaced with your update. How do I find space IDs?
Ask the agent to “list all Confluence spaces” to see available spaces and their IDs before creating pages.