> ## Documentation Index
> Fetch the complete documentation index at: https://docs.woes.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Confluence Integration

> Connect Confluence and import selected spaces into the Woes Context Library.

# Confluence Integration

<img src="https://mintcdn.com/woes/SjmqB9Aiw359c6aC/images/integrations/confluence-logo.svg?fit=max&auto=format&n=SjmqB9Aiw359c6aC&q=85&s=b32af64b008fd584d834f39557b1cf54" alt="Confluence logo" width="56" height="56" data-path="images/integrations/confluence-logo.svg" />

Confluence is a live context integration for teams that keep support runbooks,
implementation notes, release guidance, or internal troubleshooting pages in
Atlassian Confluence.

When you connect Confluence, Woes can import readable pages from selected spaces
into the Context Library. Operators can inspect that source, and agents can use
approved Confluence-backed context alongside API specs, docs sites, GitHub
repositories, Notion pages, and pasted source content.

## At A Glance

| Use Confluence for                                                                              | Where it appears                                                               |
| ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| Support runbooks, implementation notes, troubleshooting guides, and internal product knowledge. | Integrations, Context Library, agent source selection, and retrieved evidence. |

## What It Does

The Confluence integration helps support teams make practical internal
knowledge searchable in Woes:

* Import selected Confluence spaces one at a time.
* Convert readable pages into clean support context.
* Preserve source links back to Confluence pages.
* Show imported spaces as sources in the Context Library.
* Let operators review source coverage before agents use it.

## What Gets Imported

Woes imports readable page content from the Confluence space you select. Good
spaces include:

* API support runbooks.
* Setup and migration notes.
* Known issue and troubleshooting pages.
* Internal escalation guidance.
* Release notes that explain customer-facing behavior.

Woes does not turn Confluence into a customer channel. It adds source material
that can help operators and approved agents answer with better evidence.

## Setup

<Steps>
  <Step title="Open Integrations">
    In Woes, go to **Workspace Settings -> Integrations**.
  </Step>

  <Step title="Connect Confluence">
    Find **Confluence** and click **Connect**. You will be sent to Atlassian to
    approve access.
  </Step>

  <Step title="Choose a site">
    Select the Atlassian site that contains the spaces your support team uses.
  </Step>

  <Step title="Import a space">
    Return to Woes, open the Confluence integration, choose a space, and click
    **Import selected space**. Repeat this step for any additional spaces.
  </Step>

  <Step title="Review in Context">
    Open the Context Library to inspect imported pages, coverage, and source
    health.
  </Step>

  <Step title="Attach to agents">
    Attach the imported Confluence source only to agents that should answer from
    that material.
  </Step>
</Steps>

## Where It Appears In Woes

| Surface                            | What you do there                                                                    |
| ---------------------------------- | ------------------------------------------------------------------------------------ |
| Workspace Settings -> Integrations | Connect, reconnect, disconnect, list spaces, and import a selected Confluence space. |
| Context Library                    | Review imported Confluence sources, inspect pages, and manage source health.         |
| Agents                             | Attach Confluence sources to agents that should retrieve that material.              |
| Inbox                              | Operators can review retrieved evidence when an agent uses imported context.         |

## Permissions And Access

Woes only lists Confluence spaces available to the authorized Atlassian
connection. If a space does not appear, confirm the user who connected
Confluence can access that space in Atlassian.

Disconnecting Confluence stops new space listing and imports. Already imported
Woes context sources remain in the Context Library until an admin deletes them.

<Warning>
  Only import Confluence pages that are safe for your Woes support workspace to
  use as context. Do not import pages containing passwords, private customer
  secrets, access tokens, or content that agents should never retrieve.
</Warning>

## Maintaining Confluence Context

* Re-import spaces after important runbook, release, or troubleshooting changes.
* Keep pages focused and support-ready.
* Remove outdated Confluence sources when they should no longer influence
  support workflows.
* Attach Confluence sources only to agents that should use that internal
  material.

## Troubleshooting

| Issue                                     | What to check                                                                               |
| ----------------------------------------- | ------------------------------------------------------------------------------------------- |
| A space does not appear                   | Confirm the connected Atlassian user can access the space, then refresh the space list.     |
| Imported context is too vague             | Improve headings, examples, troubleshooting steps, and links in Confluence, then re-import. |
| The wrong agent is using a space          | Open the agent and remove the Confluence source from agents that should not use it.         |
| A disconnected site still has old sources | Delete the imported source from Context if Woes should no longer use it.                    |

## Related Docs

* [Sources](/context/sources)
* [Knowledge Base Overview](/knowledge-base/overview)
* [Agents](/agents/overview)
* [Context Learning](/agents/context-learning)