Skip to main content

Fluid Topics Integration

Fluid Topics is software that is designed to provide a single portal for all of your documentation, including PDFs, Word documents, knowledge base articles and content you create in Paligo too.

To use your Paligo content in Fluid Topics, you will need:

  • A Fluid Topics account with administrator permissions

  • A source set up in Fluid Topics. The source is a "silo" that will receive the content from Paligo.

  • An API key, generated in Fluid Topics.


For details on how to set these up in Fluid Topics, refer to the Fluid Topics documentation.

You can publish content directly from Paligo to your Fluid Topics instance. But to do that, you first need to set up Paligo and Fluid Topics to connect to each other.


If your Fluid Topics has been connected to your Paligo instance before, you may already have a source and API key, in which case, you can use those instead of creating new ones.

  1. Log in to Fluid Topics as an administrator to create a new source ID and generate a new API key.

    The source is the "silo" that will receive the content from Paligo. Fluid Topics uses the API key to authenticate the connection from Paligo.

    For details on creating a source and generating an API key, see the Fluid Topics documentation.

  2. Log in to Paligo via a user account that has administrator permissions.

  3. Select the avatar in the top-right corner. User avatar. It shows the user's image and their name. Next to the name is a downward pointing arrow, which when selected, reveals a menu.

  4. Select Settings from the menu. Cog icon.

  5. Select the Integrations tab. Jigsaw piece icon.

    Paligo settings. The Integrations tab is highlighted.
  6. Select Add in the Fluid Topics box.


    If the integration is set up already, there is a Change button instead.

  7. Enter the Account name.

  8. Enter the Upload URL of the Fluid Topics portal that will receive content from Paligo.

  9. Enter the API key created in step 2.

  10. Enter the Source ID created in step 2.

    Fluid Topics uses the Source ID to identify the "silo" that will receive the Paligo content. It also uses the Source ID to identify the type of content being received.

  11. Select Save.

  12. Check the box Use gateway to enable IP Allowlisting. Optional

    If you have IP restrictions enabled in Fluid Topics, you need to set Paligo to use a static IP address (via a gateway).

  13. Provide Fluid Topics support with Paligo's IP address to allowlist it. Optional

    This will enable Paligo to publish to Fluid Topics even if "IP restrictions" are enabled.

  14. Select Save.

  15. Select Test settings to verify the connection.

    • A successful test will connect Paligo to Fluid Topics and you will be able to Publish to Fluid Topics.

    • If the test fails, check that the upload URL, API Key and Source ID are correct. If they are correct and the test still fails, contact customer support for assistance.

To publish content from Paligo to Fluid Topics, you must first set up the Paligo to Fluid Topics connection. When that is in place, you can publish content from Paligo to Fluid Topics, and unlike some of the other integrations, there is no need for a layout.

When you publish with the Fluid Topics output, a zip file of your output is sent to Fluid Topics, where it is processed and added to the relevant source. You specify the source in the Paligo integration settings.

  1. Make sure that you have set up the Fluid Topics integration settings correctly.

  2. In the Content Manager, select the dotted menu ( ...) for your publication, and then select Publish.

  3. Select Fluid Topics.

    Publish document dialog for publishing to Fluid Topics. There is a Fluid Topics option at the top, as well as settings for languages, profiles, variables, and more.


    If the Fluid Topics option is not shown, check that Paligo can connect to Fluid Topics. The Fluid Topics option only shows when the connection is set up correctly.

  4. Choose the Languages that you want to publish.

    If you do not have any translations, you can only select the original language (source language).

    If you have multiple languages translated and approved, you can select which ones to include. Paligo will publish each language as a separate output.

    Languages section of Publish document dialog. There are options for each language. English UK and Swedish are selected.

    Fluid Topics will process and manage the translations so that they appear in the correct place in Fluid Topics.

  5. If you have marked up your content to use filters (profiles), use the Profiling attributes section to choose which filters to apply. If you do not want to use filters, ignore this step and continue from the next step.

    To apply filters for publishing, select Edit to display a list of the filter properties that are used.

    Choose the filter values that you want to include. Leave the fields blank for the filters that you do not want to apply.

    Profiling attributes dialog. Outputformat is set to include HTML.

    When you select OK, the chosen profile settings are shown in the Profiling attributes section.

    Profiling attributes section of Publish document dialog. Shows Outputformat: HTML selected.


    With the filter settings, you tell Paligo which content to include. For example, if you have used an outputformat filter, you could mark up some content to have a PDF value and other content to have an HTML value. In the publishing settings, if you set Output Format to HTML, it will include the content that has an outputformat:HTML filter and will exclude any content that has an outputformat:PDF filter (or any value other than HTML).

  6. If you have used variables in your content, use the Variables section to choose which variants to use for the publication.If you do not want to use variables, ignore this step and continue from the next step.

    To choose the variants, select Edit to display a list of variable sets that are used. For each variable set, there is a field that you can use to choose which variant to apply. If there are variable sets that you do not want to apply to your publication, leave the fields for those empty.

    Variables dialog showing ACME 100 200 300 as variables and ACME 100 is set.
    Variables section of publish document dialog. The ACME 100 200 300 variable set is selected with the ACME 100 variant.
  7. Use the Upload Output settings to upload the published content to other platforms as well, such as GitHub. This is optional and the uploads will only be possible if the relevant Paligo integration settings are in place. For example, you can only upload to GitHub if you have set up the Paligo to GitHub integration.

    To find out how to set the integrations up, see Integrations.

  8. Set the Optional Parameters (leave unchecked if you do not want these features):

    • Save the output in Paligo - Check the box to save the zip file in the Resource View. Clear the box if you want Paligo to only download the published output file in your browser.

    • Email me - Check this box if you want Paligo to send you an email when the publication is ready. This is useful if you have very large publications that can take a longer time to process and publish.

    • Make debug build - Check this box if you want Paligo to include a log file and link report. If there is an issue with your content, Paligo support may ask you to enable this feature so that they can use the log files to investigate.


    Every time you publish, there will also be a link in the Dashboard feed to download the published content.

  9. Select Publish Document to start publishing. Paligo will then process your content and apply your publishing settings. The time that this takes can vary depending on how much content you are publishing (the more content there is, the longer it takes).

    A progress bar shows you how much of the processing Paligo has completed and how much is left to do. When the processing is complete, Paligo "pushes" the production content into Fluid Topics.


You can also save your publishing settings so that you can select the saved version instead of re-applying all the filters, variables, etc., each time. Any settings you save can also be used for Batch Publishing.