Zendesk and Confluence
Your documentation lives in Confluence and your agents live in Zendesk. The question with Zendesk and Confluence is which one moves, and the answer is usually neither.
What people are really asking for
Almost every version of this request is one of three things.
An agent wants to search internal documentation without leaving the ticket. That is a sidebar app problem.
A team wants a page linked to a ticket so the escalation has context. That's a link and a field.
Or somebody wants Confluence to be the customer-facing help centre. That last one is the request to push back on, and we will get to why.
Surfacing Confluence in the ticket
The Zendesk marketplace carries apps that search Confluence from the agent sidebar and let you paste a link, or in some cases an excerpt, into a reply. Availability and pricing change, so check the marketplace listing and confirm whether it supports Confluence Cloud, Data Center, or both, because that split catches people out constantly.
What a decent app should do:
If nothing on the marketplace fits, the app framework lets you build a sidebar app that queries the Confluence REST API. It is a genuinely small project for a competent front-end developer, and check the current Atlassian API reference for the search endpoint and auth model before scoping it.
Capturing knowledge the other way
The more valuable direction is the one teams neglect. An agent works out a tricky answer, types it into a ticket, and it is gone.
Zendesk has knowledge capture built into the agent workspace for Guide articles: flag a gap, draft an article from the ticket, link the article to the ticket. See knowledge capture for how that works in practice.
For Confluence, you generally do not get that loop natively. The workaround that actually holds is a weekly ritual rather than a tool. Tag tickets needs-doc when the answer took real work, review the tag once a week, and write up the ones that recurred. Fifteen minutes, a named owner, and you'll out-document any team relying on an integration to do it for them.
Confluence or Zendesk Guide
These are not competing products, they are different audiences, and confusing them is the root of most of the pain here.
Confluence is an internal wiki. Anyone can edit, structure is loose, versions and comments are first class, and it's where a team thinks out loud. That is a strength for engineering runbooks and a liability for customer-facing help.
Zendesk Guide is a publishing platform. It has a themed public site, SEO-friendly article pages, article search wired into the help centre and the messaging widget, permission-controlled sections for logged-in customers, and answer suggestions that only work against Guide content.
So the split is simple. Customer-facing content goes in Guide, because that's where deflection happens and no Confluence page will ever rank for your product questions. Internal runbooks, architecture notes and process docs stay in Confluence. Agent-facing troubleshooting can live in either, and the tiebreaker is who maintains it: if engineers write it, keep it in Confluence and surface it in the sidebar.
One warning about publishing Confluence spaces to the internet as a help centre. It's technically possible and it usually disappoints. Search, branding and permissions are built for internal use, and the day someone edits a page without realising it is public is the day you stop doing it.
A setup that works
Guide holds the customer-facing articles. Confluence holds internal documentation. A sidebar app searches Confluence from the ticket. Links between the two are one direction only, from ticket to page, so nothing gets out of sync.
Then one rule everybody follows: if an answer is useful to a customer, it goes in Guide, even if a Confluence page already says the same thing. Duplicated content across two systems is annoying. A public article nobody can find because it lives on an internal wiki is worse.
If you also run Jira, the same logic applies to escalation, and the Jira integration covers that side.
Frequently asked questions
Can Confluence serve as the knowledge base?
For internal content, yes. A Confluence knowledge base Zendesk agents search from works through federated search, and the Zendesk Atlassian Confluence apps surface pages in the ticket sidebar. Customer-facing content still belongs in Guide.
Is there an official Zendesk Confluence integration?
There are marketplace apps that search Confluence from the agent sidebar. Check the listing for whether it supports Confluence Cloud, Data Center or both, and how it handles permissions.
Can I use Confluence as my customer help centre?
You can publish spaces publicly, but search, branding and permission handling are built for internal use. Zendesk Guide is designed for the job and integrates with ticket deflection.
Can agents create Confluence pages from a ticket?
Not natively in the way Zendesk knowledge capture creates Guide articles. Most teams use a tag and a weekly review instead, which works better than it sounds.
Should internal docs move into Zendesk Guide?
Only agent-facing troubleshooting, and only if support owns it. Engineering runbooks belong where engineers already work, which is Confluence.
Do Confluence permissions carry into Zendesk?
Only if the app authenticates each agent individually. An app using a single service account will show every agent everything, which is a genuine leak risk.
Documented once, asked five times
Even a perfect knowledge base leaves duplicate tickets in the queue. Ticket Merger finds and merges them automatically.
Start free trial14-day free trial. No credit card required.