Skip to content

Confluence Sync

This guide explains how to set up a connection between your SmartChat space and a Confluence Data Center instance. Once connected, SmartChat automatically syncs the Confluence pages so they become searchable and available as context for your conversations.

  • You need the Space Owner role in the SmartChat space. See Admin Panel Roles for details.
  • A service account token or personal access token (PAT) from the Confluence server you want to sync. Ask your Confluence administrator if you are unsure how to obtain one.

Go to the SmartChat Admin Panel and select the space you want to configure using the space selector dropdown in the top right.

In the left sidebar under Manage, click Data Connections. You will see a table listing all existing connections for this space (initially empty).

Admin Panel — Space members view

Data Connections page

Click the + Create connection button in the top right corner. A form will appear with the following fields:

Create connection form

Fill in the fields as follows:

FieldDescription
Connection TypeSelect Confluence.
NameA name for your connection (no spaces or special characters allowed).
URLThe base URL of your Confluence instance, e.g. https://strive.devops.t-systems.net/confluence/
KeyThe Confluence space key to sync. This is the short prefix that appears in Confluence URLs. For example, if your pages have URLs like https://strive.devops.t-systems.net/confluence/spaces/AIFS/pages/..., the space key is AIFS.
Credential TypeSelect Basic Auth.
Credential AuthorizationSelect Read.
UsernameThe username of the service account or personal account.
SecretThe corresponding password or access token.

Click Save when you are done.

Step 4 — Accept the data privacy disclaimer

Section titled “Step 4 — Accept the data privacy disclaimer”

A disclaimer dialog will appear reminding you that all content visible to the provided Confluence user will be ingested into the SmartChat space and become accessible to all space members.

Disclaimer dialog

Read the message carefully. Only click Continue if you are authorized to share all of the Confluence content with everyone in the SmartChat space.

After accepting the disclaimer, the connection appears in the Data Connections table. If the credentials and URL are correct, you will see a green WORKS badge in the Test Result column.

Connection listed with WORKS badge

  • The Next Sync column shows when the next sync is scheduled. Sync always runs automatically at 00:00 (midnight) every day.
  • The initial sync imports all pages and may take anywhere from a few minutes to several hours, depending on the volume of content.
  • Subsequent syncs only process updates and are typically much faster.

Each connection has a set of action buttons on the right side of the table:

Action buttons

ButtonAction
Plug iconTest the connection — verifies that the credentials and URL are still valid.
Play iconSync now — triggers an immediate sync. This is useful if the next scheduled sync is too far away and you want fresh data sooner. Under normal circumstances, the automatic daily sync is sufficient.
Pen iconEdit the connection — modify the name, URL, credentials, or other settings.
Trash iconRemove the connection — deletes the connection configuration. Note that removing a connection does not delete the data that was already synced.

Once the sync has completed, the Confluence content is available in the SmartChat chat interface.

Select the corresponding space from the Space Selector in the top left and start typing. The synced Confluence data will automatically be loaded as context.

Classic space — data is loaded automatically

The connection test displays one of the following status codes:

StatusMeaning
WorksConnection is healthy.
Connection ErrorSmartChat cannot reach the server (timeout, DNS failure, connection refused).
Missing CredentialsNo username or secret was provided.
Auth FailedThe credentials were rejected (wrong username/password or expired token).
HTTP 400The request is malformed (usually a wrong URL path or missing parameters).
HTTP 404The URL or Space Key was not found on the server.
HTTP 4xxAnother client-side error (e.g. 403 Forbidden, 429 Rate Limited).
HTTP 500Internal server error on the Confluence side.
HTTP 5xxAnother server-side error on the Confluence side.
HTTP ErrorAn unclassified HTTP error.
FailedAn unexpected error occurred.

Cause: The Confluence server is unreachable. The URL may be wrong, the server may be down, or there is a network/firewall issue.

Fix: Verify the correct Confluence base URL. Data Center instances typically use a path like https://your-server.example.com/confluence/. Make sure you are using the API base URL, not the URL you see in the browser when browsing pages.

Cause: The username or password is wrong, or the API token has expired or been revoked.

Fix: Re-generate the API token in your Confluence account settings and verify that the username matches the token owner.

Cause: Either the base URL path is incorrect (e.g. with or without /wiki), or the Space Key is wrong. The display name may have been used instead of the Space Key, or there is a typo. Space Keys are case-sensitive.

Fix: Check the URL path first. Then look up the correct Space Key in Confluence under Settings → Space details.

Setup succeeds but ingestion or chat fails

Section titled “Setup succeeds but ingestion or chat fails”

Cause: The SmartChat space configuration is incomplete (no API key or default model set). Alternatively, Confluence may be throttling the API with a 429 response due to too many pages being requested at once.

Fix: Ensure the SmartChat space has a valid API key, embedding model, and default LLM configured before setting up Confluence sync. If you are being rate-limited, reduce the batch size or check with your Confluence administrator for rate limit settings. You can monitor ingestion status in the Context Files panel of the space.

Cause: The API token owner lacks access to the Confluence space, or individual pages have restricted permissions that exclude the token owner.

Fix: Ensure the token owner has read access to the target Confluence space and all pages within it. Check with your Confluence administrator if page-level restrictions are in place.