DATEV interface
Outgoing and incoming invoices, credit notes and travel expenses go to DATEV Unternehmen online as a posting batch, one per client, without a CSV file. Certified, from the enterprise edition.
Learn moreBuilt-in connections and an open API in one place.
Most handovers happen inside teamspace without any interface at all, because every module shares the same data record. To the outside, teamspace connects through ready-made integrations such as DATEV, Microsoft Teams and Outlook, through an open REST API for your own tools, and through an MCP server of its own for your AI assistants.
Built-in integrations
These connections are already part of teamspace.
Integrations you can use without a project of your own. Depending on the edition, with no separate middleware.
Bank interface
The bank interface reconciles incoming payments and automatically marks the matching invoice as paid. You only assign unclear payments by hand. From the enterprise edition.
Learn moreMicrosoft Teams
You create Teams meetings in the teamspace calendar and join them with one click. Every Teams call appears in the CRM call list and turns into a contact, a time, a ticket or a follow-up. From the office edition.
Learn moreOutlook add-in
From an email in Outlook you create a contact, a ticket or a task in teamspace directly, without switching applications.
Learn moreCalendar via CalDAV
The teamspace calendar syncs via CalDAV with Outlook, Apple Calendar and other programs, so appointments stay maintained in one place.
Learn moreteamSync telephony
The teamSync telephony interface connects your phone system with the CRM, so incoming calls show the contact and conversations are logged as an activity.
Learn moreOpen REST API
For everything else, the open REST API connects teamspace with your tools.
Where no ready-made integration exists, you read and write data through the REST API. It is included from the enterprise edition and described in the developer documentation, with endpoints, authentication and schemas.
-
Connect BI and reporting tools
Metrics from teamspace flow into Power BI, Looker or your own reports, without anyone exporting lists and copying them together.
-
Accounting without a dedicated connector
For Lexware, Sage or SAP there is no ready-made connector. The exchange runs through standard exports or the REST API.
-
Import master data
You bring existing contacts, projects or staff data over at the start through Excel or the REST API, instead of typing them in.
-
Exchange records with other systems
Tickets and records can be synced with adjacent systems, so both sides see the same state.
Why little interfacing is needed on the inside
The most important integration is the one you never have to maintain.
Many companies connect time tracking, projects, invoicing and CRM through interfaces between separate programs. Each of these connections has to be set up, monitored and checked after every update. In teamspace this effort disappears, because every module shares the same data record: a logged hour belongs to the project, the invoice and the utilisation at the same time, without anyone transferring it.
You only need an open API at the boundary to the outside, for example to accounting, to a BI tool or to an industry application. That is exactly where the REST API is available. Inside teamspace, the integration is already done.
- No middleware between the modules, no duplicate maintenance of master data.
- Updates do not change internal interfaces, because there are none.
- The open API steps in precisely where teamspace meets other systems.
In testing, general release in September 2026
Your AI assistants may reach teamspace – with exactly the rights of the person behind them.
teamspace comes with its own MCP server, from the office edition upwards. Through the Model Context Protocol (MCP) you connect teamspace to AI assistants such as Claude, ChatGPT or Cursor, and you stay in control: for each connection you decide which tools are available and who may use it. The connection is built and running; it will be released for everyone in September 2026. On a test server you can see it today.
-
One connection per purpose, not one for everything
You create as many MCP connections as you need: a read-only one for the whole team, one for the HR department, one for invoice controlling. Each connection gets its own address, its own selection of tools and its own permission group.
-
Nobody gains rights through the AI
Three barriers stand in the way: the release of the configuration, the OAuth consent and the signed-in user's own rights. The last one cannot be switched off. Anyone who may not see a personnel file in teamspace will not see it through an AI assistant either. Write access is a separate permission that you grant on its own, and the audit records who allowed which client to do what, and when.
-
Your AI, your tokens, your decision
For the AI features inside teamspace you enter your own AI account: endpoint, model and key. Your administrator enables each feature individually, such as condensing long ticket histories or analysing reports. teamspace does not run a language model of its own and does not pass your data to any third-party AI service.
A short call
Which integration fits your setup?
Are you planning a connection to a particular system or your own application via the API? We clarify the requirements in a short first call and tell you what goes through a ready-made integration and what goes through the REST API.
Common questions about integrations and the API
Is there an API?
Yes. teamspace provides a REST API that lets you export, import or connect data with your own tools, for example with BI tools, accounting or your own applications. The API is included from the enterprise edition; endpoints, authentication and schemas are described in the developer documentation in the help centre.
Which systems are connected without programming?
Ready-made integrations cover DATEV Unternehmen online, the bank interface for payment reconciliation, Microsoft Teams, the Outlook add-in and the calendar via CalDAV. DATEV and the bank interface belong to the enterprise edition, Microsoft Teams from the office edition.
Is there a ready-made connector for Lexware, Sage or SAP?
No. For Lexware, Sage and SAP there is no dedicated connector. Data exchange runs through standard exports or the REST API. What makes sense in your case is something we clarify in the first call.
Can we bring existing data over at the start?
Yes. Master data such as contacts, projects or staff data can be brought over through Excel imports and the REST API, instead of entering it by hand.
Does teamspace support MCP for AI assistants?
Yes. teamspace comes with its own MCP server, through which AI assistants such as Claude, ChatGPT or Cursor access teamspace under control. You create as many connections as you need: each with its own address, its own selection of tools and its own permission group. The connection is built and running; it will be released for everyone in September 2026. On a test server we can show it to you in the first call today. The setup is documented in the help centre, from the introduction to MCP to connecting teamspace to Claude.
Which editions include MCP and the AI features?
The MCP server and the AI features are included from the office edition upwards, at no extra charge, so you do not need the enterprise edition for them. The REST API, by contrast, is only available from enterprise. The two solve different problems: the API is for software that always does the same thing, MCP is for questions you do not know in advance. The trade-off is set out in the help centre under MCP or API.
Can someone gain more rights through an AI assistant?
No. Three barriers stand in the way: releasing the configuration to a group or person, the OAuth consent, and the signed-in user's own rights. The last one cannot be switched off; it applies to every call exactly as it does in the interface. Anyone who may not see a personnel file in teamspace will not see it through an AI assistant either. Write access is a separate permission that you grant on its own, and the audit records who allowed which client to do what, and when. The details are set out under security and permissions with MCP.
Which AI does teamspace use, and what happens to our data?
teamspace does not run a language model of its own. For the AI features inside teamspace you enter your own AI account, that is endpoint, model and key, and your administrator enables each feature individually. That means you decide which provider processes your data and where, and no additional processing arrangement arises through teamspace. Your client data is not used to train AI models. Background in the help centre: your AI, your data. How teamspace handles your data is set out on the security page.
Which AI features are available in teamspace today?
Two are live: the AI condenses a long ticket history down to the essentials, and it pulls the key findings out of a report. Both only appear once an AI of your own is connected in the tenant. More will follow by September 2026, among them automatic sorting of incoming tickets. The current state is listed in the help centre under available AI features.
Does the AI write our invoices?
No, and that is deliberate. Invoices in teamspace are generated from rules, which makes them 100 per cent correct according to the rules you have set, rather than 99 point something as with a language model. The AI may assist and check, for example by pointing out anomalies. It does not write an invoice, and it does not decide. You stay in control.
Would you like to connect teamspace to your systems?
In a short first call we go through your existing tools and show which are connected out of the box and what runs through the open REST API.