Back to Search AI connectors list Front is a customer communication hub that streamlines conversations, enhances team collaboration, and provides a unified view of messages from various channels. Using the Search AI connector for Front, you can ingest and index content from your Front knowledge bases and enable efficient search on that content.Documentation Index
Fetch the complete documentation index at: https://koreai.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Specifications
| Specification | Details |
|---|---|
| Repository type | Cloud |
| Supported content | Knowledge Base Articles |
| RACL support | Yes |
| Content filtering | No |
Integration Steps
- Generate an API token in Front.
- Configure the Front connector in Search AI.
Generate an API Token
Search AI uses Front APIs to access content and requires an API token to authenticate.- Sign in to your Front account with admin access.
- Navigate to Settings > Developer.
- Go to the API token tab. Click Create Token, enter a name, and select the scopes required to access knowledge base articles. Click Create.
- Copy the generated API token — you will need it for the connector configuration.
Configure the Front Connector in Search AI
- Navigate to the Connectors page.
- Click Add Connector and select Front from the list.
-
Provide the following details:
Field Description Name Unique name for the connector API Token Token generated in Front - Click Connect to authenticate and establish the connection.
Content Ingestion
After connecting, go to the Configuration tab to set up content synchronization. Use Sync Now for an immediate sync, or configure Schedule Sync to automate future syncs. Search AI ingests Knowledge Base Articles from all knowledge bases in the connected Front account, including article content and metadata in JSON format. View ingested content on the Content tab.RACL Support
Access control is based on the visibility type of each knowledge base in Front. Internal Knowledge Bases Each internal knowledge base is identified by a uniqueknowledge_base_id, which is stored as the sys_racl value for all articles in that knowledge base.
Example — an article in a knowledge base with id = knb_deip:
sys_racl field is automatically set to *, granting universal access.