Indexed sources in AI Search

  • Release version: Yokohama
  • Updated July 2, 2026
  • 5 minutes to read

    • Indexed sources designate ServiceNow AI Platform® tables and external document sets with alphanumeric text and string field content that you want to make searchable. AI Search ingests text and string fields from table records or external documents and stores their searchable alphanumeric content in its search index.

    For instructions on creating an indexed source, see Create an indexed source.

    Indexed source types

    AI Search supports the following indexed source types.
    Internal indexed source
    An internal indexed source retrieves alphanumeric content and metadata from text and string fields on ServiceNow AI Platform records. It includes a unique name and a reference to a ServiceNow AI Platform table with records that you want to make searchable. AI Search extracts and indexes searchable alphanumeric content and metadata from text and string fields on records in this table and in any of its child tables that you configure for indexing.
    AI Search excludes some ServiceNow AI Platform tables from indexing. You can't define indexed sources for these excluded tables or their derived tables. For a list of excluded tables, see ServiceNow AI Platform tables excluded from AI Search indexing.
    You can't index remote tables with internal indexed sources. To index content from a remote table, create an external indexed source.
    External indexed source
    An external indexed source retrieves alphanumeric content and metadata from text and string fields of documents in an external repository or a remote table. It includes a unique name and a reference to an external content schema table instead of a ServiceNow AI Platform table. For more details on configuring indexed sources for external content, see Indexing and searching external content in AI Search.
    Note:
    AI Search doesn't index Unicode characters from the High Surrogate Area (code units in the range U+D800 to U+DBFF). Characters from this range are replaced with spaces during indexing.

    Indexing and search performance

    Search performance for AI Search is affected by several customer-controlled factors related to content indexing. Changes to these factors can impact search performance as follows.
    Index size
    Indexing more content produces a larger index, which takes more time to search. Avoid indexing content that isn't needed for search.
    Indexing large source tables, such as the Task [task] table and tables that extend it, can add significant numbers of records to the AI Search index.
    Number of indexed sources
    An index with more indexed sources takes longer to search than one with fewer indexed sources. This is true even if the two indexes are the same size.
    Number of indexed fields
    Increasing the number of fields you index across your indexed sources makes the system take longer to find search results. This effect is independent of index size and number of indexed sources.
    Indexing frequency
    The more often your indexed content is synchronized and updated, the more often search will compete with indexing for compute resources, increasing search response time. This is especially pertinent for indexed sources with frequently modified fields.

    Indexed source retention policies and filter conditions

    To limit the size of your index and the frequency of index updates, you can define retention policies and filter conditions for your indexed sources.

    As an example, you can define a retention policy for an indexed source to exclude records that are more than two years old. This policy keeps your search results more current and reduces the size of your index. Changes made to the excluded records don't trigger index updates, so this policy also reduces indexing frequency.

    Similarly, you can define a filter condition for an indexed source that excludes source table records with a specific status, such as Open. This filter condition reduces the number of records indexed from the source table, which in turn reduces the total amount of data you index. Excluding open records that have frequent updates also reduces indexing frequency.

    AI Search also uses your retention policy and filter condition settings to automatically purge stale records from the index, reducing its size.

    To learn more about creating retention policies and filter conditions for your indexed sources, see Indexed source retention policies and filter conditions.

    Note:
    Retention policies are required for indexed sources that index records from the Task [task] table or tables that extend it. They are optional for other indexed sources.

    Indexed source attributes and field settings

    You can configure attributes and field settings for an indexed source to control indexing behavior for source records. Attributes control the indexed source's behavior at the record level, while field settings define its behavior for individual fields on indexed records. For more information, including lists of available attributes and field settings, see Indexed source attributes for AI Search and Field settings for AI Search.

    Indexing content from an indexed source

    After you define an indexed source, AI Search begins automatically indexing to reflect changes to records in the selected source table and its specified child tables. The results of all record create, update, and delete operations in these tables are reflected in the search index. AI Search doesn't index content from unmodified records in these tables until you perform a full table index. For more information on indexing behavior, including steps for full table indexing, see Indexing content from AI Search indexed sources.
    Note:
    The pre-configured indexed sources included with AI Search only index content from text and string fields on source records. When searching records from these indexed sources, you can use numeric fields to facet or filter your search results, but you can't find records using their numeric field values. To search on a record's numeric field values, copy them into a text or string field so they can be indexed.

    Indexing content from knowledge articles

    When indexing content from records in the Knowledge [kb_knowledge] table, AI Search defaults to including content defined in knowledge blocks. Administrators can override this default behavior and configure AI Search to exclude content from knowledge blocks when indexing knowledge articles. For details on making this change, see Exclude knowledge block content from the AI Search index.

    Multiple indexed sources for the same ServiceNow AI Platform table

    You can't create more than one indexed source for a single ServiceNow AI Platform table. However, plugins and applications may define duplicate indexed sources for a ServiceNow AI Platform table. For example, the base system includes an indexed source defined for the User [sys_user] table, but a plugin or application might define a second indexed source for this table under a different name.
    Note:
    Only one indexed source can be active at a time for a given ServiceNow AI Platform table. The system makes duplicate indexed sources for a table inactive by default. Before you can make one of these duplicate sources active, you must edit the currently active source and make it inactive. AI Search only indexes content and metadata from active indexed sources.