Currently when syncing with Confluence, the only visible sources are those contained within ‘Pages’. Anything that’s in a folder or subfolder is hidden and so cannot be located and used for FIN or CoPilot. Is there a workaround for this that doesn’t mean we have to remove everything from the folders and have 1000 individual pages for our knowledge base?
Has anyone found a workaround that isn’t too time consuming?
Best answer by Paul B12
Hey
Thanks for flagging this! I totally get how having all your Confluence content neatly organized in folders and subfolders is important, and it’s not ideal to flatten everything into one big list of pages.
Right now, Intercom’s Confluence integration only syncs pages that are directly within the space or ‘Pages’ section it doesn’t automatically dive into folders or subfolders to pull content from there. This is definitely something our team is aware of as a limitation.
One handy workaround another customer shared is to embed pages within other pages instead of using folders. This mimics a folder-like structure, but since embedded pages are still technically just pages, they transfer over to Intercom without issues. It lets you keep things organized without needing to flatten everything or lose structure.
The catch is: actual folders or subfolders won’t sync, but embedded pages do. Some folks create a parent page that acts like a “folder”, and then embed or link the relevant child pages inside it. This seems to work well for keeping content grouped while ensuring it’s available for Fin or Copilot.
I know it’s not perfect, but I hope this gives you a bit more flexibility while we wait for deeper folder support.
For now, if you embed a page within a page, it mimics the folder capability and still transfers into Intercom. Once you create the folder it all disappears in the transfer. I am hoping that folders move over at some point but the page within a page has worked well for us today. (In my screenshot the ones in red transfer but the others do not.)
+2Hey
Thanks for flagging this! I totally get how having all your Confluence content neatly organized in folders and subfolders is important, and it’s not ideal to flatten everything into one big list of pages.
Right now, Intercom’s Confluence integration only syncs pages that are directly within the space or ‘Pages’ section it doesn’t automatically dive into folders or subfolders to pull content from there. This is definitely something our team is aware of as a limitation.
One handy workaround another customer shared is to embed pages within other pages instead of using folders. This mimics a folder-like structure, but since embedded pages are still technically just pages, they transfer over to Intercom without issues. It lets you keep things organized without needing to flatten everything or lose structure.
The catch is: actual folders or subfolders won’t sync, but embedded pages do. Some folks create a parent page that acts like a “folder”, and then embed or link the relevant child pages inside it. This seems to work well for keeping content grouped while ensuring it’s available for Fin or Copilot.
I know it’s not perfect, but I hope this gives you a bit more flexibility while we wait for deeper folder support.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
