You can sync or import your internal content from Confluence, Guru, or Notion to your Fin workspace where it can be enabled for Fin and/or Copilot. Confluence and Notion sources now support richer metadata, pre-filter rules, and a new metadata review flow so you can control exactly which pages come into Fin and where they're used.
When content is synced:
It can’t be edited in Fin. Changes to content must be made in the source tool (Confluence, Notion or Guru).
It will automatically resync every 24 hours and any new content changes will then be reflected in Fin. It can also be manually re-synced.
The daily sync is skipped when there have been no content updates to the source since the last sync, as running it would produce nothing new.
Content will be added to new synced folders in Fin. A synced folder can’t be modified and all folders will be shown in alphabetical order.
When content is imported:
It is transformed into native internal articles which can be edited/deleted from within your Fin workspace.
Content will be added to a new native folder in Fin. Native folders can be modified.
Sync or import internal articles
To sync new internal sources, navigate to Train > Content and click See all below the "Add content" section.
Then select an internal knowledge source, such as:
Notion
Confluence
Guru
You'll be asked for credentials to access the associated Confluence/Guru/Notion account.
Confluence
Open your Confluence source in Train > Content.
Click Edit source (in the three-dot menu next to the source).
Walk through the Connect → Metadata → Target → Review steps.
Configure metadata filters, audience targeting, and Fin AI Agent/Copilot availability.
Click Update and sync.
Note: This works for both v1 and v2 sources (Folders-enabled sources). Your existing OAuth credentials carry over — you may be prompted to re-authenticate if your connection has expired. Spaces with restricted permissions may fail to sync correctly. Always ensure the user account used to connect Confluence has appropriate viewing and access permissions for the spaces you intend to sync.
The Metadata step lets you pre-filter which pages come into Fin. For Confluence, metadata synced as structured fields includes labels, title, parent page, author, and created/edited dates. You can build pre-filter rules using string conditions (is, is not, contains, starts with, ends with) and label conditions (is, is not).
Note:
This integration currently supports Confluence Cloud only. Ensure you are not attempting to integrate with an on-premises version of Confluence.
We only import Confluence spaces of the type 'global'.
Ensure you sign in with a user account which has the correct permissions for the content you are looking to sync or import to Fin.
Folders can now be created within Confluence, however those are not currently supported with this sync. You will only see these pages and sub-pages appear in the 'select folders' dropdown. 👇
Note:
Folder exclusion is now handled via filters: use the "Ancestor page" filter to exclude entire page subtrees. If you had denied folders configured before, they're automatically migrated to filter rules on your next sync — no action needed.
We don't support single-page syncs. Only the full sync is supported.
We support syncing Folders, but not Whiteboards from Confluence.
Troubleshooting Confluence space syncing issues
When integrating Confluence spaces with Fin, you might encounter situations where certain spaces aren't visible or syncing correctly. This guide helps you diagnose and resolve these common issues.
Verify the type of the missing Confluence space
In Confluence, navigate to Space settings > Manage Space > Space Details.
Review the ‘Type’ of the space.
Fin only supports syncing spaces of the 'global' type. Spaces marked as 'personal' or 'knowledge_base' are not included in the sync.
Create a new custom space (If type is unsupported)
If the missing Confluence space is of an unsupported type (e.g., 'personal' or 'knowledge_base'), you can create a new 'Custom' space to resolve the issue.
In Confluence, create a new Custom space.
Transfer the content from your unsupported space into this newly created Custom space.
Check visibility settings
In Confluence, ensure that the space you want to sync is set to a 'current' status.
Only spaces with this status will be considered for syncing with Fin.
Troubleshooting folder and page hierarchies
Fin does not directly support folders within Confluence for syncing purposes. Instead, it syncs based on individual pages and sub-pages.
To ensure your content syncs correctly, structure it using pages and sub-pages. If you need to exclude specific content, move those pages into a separate Confluence space that is not intended for syncing with Fin.
If the above steps do not resolve the issue, there may be a specific backend setting that needs to be enabled for your workspace. To get this sorted, reach out to our Support team. When you do, let them know you've already walked through the troubleshooting steps. Then, ask them to dig into enabling any backend settings that could help display all your non-personal Confluence spaces, bypassing those default restrictions. They'll help get everything flowing smoothly for you.
Note: Spaces with restricted permissions may fail to sync correctly. Always ensure that the user account used to connect Confluence with Intercom has appropriate viewing and access permissions for the spaces you intend to sync.
Guru
Open your Guru source in Train > Content.
Enter your Guru email and API token.
Select Collection, Folders, and whether to import or sync content.
The status will be shown in Fin Content when the sync/import starts.
Once sync/import is complete the status icon updates to a green tick.
Tip: Ensure you have the correct permissions associated with your Guru account and have your API credentials to hand when syncing or importing. API credentials can be accessed by following the instructions outlined here and can be found in your settings page. Ensure that you select the User Token.
Notion
Open your Notion source in Train > Content.
Click Edit source (in the three-dot menu next to the source).
Walk through the Connect → Metadata → Target → Review steps.
Configure metadata filters, audience targeting, and Fin AI Agent/Copilot availability.
Note: No migration required for Notion — everything is handled implicitly on your next sync. Dynamic properties are brought in automatically as structured fields.
Tip: Ensure you sign in with a user account which has the correct permissions for the content you are looking to sync or import to Fin.
Metadata review flow
Confluence and Notion sources use a four-step setup flow that makes it transparent how content is fetched into Fin, and gives you control over what gets imported and where it's used.
Connect
Authenticate to the external source. Your existing OAuth credentials carry over for Confluence sources — you may be prompted to re-authenticate if the connection has expired.
Metadata
Choose which content should be in scope using pre-filter rules based on metadata from your external knowledge base. Typical metadata includes:
Labels or tags
Title
Parent page / ancestor page
Author
Created and edited dates
Dynamic properties (Notion)
Build rules using string conditions (is, is not, contains, starts with, ends with) and label conditions (is, is not) to narrow down the slice of content that gets synced — for example, only pages labeled "fin-ai", or only content updated after a certain date.
Tip: If you skip the Metadata step, the importer brings in all eligible content from the source by default.
Target
Decide where imported content is used inside Fin. Configure:
Fin AI Agent — use the content to answer customer questions automatically (defaults to OFF)
Copilot — make content available to teammates as suggested answers
Audience targeting — define audience rules at source level, auto-applied at import time
Review
Confirm your configuration before syncing starts. The review shows:
Connection details (which external account or subdomain you're connected to)
Items in scope after applying Metadata filters
Enabled destinations in Target
Audience and targeting rules
Give the source a clear name before confirming — for example, "Confluence – Internal Support KB" or "Notion – Product Docs (EMEA)". Then click Update and sync.
Tip: You can re-open the same flow later to adjust Metadata, Target, or Review settings without recreating the source.
Manage synced internal articles
Once the sync or import is complete, you’ll receive an email notification and the internal articles will appear in Train > Content under the "Content sources" section.
Configure internal article settings
Go to Train > Content, select the content source, then open the internal article. Configure its settings in the "Details" panel on the right:
Data: View the content type, language, creation date, created by, last update, and the teammate who last updated it.
Fin: To enable/disable for Fin and Copilot. When enabled, the content becomes available to customers through Fin Agent and to teammates via Fin Copilot, respectively.
Audience: Ensure customers only get answers and see content that is relevant for them when Fin or Copilot responds.
Link: A link to the article in your internal knowledge base (e.g. Notion/Confluence/Guru).
Reports: Tracks how often this content is involved and used to resolve conversations by Fin Agent.
Tags: Add a tag to group internal articles together and keep content organized (includes imported tags).
Note:
Synced internal articles can’t be edited. If you want to make changes to the content, you’ll need to do this from the source itself.
Imported internal articles can be edited and managed within Fin. They won’t sync with the source, so any changes you want to make need to be done within your Fin workspace.
Re-sync or remove internal articles
Internal articles from external sources will automatically be synced every 24 hours, but you can manually re-sync or remove a source by going to Train > Content, select the 3 dot menu next to the source and then select Re-sync or Remove this source.
Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts