Skip to main content
teamspace

Built-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, and through an open REST API for your own tools.

teamspace as a light concept illustration: in the centre a card One data record with the entries Customer, Project, Hour and Document, around it connection cards linked by orange lines for DATEV, Microsoft Teams, Outlook, bank interface and calendar, and on the right a highlighted orange card Open REST API as a connector for your own tools.

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.

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 more

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 more

Microsoft 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 more

Outlook add-in

From an email in Outlook you create a contact, a ticket or a task in teamspace directly, without switching applications.

Learn more

Calendar via CalDAV

The teamspace calendar syncs via CalDAV with Outlook, Apple Calendar and other programs, so appointments stay maintained in one place.

Learn more

teamSync 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 more

Open 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.

teamspace REST API as a light concept illustration: on the left a teamspace card with a connector symbol, from which three labelled connections lead to a BI tool card, an accounting card and a card Your own application, each connection carrying the label read and write.

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 progress

What we are working on right now: AI in teamspace and a connection via MCP.

Two topics are in active development. We describe them here as an outlook, not as a finished feature, so you know where things stand.

  • AI that works inside your environment

    We are developing AI features that assist within your teamspace environment. Your client data is not used to train models, as described on the security page.

  • Connection via MCP

    Through the Model Context Protocol (MCP), AI assistants should in future be able to access teamspace directly and under control. This connection is in progress and not yet released.

teamspace outlook as a light concept illustration with two cards: on the left a card AI in teamspace with a lock symbol and the note no training with your data, on the right a card MCP with a plug symbol and the label AI assistant connects to teamspace, both with an in-progress note.

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 use AI, and what happens to our data?
AI features inside teamspace are currently being worked on, they are not yet generally available. Your client data is not used to train AI models. How teamspace handles your data is set out on the security page.
Does teamspace support MCP for AI assistants?
A connection via the Model Context Protocol (MCP), through which AI assistants can access teamspace under control, is in development. It is not yet released; we can give you a date as soon as it is available.

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.