Skip to main content
Import pages from Atlassian Confluence Cloud into AGO. The connector fetches pages recursively from a root page, converts HTML to Markdown, downloads attachments, and rewrites internal Confluence links to AGO links.

​
Prerequisites

  1. Access to Confluence Cloud
  2. An API token with read access to the spaces you want to import
  3. The root page ID for your import (the top of the page tree)

​
Generating an API Token

Confluence Cloud:
  1. Go to Atlassian Account Settings
  2. Click Create API token
  3. Give your token a label (e.g., “AGO Integration”)
  4. Copy the token immediately (you won’t be able to see it again)
This connector uses the Confluence Cloud API with an email address and API token. Confluence Data Center and its personal-access-token flow are not supported.

​
Finding Your Root Page ID

Navigate to the page you want as your root and look at the URL:
The number 123456789 is your page ID. You can also find it via the page’s ... menu > Page Information.

​
Setup Steps

​
1. Configure Confluence Credentials

In your AGO admin interface, go to Knowledge → Connections → Confluence and configure your connection:

​
2. Create a Knowledge Source

  1. Navigate to Knowledge > Sources > Create
  2. Select Confluence as the connector type
  3. Enter the Root Page ID — the starting page for recursive import
  4. Name your source (e.g., “Product Documentation”)
  5. Save and run a manual sync
The connector will import the root page and all child pages beneath it, preserving the hierarchy.

​
3. Import Multiple Spaces

Create a separate source for each Confluence space or section. For example, create one source for “Product Docs” pointing to one root page, and another for “Engineering Wiki” pointing to a different root page.

​
What Gets Imported

The connector processes each page through these steps:
  1. Fetches HTML content from Confluence
  2. Converts Confluence emoticon images to Unicode emojis
  3. Converts HTML to Markdown (tables, lists, code blocks preserved)
  4. Downloads attachments if the page version changed
  5. Rewrites internal Confluence links to AGO documentation links
  6. Stores the page with its position in the hierarchy
Each sync fetches and updates page content. When a page version is unchanged, its attachments are not downloaded again.

​
Filtering

The connector imports all pages under the root page. To import only a specific section:
  • Set the root page ID to the top of that section instead of the entire space homepage
  • Create separate sources for different sections you want to import independently

​
Best Practices

  • Archive outdated pages in Confluence before importing
  • Select a root page that represents the top of your documentation tree — avoid the space homepage if it includes unwanted sections
  • Start with a small space to verify formatting before importing large ones
  • Schedule regular syncs (daily or weekly) to keep content fresh
  • For large spaces (500+ pages), split into multiple sources by section

​
Troubleshooting

  • Verify your API token is correct and not expired
  • Check the email address matches the token owner
  • Ensure the user has read permission for the space
  • Verify the root page ID is correct
  • Check the page hasn’t been deleted or moved
  • Verify the attachments are accessible to the API user
  • Attachments are downloaded again when the Confluence page version changes; after updating the page, run another sync
  • Some Confluence macros don’t have a Markdown equivalent and may not convert cleanly
  • Test with simpler page content first to isolate the issue