Confluence Integration

The Confluence integration lets your company connect Atlassian Confluence Cloud to IntuitivePM. Use it when Confluence pages should become trusted context for agent workflows without giving agents Atlassian credentials.

With Confluence connected, company admins can:

• Connect Confluence through Atlassian OAuth.
• Discover Confluence spaces.
• Enable only the spaces IntuitivePM may use.
• Search and preview pages from enabled spaces.
• Let approved agents read selected Confluence pages through IntuitivePM.
• Review audit events that show which page an agent read.

How It Works

IntuitivePM connects to Confluence through Atlassian OAuth. The Atlassian token is stored and used by IntuitivePM on the server side. Users and agent runtimes never receive Atlassian credentials.

When an agent needs Confluence context, IntuitivePM checks the workflow lease, selected Knowledge Source, enabled space, configured page or page search, and active company. IntuitivePM then reads the selected page through the server-side gateway, converts it to sanitized Markdown, records citations and content hashes, and gives the agent only the scoped context for its current task or workflow run.

Confluence write-back is not enabled yet. Agents can read approved pages, but they cannot edit, delete, comment on, or publish Confluence content.

Prerequisites

• An Atlassian Cloud site with Confluence.
• Company admin access in IntuitivePM.
• Confluence enabled for your IntuitivePM company.
• Permission in Atlassian to authorize the IntuitivePM app.
• Access to the Confluence spaces and pages you want IntuitivePM to use.
• Agent orchestration enabled if you want agents to use Confluence pages as workflow context.

Connect Confluence

1. Open System -> Integrations -> Integration Hub.
2. Open Confluence.
3. Review the connector boundary checklist.
4. Select Connect Confluence.
5. Sign in to Atlassian when prompted.
6. Review and approve the requested permissions.
7. Return to IntuitivePM after the OAuth flow completes.

After connection, the Confluence card shows connection status. Open the Confluence details to inspect connection health, connected user, token expiry, enabled spaces, permission drift, and recent operational events.

Enable Spaces

Confluence spaces are disabled by default after connection. This prevents agents from reading a whole Confluence site just because OAuth succeeded.

To enable Confluence content:

1. Open System -> Integrations -> Integration Hub.
2. Open Confluence.
3. Select the Confluence connection.
4. Sync spaces.
5. Enable only the spaces IntuitivePM may use.

Use the narrowest practical space scope. If only one project needs Confluence context, enable the project space instead of broad company-wide spaces.

Preview Pages

Admins can search and preview pages from enabled spaces before attaching the source to a workflow.

1. Open the Confluence details.
2. Select an enabled space.
3. Enter a page-title search term when needed.
4. Select Search pages.
5. Select a page to preview the sanitized Markdown, content hash, warnings, citation metadata, and attachment metadata.

Previewing pages confirms that IntuitivePM can read the selected page through the backend gateway. It does not expose Atlassian tokens to the browser or to agents.

Use Confluence As A Knowledge Source

Company admins can create Confluence Knowledge Sources for workflow nodes.

1. Open AI Agents -> Knowledge Sources.
2. Select New Source.
3. Choose Confluence.
4. Select the Confluence connection.
5. Select the enabled space.
6. Select a specific page or configure bounded page discovery for the node.
7. Save the source.
8. Attach the source to a workflow node that needs that Confluence context.

Confluence Knowledge Sources are most useful for project requirements, technical runbooks, policy pages, implementation notes, customer documentation, and decision records that agents should cite while working.

What Agents Can Read

Agents can receive scoped Confluence page context for the work they are assigned to.

Runtime reads currently include:

• Page title and metadata.
• Sanitized page body as Markdown-like text.
• Citation metadata.
• Content hash.
• Attachment metadata such as file name, MIME type, size, and version.
• Extracted attachment text for supported text, Markdown, CSV, JSON, XML, PDF, DOCX, and XLSX files.

Attachment files are read through IntuitivePM’s backend proxy. Agents do not receive Atlassian download links or credentials. Unsupported binary files, archives, executables, unknown file types, and attachments larger than 10 MiB are blocked by default.

Agents receive page context, source metadata, citations, and content hashes. They do not receive Atlassian credentials and they do not browse Confluence directly.

Audit Source Reads

Company admins can review Confluence source activity from the Confluence connection details and from connector audit diagnostics.

Audit filters can narrow events by:

• Confluence connection.
• Space key.
• Page ID.
• Action.
• Actor type.
• Source type.
• Time window.

This is useful when you need to answer questions such as:

• Did an agent read a Confluence page during a workflow run?
• Which enabled space did the read come from?
• Which page was read?
• Which attachment was read?
• Which agent, runtime, task, or workflow run was involved?
• How much content was returned?

Detailed connector read-audit rows are kept for 180 days by default.

Security Model

IntuitivePM uses these guardrails for Confluence:

• Atlassian credentials stay on the IntuitivePM server.
• Agent runtimes never receive OAuth tokens.
• Confluence reads are scoped to the active company, connection, workflow, node, and lease.
• Spaces are disabled until an admin enables them.
• Source content is treated as untrusted data and sanitized before agents use it.
• Runtime page and supported attachment reads return citations and content hashes.
• Runtime attachment reads are capped at 10 MiB and remain behind company rollout controls.
• Confluence write-back is not enabled in the current rollout.
• Confluence reads and operational events are auditable.

Troubleshooting

Recommended Setup

For most teams:

1. Connect Confluence from the Integration Hub.
2. Enable only one pilot space.
3. Preview one or two pages from that space.
4. Create a Confluence Knowledge Source from a specific page.
5. Attach it to a low-risk workflow node.
6. Run a test task and confirm the answer includes citations.
7. Review audit events before enabling more spaces.

Related Guides

• Integration Hub
• Agent Orchestration
• Assign Work To Agents
• Jira Integration
• SharePoint Integration