Skip to content
This site is under construction. Content, screenshots, and workflows may change at any time.

Source types

Every source you add goes into your team’s Knowledge Base. In Knowledge Base, click Add Source and pick a category on the left. This page describes each type in the order the dialog shows them.

CategoryTypeUse it for
Website LinksURLOne public webpage
Website LinksURL ListMany specific pages from a text file
Website LinksCrawlA whole site or section, by following links
Website LinksSitemapThe pages listed in a sitemap
Files & TextFileA PDF, TXT, or Markdown document
Files & TextTextContent you paste in
WPManageNinjaFluent SupportTickets from your Fluent Support site
MCPMCP serverLive, read-only tools from a remote MCP server

Website and Fluent Support sources can refresh on a schedule: Never, Daily, Weekly, or Monthly. Files and pasted text don’t refresh; replace them when they change. See Keep knowledge up to date.

Website sources must use public web addresses. FluentChat rejects addresses that point to private or internal networks.

URL

Indexes the content of a single page.

FieldWhat to enter
Source URLThe page address, for example https://www.example.com/pricing. Up to 2,048 characters.
Source titleOptional. A name to show in the Knowledge Base.
Scheduled refreshHow often to fetch the page again.

URL List

Indexes every page in a list you upload.

FieldWhat to enter
Source FileA .txt file with one URL per line, up to 5 MB. Lines that aren’t valid URLs are skipped. A list can hold up to 5,000 URLs.
Scheduled refreshHow often to fetch the pages again.

Crawl

Starts at one page and follows links to index the pages it finds.

FieldWhat to enter
Start URLWhere the crawl begins, for example https://www.example.com/docs.
Source titleOptional. A name to show in the Knowledge Base.
Scheduled refreshHow often to crawl again.

The crawl stays on the same site and under the start URL’s path. Starting at https://www.example.com/docs covers /docs and pages below it, not /blog. A crawl indexes up to 5,000 pages.

To keep pages out of a crawl, add them to Blocked URLs before the next crawl.

Sitemap

Indexes the pages listed in an XML sitemap.

FieldWhat to enter
Sitemap URLThe sitemap address, for example https://example.com/sitemap.xml.
TitleA name for the source.
LocationsAfter FluentChat reads the sitemap, choose which listed pages and nested sitemaps to include. Up to 5,000 locations.
Scheduled refreshHow often to read the sitemap again.

If the dialog shows No locations found in this sitemap, check that the address returns a valid XML sitemap.

Files & Text

File

Uploads one document.

FieldWhat to enter
Source FileA PDF, TXT, or Markdown (.md) file, up to 20 MB.
Source titleOptional. A name to show in the Knowledge Base.

Text

Adds content you paste, such as an FAQ or a policy that isn’t on your website.

FieldWhat to enter
TitleA name for the text. Required.
ContentThe text itself, up to 500,000 characters.

WPManageNinja

Fluent Support

Indexes tickets from a WordPress site running Fluent Support, so bots can answer from past support conversations.

FieldWhat to enter
DomainYour WordPress site address.
UsernameA WordPress user that can read the tickets.
Application PasswordA WordPress application password for that user.
Refresh ScheduleHow often to fetch tickets again.
StatusWhich ticket statuses to include: new, active, or closed. Choose at least one.
ProductOptional. Limit tickets to one product.
TagsOptional. Filter by tags with Includes any of, Doesn’t include any of, Includes all of, or Includes none of.
Ticket CreatedOptional. Limit tickets by creation date.

MCP

MCP server

Connects a remote Model Context Protocol server so bots can look up live information through its tools. MCP tools run during conversations; they aren’t indexed as documents.

FieldWhat to enter
Server nameOptional. Leave blank to use the server URL as the name.
Server URLThe server’s remote HTTP endpoint, for example https://example.com/mcp.
AuthenticationOptional headers the server needs, such as Authorization: Bearer …. Header values are stored securely and aren’t shown again after you save.
Allowed toolsAfter FluentChat reads the server’s tools, check the ones bots may use. Clearing every tool turns off live access.

Read-only access. Bots only use MCP tools to read information. Tools your server marks as write or destructive are never offered to bots. If your server doesn’t label its tools, give FluentChat read-only credentials.

Once added, an MCP server shows Connected or Not checked. Open it to Refresh tools after your server publishes new ones. Bots use an MCP server only if it’s part of their knowledge selection. Deleting the server removes its tools from every bot in the team.

Next steps