Content Aggregation

Whatfix uses an in-house proprietary software tool to crawl content from your knowledge base repository. No third-party application is used to fetch content.

Integrating a repository with dynamic URLs is NOT RECOMMENDED. A dynamic URL changes its value based on certain parameters in the application. When integrating a repository, Whatfix uses a page's URL to uniquely identify the page. Integrating a ...

Yes, similar to other Whatfix content, repository links can be displayed contextually using Tags . For example, tagging your repository links with a Role Tag makes the link show only to end users with the corresponding role. In addition to indivi...

Whatfix cannot crawl a repository with dynamic URLs. A repository with dynamic URLs indicates that multiple users are accessing the same repository but through different URLs. Let’s say you have three customers: A, B, and C. When they need support...

Yes, Whatfix can fetch repository content in any language. However, some Whatfix features may not be compatible with content in languages other than English. For example, QuickRead supports content only in the European languages supported by Whatfix...

Yes, Repository integration works with the Export or Self Hosted mode of deployment . After adding the Repository to a Self Help segment, the end-user search restricts results to titles only. The Self Help search fetches content based on the text...

No, Whatfix fetches only the content that you provide access to. For example, when using SharePoint, Whatfix enables you to mention which content folder we can access and fetch the content from. Note: If the specified f...

You may want to delete an outdated or duplicate repository link present in the Production stage of the Whatfix dashboard. Note Only an Account Manager can perform the following task. For more information about avail...

Whatfix requires up to 36 hours to crawl every 2,000 links per repository. However, Whatfix enables integration of multiple repositories simultaneously. The time required for Whatfix to integrate a repository depends on the number of links it cont...

Whatfix retains the repository content data for 2 years post-termination of the contract. If Whatfix needs to delete, update, or modify data anytime during the term of engagement or post termination, contact your Whatfix representative or reach out ...

Whatfix enables integration of up to 5 content repositories. To increase this limit, contact support@whatfix.com .

Crawl up to 5000 links from your Knowledge Base (KB). Whatfix takes up to 36 hours to crawl 2000 links. If you have more than 2000 links, the crawling process will accordingly take more time. For more information, see Content Aggregation .

The default sync frequency for a repository is 7 days. Whatfix enables you to set the sync frequency based on your requirements. Note: Whatfix requires a time interval of 3 days between two syncs. For more information, se...

Outdated content that remains in your Content Repository might not be suitable for display in Self Help. Whatfix enables you to not display an article from your Content Repository in Self Help by preventing it from getting crawled. Make this excepti...

Yes, all content fetched from the Content Repository remains encrypted at all times. Whatfix encrypts the content as soon as it reads it from your Knowledge Base, during transfer, and keeps it encrypted even after receiving it on its servers.

Whatfix requires the URL of the knowledge base repository to integrate with the application. If the repository is password protected, provide the necessary credentials to Whatfix to access the content. Note The provided c...

Whatfix provides out-of-the-box integrations for repositories in the following applications: SharePoint OneDrive ServiceNow Freshservice Confluence Salesforce ShareFile Freshdesk Zendesk Seismic Whatfix ...

Currently, Whatfix can fetch content such as DOCs, PDFs, PPTs , and other HTML-based content.

Whatfix stores all content in the Whatfix Cloud according to data residency guidelines. Note: Data is stored in Virginia, USA (East) and Arizona, USA (West) for Non-EU customers. Data is stored in Switzerland an...