Skip to main content
For an agent to not just inform but carry out real transactions, it calls tools in the flow – small, clearly scoped actions like “classify the request”, “book an appointment”, or “check a balance”. Where a tool comes from and whether it talks to an external system depends on its category.

Three categories of tools

Built-In Tools

Platform-native tools that are available in every agent without any configuration. No external system, no credentials. Example: classify.

MCP Servers

Connect any MCP server. The agent reads its tools; you enable per agent what it is allowed to use.

Domain-System Connectors

Connect to your practice or domain software. Provides domain-specific tools (e.g. appointment booking) and talks to your system for real.
This chapter describes how you select and configure integrations in the portal. The technical implementation of your own interface is not part of this documentation.

Domain-System Connectors

A connector links an agent to an external domain system and provides it with the matching tools. Each tool is assigned to exactly one connector.

Available connectors

In the Connectors tab of an agent you see the available connector types (with description, number of supported tools, and the supported authentication methods) as well as your already active connectors.
The demo connectors respond with hardcoded sample data and are ideal for trying out a flow without a real domain system. For production use, choose a domain-system connector like planorg PVS or an MCP server.

Configuring a connector

1

Choose a connector type

Pick the connector type that matches your system.
2

Enter the base URL

Enter the address (base URL) at which your system provides the interface.
3

Enter credentials

Enter the authentication (see below). Which fields appear depends on the chosen method. Secret values are stored encrypted.
4

Enable tools

Enable the tools the agent is allowed to use through this connector.

Authentication

Domain-system and MCP connectors support two authentication methods. Which one is available is defined by the respective connector type.
Your credentials are stored encrypted. Secret fields are no longer shown in plain text in the portal after saving – when editing, leave the field empty to keep the stored value.

Example: appointment booking

The most mature use case is telephone appointment booking for healthcare via the planorg PVS connector. Among other things, it provides tools to identify patients, list doctors and calendars, determine availability, and book appointments for known and new patients. In your flow you chain these tools together into the complete booking conversation.
After setting up an integration, you should thoroughly check the agent with a test call before you go live.