For Confluence on-premise collections, is it necessary to install anything on a server?
Yes, you must install an application on a Windows machine that is always on and has constant connectivity to the Confluence server and Internet. For more information, explore our guide to collecting from Confluence on-premise.
Can Onna collect Jira data from embedded Jira links within Confluence pages?
Even if the credentials are the same for both the Confluence and Jira accounts, Onna will not sync the data within the embedded Jira links. You must create a separate source within Onna to sync Jira data. Learn how to set up a Jira source in our Help Center.
What happens to Confluence links embedded in collected pages when "Collect external links" is enabled?*
When the "Collect external links" option is enabled, Onna identifies every URL embedded in a collected page and attempts to retrieve it. This includes links pointing to other pages within the same Confluence site — "external" in this context means external to the page being collected, not external to the Confluence site.
Each link is retrieved via a standard HTTP request to the URL. This request is made directly to the link address and not through the Confluence API. The HTML response returned to that request is what Onna ingests and stores as the collected artifact for that link.
For Confluence Cloud pages collected this way, the stored HTML may render differently when opened outside the source Confluence environment than the original page does within Confluence. Content that relies on client-side JavaScript or Confluence-specific rendering may appear blank or incomplete.
Note
This behavior applies only to pages collected indirectly through links. Confluence pages that are explicitly included in the collection scope are collected via the Confluence API and are not affected.
Why is Admin access required for Onna to pull data from Confluence?
We request admin access for completeness in the collection. By authenticating with an admin user, we can ensure that all available spaces and pages are returned. A regular user may not have access to the space needed to collect or all of the pages in a space to collect.
Can a sync be configured only to collect a single Confluence page?
Yes, to sync a single Confluence page, paste the link of the single page in the hostname field. When configuring the source, you will receive a message asking if you want to sync a single page.
How do I collect from a Confluence Data Center?
Confluence Data Center is a self-managed edition of Confluence built for enterprises. Onna users can collect from the Data Center edition with the same features and limitations of a Confluence server.
Onna recommends setting up a collection through the Legacy API when ingesting a large volume of Confluence spaces or pages. With the Legacy API configuration, you can collect multiple single-page collections that may not be able to be set up through the user interface.
Note
When ingesting a large volume of Confluence content, the Onna Support team suggests creating several Confluence data sources in Onna. Each source can be separated by Confluence spaces or pages.
How do I identify specific pages in exported Confluence data?
If you are trying to identify specific pages in exported Confluence data, there are a few fields you can leverage to find this information.
Metadata_File name: This field includes the file name of the resource. The file name is based on the page's subject, and the format will be HTML by default, so this will help you identify pages by name.
ResourceName: This field includes the Page ID. Page ID and Space ID are the unique identifier and representatives of each Space and Page. Users can edit the title of the Page anytime. Therefore, it's more content than a field. Please note, when reviewing ResourceName, results with pre-fix "att" are likely attachments of pages.
Note
To identify the Space ID and a Page ID you can deconstruct the URL of the Page. In this example:
https://atlasense.atlassian.net/wiki/spaces/JT/pages/2254897153
The Space ID is JT, and the Page ID is 2254897153
What should I expect when opening exported Confluence HTML files outside the source Confluence environment? *
It depends on how the page was collected, and the difference matters when you're exporting or producing files to someone without Confluence access.
When a page is directly included in your collection scope, Onna retrieves it through the Confluence API and stores it as an HTML file. That file contains the page content as it was returned by the API at the time of collection, and it generally holds up fine when opened outside of Confluence.
Pages collected through the "Collect external links" option work differently. What gets stored in that case is the raw HTML response from a direct HTTP request to the link URL — not API output. That file isn't self-contained. It may depend on styles, scripts, or other resources that only load correctly inside the Confluence environment, which means it can show up blank or incomplete when opened outside of it.
If you're producing Confluence content to someone who doesn't have Confluence access, it's worth opening any link-collected files first to check how they render before sending them out. If a file isn't displaying correctly, the most reliable fix is to add that page directly to your collection scope so Onna collects it through the API instead.