Connect Fluid Topics to Rapidflare to ingest structured technical documentation with version control, enabling your AI Agent to answer questions from your product knowledge platform.

Overview

Fluid Topics is an enterprise product knowledge platform that centralizes technical documentation from multiple sources. The Rapidflare integration allows you to:

• Ingest documents and maps - Support for both standalone documents and structured multi-topic documentation
• Automatic version selection - Intelligently select the best version when multiple exist
• Preserve structure - Maintain topic hierarchy and relationships
• Handle rich content - Process embedded images and resources

Key Concepts

Understanding Fluid Topics terminology helps configure the integration effectively:

Setting Up Fluid Topics

Step 1: Add a New Source

1. Navigate to Sources in your admin dashboard
2. Click Add Source
3. Select Fluid Topics

Step 2: Configure Connection

1. Enter your Fluid Topics base URL (e.g., https://docs.yourcompany.com)
2. Provide your API token (Bearer token for authentication)
3. Test the connection

Step 3: Define Content Scope

You can specify content in two ways:

Filter URLs - URLs that return multiple documents matching criteria:

https://docs.yourcompany.com/search/documents?value-filters=Product~"ProductName"&content-lang=en-US

Use filter URLs when:

• Ingesting many documents matching criteria
• You want automatic discovery of new matching docs
• Filters are stable and well-defined

Direct URLs - Specific document or map URLs:

https://docs.yourcompany.com/v/u/en-US/specific-document

Use direct URLs when:

• Specific critical documents must always be included
• Documents don't match filter criteria
• Testing or debugging specific content

Step 4: Configure Options

• Cache by Last Modified - Enable version-aware caching to skip unchanged documents (recommended)
• Locale Preference - Prefer specific language versions (e.g., en-US)

Version Handling

When multiple versions of the same document exist, Rapidflare automatically selects the best one using these priority rules:

1. File type - Supported formats only (PDF, HTML, DOCX)
2. Latest flag - Prefer items marked as the latest version
3. Locale - Prefer your configured locale (default: en-US)
4. Content type - Prefer Maps over Documents (more structured)
5. Publication date - Most recently published wins

This ensures you don't get duplicate content from multiple versions or translations of the same document.

Content Processing

Documents

Standalone documents are processed as:

1. Download the binary content
2. Extract text based on file type (PDF, HTML, DOCX)
3. Create searchable document with metadata

Maps (Structured Documentation)

Maps are processed topic-by-topic:

1. Fetch the table of contents hierarchy
2. Download each topic as HTML
3. Replace embedded images with accessible URLs
4. Create individual documents for each topic with unique URLs

This granular approach ensures precise retrieval—the AI can reference specific sections rather than entire manuals.

Best Practices

Filter URL Design

• Use specific filters to avoid ingesting irrelevant content
• Combine multiple filter URLs for different product lines
• Test filter URLs in Fluid Topics search first

Direct URL Usage

• Include critical documents that might not match filters
• Add newly published documents before they appear in filters
• Use for testing specific content ingestion

Version Management

• Enable cache by last modified to avoid reprocessing unchanged docs
• Set appropriate locale preferences for your audience
• Monitor the ingestion logs for version selection decisions

Troubleshooting

Documents Not Found

• Verify the filter URL returns results in Fluid Topics
• Check that direct URLs are accessible
• Ensure your API token has read access

Wrong Version Selected

• Review the version selection logic in ingestion logs
• Adjust locale preferences if wrong language is selected
• Use direct URLs for critical documents to guarantee inclusion

Missing Topics from Maps

• Check if topics are published and accessible
• Verify the API token has access to all topics
• Look for errors in the topic extraction logs

Images Not Displaying

• Rapidflare converts embedded images to direct URLs
• Ensure images are published and accessible
• Check that resource URLs are not behind additional authentication