Prerequisite: Third-party connectors are available only on the Sana Enterprise tier, with one exception: the Workday connector is included for both Sana Core and Sana Enterprise.
Introduction
Connect your self-hosted Confluence Data Center instance to Sana to search, read, create, and manage pages and blog posts. Get instant answers and summaries from your spaces.
In summary, the connector has the following key characteristics:
Category: Documents
Connector type: Real-time
Auth type: OAuth
Hosting type: Managed
Tools
Tools are the operations the agent can use when you ask Sana about Confluence Data Center. In practice, the agent may call more than one to complete a single request.
Tool |
Create content |
Delete content |
Get page by ID |
Get pages |
List space key options |
List type options |
Search content |
Update content |
Note: This article lists the connector's full set of tools. Your workspace owner can disable individual tools for your workspace, so some of those listed here may not be available to your agents. If a tool you expected is missing, reach out to your workspace owner.
Triggers
While tools are the actions an agent takes on your behalf, triggers are the events that can start an agent automatically. When you build an agent, you can choose one of the triggers below as its starting point. For example, having the agent run every time something new happens in Confluence Data Center.
Trigger |
Blogpost Updated |
New Blogpost Created |
New Page Created |
Page Updated |
Scope and permissions
This connector uses OAuth. When you connect your account, you will need to sign into your account and grant the required permissions:
Scope | Purpose |
WRITE | Search and read pages and blog posts, and create, update, or delete them on your behalf. Capped at what your own Confluence account can do. |
Before you start
We recommend Central configuration: a Confluence admin registers Sana once as an incoming application link in your Confluence instance, and a Sana workspace owner saves its credentials in Sana. Everyone in the workspace can then connect with their own Confluence account.
With Individual configuration, a Confluence admin still creates an incoming application link, using the callback URL shown in the connect window, and shares its Client ID and Client Secret with everyone who needs the connector. Each person then enters the API URL, Client ID, and Client Secret when they connect.
The steps below set up Central configuration. Sana's redirect URL is only generated once the credentials are saved, so you visit Confluence twice.
1. Create an incoming link in Confluence
Go to Administration > General Configuration > Application links and select Create link. Choose External application with Incoming as the direction, then set:
Redirect URL — a placeholder such as
https://example.comfor now. You replace it with Sana's own redirect URL in step 3.Permission — Write. Each user's access is still capped at what their own Confluence account can do.
Confluence generates a Client ID and Client Secret when you save.
2. Save the credentials in Sana
In Sana, open the Confluence Data Center connector in your workspace's connector settings. Under OAuth Setup (or Credentials, if the connector is already added), choose Central configuration and enter:
API URL — the base URL of your Confluence instance, for example
https://confluence.example.com.Client ID and Client Secret — the values from step 1.
Save, then copy the Redirect URL that Sana shows.
3. Add Sana's redirect URL to the link
Back in Confluence, open the application link from step 1, edit it, and replace the Redirect URL with the one you copied from Sana.
For more detail on incoming links, see Atlassian's documentation.
Set up instructions
Prerequisites:
You are a Sana Enterprise user – all third-party connectors except the Workday connector are available only for users on the Sana Enterprise tier.
Your Sana workspace owner has enabled this connector – if the workspace owner has disabled the connector it won't appear in the list of available connectors.
Your Confluence Data Center admin has completed the required set up – see Before you start above.
Step 1: Go to the connectors page in Sana
In Sana, click on your profile icon and name in the bottom left corner and select Connectors.
Step 2: Find Confluence Data Center in the list of available connectors
Scroll to the Available connectors section and locate Confluence Data Center.
Note: If you can't find a connector in this list, it means one of the following:
You've already connected it — check the ”Active connectors” section at the top of the connectors page, or
Your workspace owner has disabled this connector for your workspace — reach out to them for more information or to request that it be enabled.
Step 3: Hover the connector card and click the connect button
Hover the Confluence Data Center card and click the Connect button.
Tip: If you click the card itself instead of the Connect button, you'll open a connector detail page with more information about its capabilities.
Step 4: Initialize the Pipedream connection
When clicking Connect in the previous step, a pop-up will appear powered by Pipedream. Click the Continue button in the pop-up to initialize the set up.
Note: Sana uses Pipedream to connect your account. Pipedream is a Workday product, trusted by millions of people to keep their data secure.
Step 5: Sign in to Confluence Data Center and approve the requested scopes
You'll be redirected to Confluence Data Center to go through their OAuth flow. Sign in and approve the scopes Sana needs to operate the connector.
Step 6: Complete the set up
You've successfully connected your Confluence Data Center account. Click Continue to complete the setup and start using the connector.
Known limitations
Content types: This connector primarily reads and writes Pages and Blog posts. Other content types (Databases, Whiteboards) are not supported.
Network access: Sana connects to your Confluence Data Center API URL from Sana's cloud connector platform — being reachable over the public internet is not enough if a firewall filters traffic. Corporate firewalls must allow traffic from the connector platform (contact support for the IP ranges to allowlist), otherwise requests time out.
Frequently asked questions
Q: I connected Confluence Data Center with a personal access token before. Do I need to reconnect?
A: No. Connections made with a personal access token keep working. New connections use OAuth. With Central configuration, your Confluence admin first needs to complete the set-up described in Before you start above. With Individual configuration, your Confluence admin still needs to create an incoming application link and share its Client ID and Client Secret.



