11. Additional data sources and interfaces

Depending on the use case, it may make sense or be necessary to supplement the knowledge base from documents and verified company knowledge with additional data sources. These include, for example, databases, business systems, and other data interfaces that can be connected via modern integration standards such as MCP.

The reason is simple: not everything an AI is supposed to answer or do is contained in documents. Many important pieces of information are “live” and constantly changing, such as prices, inventory levels, customer status, transaction data, tickets, delivery dates, master data, or project information. For the AI to work reliably here, it needs controlled access to the systems in which this data is provided.

What happens in this step?

In this step, it is jointly determined which external systems should be connected and for what purpose. These can be classic databases (e.g. SQL databases), internal APIs, ERP/CRM systems, DMS, ticketing or helpdesk systems, product databases, knowledge systems, or specialized platforms.

Suitable interfaces are then implemented and secured. Depending on the system landscape, this can be done via direct database access, REST APIs, middleware, events—or via standardized connector approaches such as MCP. The goal is always to ensure that the AI does not retrieve data “somehow,” but via clearly defined, tested, and controllable paths.

What is important here is: the AI does not get blanket access to “everything.” It is defined precisely which data fields, tables, endpoints, or functions may be used, which roles this applies to, and under which conditions queries are permitted. In addition, it can be defined whether the AI may only read data or whether it may also trigger actions, for example creating a ticket, pre-filling a quote, or initiating a workflow. If write access is permitted, additional control mechanisms and approvals are generally built in.

Why this step is so important

Without connected live data, AI remains limited to static information in many cases. That is often entirely sufficient for explanations, processes, policies, or product knowledge, but not for tasks that require current states or need to actively use systems.

Connecting additional databases and interfaces ensures that the AI does not guess or work with outdated information. Instead, it can retrieve current, reliable data and combine it with verified company knowledge. This makes answers more precise, processes faster, and tasks more automatable.

At the same time, this step is crucial for clean governance: instead of “somehow having access,” there are defined data paths, traceable permissions, clear boundaries, and controllable results.

What you gain from it

By integrating additional data sources, your AI becomes significantly more capable in day-to-day operations. It can not only explain, but also provide concrete support because it can work with current data.

Examples include the automated answering of status questions (“What is the status of case X?”), preparing quotes with live prices and suitable terms, retrieving product or spare-part information from master data, creating or updating tickets, or context-specific support in customer service with a view of the specific customer case.