What a connection is
An MCP server or an API that an admin has added to the company, with its own credentials and its own list of what the assistant may call. The model sees those calls as tools, next to the SAP ones, and decides when a question needs them. You ask once; it reads SAP and the other system and puts the two beside each other.
Examples
- "Where is order 41000739?" SAP says it was delivered to a carrier on Tuesday; the carrier's API says it is out for delivery this morning.
- "What has the web shop sold since Friday that we have not picked yet?" The shop's API lists the orders; SAP says which have a delivery.
- "Before I quote BLUESKY, what did they last complain about?" The CRM's notes, the open SAP invoices, in one answer.
- Our own products expose MCP as well: BE Messaging for the SMS thread with a customer, BE Hub for the state of a machine.
What stays the same
- Reads run freely, within what the connection allows. The admin decides which calls exist; the model cannot invent one.
- Anything that would change a system, in SAP or elsewhere, is prepared, shown and waits for Confirm, under the same rights as the SAP tools.
- Every call is a recorded turn: which system, what was asked, what came back, how long it took.
- Customers and callers never reach these connections unless the admin scopes one to them. By default they are staff tools.
Which systems
The integrations page lists the ones we are asked about most, by category, and how automation platforms such as Zapier extend the reach.
Adding one
Tell us what the system is and what you want to be able to ask. An MCP server is added with its address and key; an API with its base URL, authentication and the handful of calls that matter. Each is tested read-only first, like the SAP connection.