Your knowledge base is more than the words on the page.

A troubleshooting ‘DIY’ guide may depend on screenshots to explain a procedure, a table to clarify configuration options, an attachment to provide supporting detail, and links to child pages to guide the reader’s next step.

Those elements carry knowledge, too.

When bringing Confluence content into Salesforce, the evaluation should go beyond whether the text becomes available:

• Do images remain part of the instructions?
• Do tables retain their structure and readability?
• Are supporting attachments available?
• Do links connect readers to the corresponding knowledge articles?
• Are references to pages that haven’t been published identified?
• Can authors update the content without rebuilding it in another editor?

These details determine whether a published article helps someone complete a task—or leaves them searching for missing context.

zAgile’s Knowledge:Bridge is purpose-built for this publishing workflow. Teams create and curate rich content in Confluence, then publish it as Salesforce Knowledge articles while preserving supported formatting, structure, images, and attachments.

With support for child-page listings and checks for references to unpublished pages, the workflow also addresses the relationships between articles—not just individual pages.

Authors continue working in Confluence. Support teams and customers receive curated knowledge through Salesforce.

When evaluating Confluence-to-Salesforce integration, bring a real article: screenshots, tables, attachments, and related pages included.

The result should preserve what makes that article useful.

Explore Knowledge:Bridge: https://www.zagile.com/knowledgebridge/

#SalesforceKnowledge #Confluence #KnowledgeManagement