To link Confluence to a Slack channel, install the Confluence Cloud app from the Slack Marketplace, open your target Slack channel, and type /confluence connect — the entire setup takes under five minutes. This connects your Confluence site to Slack so channels can receive page update notifications, generate link previews, and link back to Slack channels directly from Confluence pages. Getting it to actually reduce noise, surface knowledge at the right moment, and stop people from asking the same questions over and over — that takes a bit more thought. This guide covers both: the exact steps to connect Confluence to Slack, and the practical patterns that make the integration worth keeping.

What the Confluence-Slack Integration Actually Does

The Confluence Slack integration is a notification and linking layer, not a full knowledge sync. Here is what it actually enables:

• Slack channels can subscribe to updates from specific Confluence pages — edits, comments, and new blog posts push as notifications

• Pasting a Confluence URL into Slack generates a link preview showing the page title, space, last editor, and a content snippet

• Teams can link directly to Slack channels from within Confluence pages using deep links

There are two versions to be aware of. Confluence Cloud uses the Atlassian app in the Slack Marketplace and is the easier path — most of the setup happens directly in Slack. Confluence Data Center requires admin configuration on the Confluence side before channel connections are available. The steps differ, and this guide covers both.

Set the right expectation before you start: this integration keeps Slack and Confluence in conversation with each other. It does not automatically move knowledge between them. What gets documented in Confluence stays in Confluence. What gets discussed in Slack stays in Slack. The integration helps you bridge that gap — but only if you use it deliberately. According to a 2024 Atlassian State of Teams report, teams that integrate their documentation and communication tools report a 35% reduction in time spent searching for information across platforms.

How to Connect Confluence to a Slack Channel

Follow these steps based on your Confluence version.

Confluence Cloud

1. Install the Confluence Cloud app from the Slack Marketplace. Go to the Slack Marketplace, search for "Confluence Cloud," and install it at the workspace level. You need Slack admin permissions to do this — if you do not have them, ask your Slack admin to install it first.

2. Open the Slack channel you want to connect and type /confluence connect. A prompt will appear asking you to authenticate with your Atlassian account.

3. Authenticate and confirm the correct Confluence site. If your Atlassian account has access to multiple Confluence sites, you will be asked to select which one to link. Pick the right site — this is the most common source of errors.

4. Confirm the connection. Once authenticated, Slack will confirm the channel is connected. You can now subscribe to page updates and receive link previews from that Confluence site.

Confluence Data Center

1. Navigate to Confluence Global Administration. From the Confluence admin panel, go to Global Settings > Slack Integration.

2. Follow the connection link under "Connection status." This walks you through authorizing the Slack workspace at the server level. You need both Confluence admin and Slack admin permissions to complete this step.

3. Once connected at the admin level, individual users can begin linking channels to Confluence spaces and pages following the same slash command pattern as Cloud.

Common errors to watch for

• Wrong site linked: Double-check the Confluence site URL during authentication, especially if you have staging and production environments

• Missing admin permissions: The app must be installed at the Slack workspace level before individual users can run /confluence connect

• App not installed workspace-wide: Installing for a single channel is not enough — the Atlassian app needs workspace-level authorization

How to Subscribe a Slack Channel to a Confluence Page

Once connected, subscribing a channel to specific page updates is straightforward.

In any Slack channel, type:

/confluence connect [paste the Confluence page URL here]

Slack will confirm the subscription. From that point on, the channel will receive a notification whenever someone:

• Edits the page

• Leaves a comment

• Publishes a new blog post in the linked space

To manage or remove subscriptions, use the /confluence notify command. This opens a menu where you can view active subscriptions for the channel and toggle them on or off.

The most useful application of this: subscribe your #product-updates channel to your product roadmap page in Confluence. Every time the roadmap changes, the channel gets a notification automatically — no one needs to remember to post an update manually. The same logic applies to #engineering-docs, #onboarding, or any channel where keeping up with a living document matters. For more ideas on structuring channels around documentation workflows, see How to Organize Slack Channels: A Practical System That Actually Scales.

How to Add a Confluence Link to a Slack Channel from a Confluence Page

Running the integration in the other direction — linking from Confluence into Slack — is also worth doing, especially for onboarding docs and project pages where you want people to know which channel owns the work.

Here is the process:

1. In Slack, right-click any channel name in the sidebar and select Copy Link. This gives you a slack:// deep link URL.

2. In your Confluence page, highlight the text you want to hyperlink, open the link tool, and paste the Slack deep link.

3. Save the page. Clicking the link will open the channel directly in the Slack desktop app.

Important caveat: deep links open the Slack desktop application. Users who access Slack via browser only, or who do not have Slack installed, will hit an error. If your team has mixed Slack access, pair every channel link with a plain-text description of what the channel is for — this way the information is useful even when the link is not.

Can you link to a Slack profile from Confluence?

This comes up often in the Atlassian Community. The short answer: no, not reliably. Direct message links (the slack://user?team=...&id=... format) do not work consistently when embedded in Confluence pages. They depend on the viewer's Slack client, authentication state, and workspace membership — too many variables to be dependable. Channel links are the supported path. If you want to surface a point of contact in Confluence, link to their Confluence profile or list their name and Slack handle as plain text instead.

How Confluence Link Previews Work in Slack

This is one of the most underused features of the confluence slack integration. When anyone pastes a Confluence page URL into a Slack message, the Atlassian app automatically generates a link preview — called an "unfurl" — that displays:

• The page title

• The Confluence space it belongs to

• When it was last edited and by whom

• A short content snippet

For this to work, the Confluence Cloud app must be installed and the person sharing the link must be authenticated with their Atlassian account in Slack.

Practical tip: use link previews instead of copy-pasting content into Slack messages. When you share meeting notes or a decision log as a Confluence link, the preview gives enough context for most people to know whether they need to open it — without forcing anyone to leave Slack to find out. It is a small habit that keeps Confluence as the source of truth rather than letting information fragment across Slack messages.

Where the Confluence-Slack Integration Falls Short

The integration does what it says. The problem is what it does not say.

Notifications are one-directional. Confluence pushes updates into Slack. Nothing flows the other way. Every decision made in a Slack thread, every answer given in #general, every clarification buried in a DM — none of that reaches Confluence unless someone manually copies it over.

In high-volume channels, page update notifications get buried fast. If your #engineering channel has 200 messages a day, a Confluence notification from three hours ago is effectively invisible.

The deeper problem: linking two tools is not the same as connecting your knowledge. The informal Q&A that actually runs your organization — "what's the process for X," "who owns Y," "why did we decide Z" — happens in Slack threads. That knowledge stays trapped there. It never makes it to Confluence. Teams end up answering the same questions repeatedly because the answer lives in a thread from six months ago that no one can find. According to a 2023 IDC report, employees spend an average of 2.5 hours per day searching for information or recreating knowledge that already exists somewhere in their organization — costing enterprises an estimated $47 million annually in lost productivity per 1,000 workers. This is a known and persistent gap in how Slack handles knowledge.

Question Base captures the informal knowledge that lives and dies in Slack threads — the Q&A that never makes it to Confluence — and makes it searchable and retrievable without anyone needing to document it manually.

How to Get More Out of Confluence and Slack Together

The integration is a starting point. These patterns turn it into something your team actually relies on.

Create dedicated channels for Confluence spaces

Map your Confluence spaces to Slack channels — #engineering-docs, #product-wiki, #hr-policies — and subscribe each channel to the relevant Confluence space. Updates to any page in that space notify the channel. This keeps the right people informed without spamming channels that do not need to know.

Establish a 24-hour documentation norm

When a Slack conversation produces a decision, a process clarification, or an answer that will come up again — someone pastes it into the linked Confluence page within 24 hours. This does not require a tool. It requires a team agreement. Make it explicit in your working norms and point people to where the linked Confluence page lives. Over time, this practice dramatically reduces the number of times the same question gets asked. For more on building sustainable knowledge-sharing habits, see How to Build a Knowledge Base From Slack Conversations.

Use Confluence links in channel descriptions and bookmarks

New team members should not have to ask where documentation lives. Put the Confluence page link directly in the Slack channel description for every channel that has a corresponding doc. Pin the most important Confluence links in the channel's Bookmarks bar — the strip at the top of every Slack channel — so they are visible without anyone having to dig.

Add page links to your onboarding Confluence docs

Onboarding documentation in Confluence is only useful if new hires know where to go when they have questions. Link the relevant Slack channels directly in your onboarding pages. Someone reading the engineering onboarding doc should be one click away from #engineering-help. This closes the loop between your written documentation and the live conversations where answers actually happen.

Reduce the manual lift with tooling that bridges the gap

The honest version of this advice: even teams that do everything right will still lose knowledge in Slack. The volume is too high and the incentive to document is too low. Tooling that automatically captures Slack Q&A and surfaces it alongside Confluence content reduces the manual lift significantly — and means that when someone asks a question that has already been answered, they get the answer instead of silence.

The Confluence-Slack integration is worth setting up and maintaining. But treat it as one layer of your knowledge infrastructure, not the whole thing. The teams that get the most out of it pair it with intentional channel structure, clear documentation norms, and tooling that handles the knowledge that falls through the cracks. Start with the connection, then build the habits around it.

Frequently Asked Questions

How do I link a Confluence page to a Slack channel?

Open the Slack channel you want to connect, type /confluence connect followed by the Confluence page URL, and authenticate with your Atlassian account when prompted. Once confirmed, the channel will receive notifications whenever that page is edited or commented on. The Confluence Cloud app must be installed at the workspace level before this command is available.

Can I add a Slack channel link inside a Confluence page?

Yes — right-click the channel name in Slack's sidebar, select "Copy Link" to get the slack:// deep link, then paste it as a hyperlink in your Confluence page. Clicking the link will open the channel directly in the Slack desktop app. Note that this deep link only works for users who have the Slack desktop application installed.

Does the Confluence-Slack integration work for Confluence Data Center?

Yes, but the setup requires a Confluence admin to first authorize the Slack workspace under Global Settings > Slack Integration in the Confluence admin panel. Both Confluence admin and Slack admin permissions are needed to complete the initial connection. Once the workspace-level link is established, individual users can connect channels using the same slash commands as Confluence Cloud.

Why aren't my Confluence link previews showing up in Slack?

Link previews (unfurls) require both the Confluence Cloud app to be installed in your Slack workspace and the person sharing the link to be authenticated with their Atlassian account in Slack. If either condition is not met, the URL will appear as a plain link without a preview. Re-running /confluence connect in any channel and completing the authentication flow usually resolves this.

How do I stop getting too many Confluence notifications in Slack?

Use the /confluence notify command in the relevant channel to open a subscription management menu where you can toggle off specific page or space subscriptions. It is best practice to subscribe only high-traffic documentation channels (like #product-updates or #engineering-docs) rather than general channels. Keeping subscriptions scoped to the right audience prevents notification fatigue and keeps updates visible to the people who need them.