Interface
Master data comes from DATEV
Personnel number, department, start date. Maintained once, identical everywhere.
daily
hubInterfaces and connectors
If it has an interface,we connect it.
Payroll, ERP, HR system, industry software: teamly picks up data where it is already maintained. Nine systems have a ready-made route, for everything else we build the connector inside the project. And when a vendor offers no open interface, we say so instead of promising it.
Servers in GermanyISO 27001 data centresDPA under Art. 28 GDPR
Systems
What teamly already talks to
These systems have a documented route because we have built it in real projects. Four of them have their own page with data fields and setup effort.
Payroll and accounting
DATEV
Timesheets, leave and sick notes travel from the app into DATEV payroll, either through a secured API or the LODAS import.
Payroll and accounting
sage
Employee master data and absences. Which sage product line you run is clarified before the field mapping.
HR and industry software
Personio
Bidirectional: master data, org structure and absences. The Personio API is available from the Professional plan; Essential customers get a CSV sync.
HR and industry software
MediFox DAN
Master data and structures from MediFox DAN flow straight into teamly, with no double entry. The most common connector in care projects.
ERP
SAP
HR and organisational data from SAP. The route depends on the module and release; typically a service on the SAP side plus field mapping.
Collaboration and identity
Microsoft 365
SSO through Entra ID with SAML 2.0 or OpenID Connect, an optional Teams bridge, and links to SharePoint documents that keep their M365 permissions.
Collaboration and identity
Google Workspace
SSO plus calendar and document links. Frontline staff without a Google account keep signing in with a personnel number.
CRM and sales
HubSpot
Deals and service tickets trigger push messages in teamly, contact data is readable in the app. On request teamly writes activities back.
Statutory notices
aushang-digital.de
Statutory workplace notices as a portal, embedded in teamly by link or QR code. A sister product from 2peaches.
Your own system
Custom
Your own ERP, time tracking, POS or maintenance software: if it has an interface, we build the connector as part of the project.
The list grows with every project. If your system is missing, that does not mean it cannot be done: as a rule we clarify feasibility directly with the vendor.
Routes
Four routes into the app, and when each one fits
An integration is not magic, it is a question of transport. teamly uses exactly four routes. Which one applies is not teamly’s choice but the other system’s: what it offers as an interface decides how current the data can be and in which direction it flows.
REST API
The default route. teamly calls the other system’s API, or exposes its own REST API so your IT team can write and read data. Authentication uses tokens, never a user password. The interval is yours to pick; with Personio, for example, we sync every 15 minutes.
Webhook
Instead of asking, teamly gets called. The other system sends an event the moment something happens: deal won, ticket escalated, shift changed. teamly turns that call into a message or an update inside the app. The right choice for anything that has to reach staff immediately.
File import and SFTP
The route for systems that only know exports. A CSV or Excel file lands on a secured channel, either an SFTP drop or an upload in the admin backend, and teamly reads it against an agreed schema. Less elegant than an API, but sturdy, auditable and set up in a day.
SSO with SAML 2.0 and OIDC
Not a data channel but an identity channel. Your office staff sign in with the company account they already use, and teamly verifies it against Entra ID or another identity provider. teamly stores no passwords. Frontline staff without a company email keep signing in with a personnel or phone number.
- read and write · minutes to real time
- push from the other system · visible within seconds
- one direction · schedule as agreed, usually nightly
- identity · MFA through your identity provider
All four routes can be combined in one project. A typical setup looks like this: master data by API from the HR system, payroll data as a file to accounting, urgent alerts by webhook, office login through SSO. What works in your case is checked before you sign, not during the rollout.
Process
From idea to a running interface
Integration work runs alongside app development, not after it. It is part of onboarding and is steered by your customer success manager.
- 1
Record systems and fields
Which software do you run, in which version, and who administers it? We note every field that should be visible in the app, and every one that has to flow back.
- 2
Check feasibility, with the vendor if needed
We read the interface documentation. If there is none or it is unclear, we approach the vendor directly. The result is a statement you can rely on: works by API, works by file, does not work.
- 3
Agree mapping and master system
Which system wins when values disagree? For master data usually the HR system, for shifts and content teamly. This is written down, otherwise two systems end up arguing over the same personnel number.
- 4
Test run with real data
A sync on a test environment with a real slice of your data. Your department checks the values field by field before anything goes into production.
- 5
Go live and monitoring
The interface goes live with the app. Failed runs raise an alert to your administrator and to us, with a log of what did not get through.
1 to 2
weeks for a standard connector
3 to 6
months until your app goes live
4
transport routes, combinable
9
systems with a documented route
Limits
Where an integration does not work
The line "if it has an interface, we connect it" carries one important condition: the interface. These six points come up regularly in projects, and they are here so you do not hear about them for the first time at kickoff.
No interface, no live sync
Software without an API and without an export cannot be connected cleanly. We do not do screen scraping or bots that drive a user interface: too brittle with every vendor update, too risky for data protection.
No access through user accounts
teamly works with technical credentials, a token or a certificate. We do not store your employees’ personal logins to operate a third-party system, even when that would be the faster route.
Some vendors require a higher plan
The Personio API starts at Professional, so does the HubSpot API. Whether your current plan unlocks the interface is checked upfront. Vendor charges are billed by the vendor, not by us.
File import is not real time
Where only an export exists, data is as current as the last run. A nightly schedule means someone hired today shows up in the app tomorrow. Fine for master data, not for a shift change at 6 a.m.
A sync is not a migration
A running interface keeps two systems aligned. It does not replace the one-off import of legacy data from a retired tool. That is a separate step in the project with its own effort.
Time tracking runs through the integration
teamly has no time-tracking module of its own. Hours are captured in the app and handed to the leading system, DATEV for example. If you need full time-account management, you keep your specialist system for that.
aushang-digital.de
Statutory notices in the app instead of on the wall
aushang-digital.de is a portal for the statutory workplace notices German employers have to display. It comes from 2peaches GmbH in Reichenbach im Vogtland, the same company that builds teamly.
Employers in Germany must make certain laws accessible on site, among them the Working Hours Act, the Occupational Safety Act, the Youth Employment Protection Act, the Maternity Protection Act, the General Equal Treatment Act, the Minimum Wage Act and the Federal Leave Act. The usual answer is a folder in the break room that is out of date after the next amendment.
aushang-digital.de keeps that catalogue current as a portal and recommends per industry which laws apply to you. The enterprise tier shows the notices in six languages: German, English, Turkish, Russian, Polish, Arabic. Access needs no login and works through a link or QR code, and access is logged. Pricing starts at 9 euros net per month for one location, as of August 2026.
- laws in the catalogue per industry
- over 50laws in the catalogue per industry
- languages in the enterprise tier
- 6languages in the enterprise tier
- entry price per month, net
- 9 €entry price per month, net
- updates after a change in law
- ongoingupdates after a change in law
How it attaches to teamly
- 1
You set up your notice catalogue in aushang-digital.de, once per location.
- 2
The portal returns a link and a QR code. Both stay stable, even when a law changes.
- 3
The link goes into teamly as a tile in the knowledge base or as a document. Your staff tap it and see the current version.
- 4
For proof of communication, combine it with a news post and read receipt in teamly. That documents who has seen the information.
Note: aushang-digital.de and teamly are operated by the same company, 2peaches GmbH. Embedding needs no custom development because the portal is delivered by link and QR code. There is no obligation to book it, teamly works without it.
FAQ
Common questions about integrations
What IT, HR and the works council want to know before connecting.
Is it true that anything can be connected?
Anything with an interface. That is not a slogan but the condition: a documented API, a webhook, or at least a data export. Without either, a reliable sync is not possible, and we say so in the first conversation. For vendors we do not know yet, we get in touch and clarify feasibility before you sign.
Does teamly have its own API?
Yes, a REST API for custom integrations at enterprise level. Your IT team can create users, publish content and read data through it. Authentication uses tokens and every call is logged.
How long does an integration take?
A standard connector such as DATEV, Personio or Microsoft 365 takes 1 to 2 weeks and runs alongside onboarding. A connector for a system new to us takes longer because feasibility has to be clarified with the vendor and tested. Your app itself goes live in 3 to 6 months.
What does an integration cost?
Standard connectors are included in teamly plans from Business upwards. A custom connector is quoted as part of the project and appears with a price in your offer. Whatever your vendor charges for its interface, such as a higher plan or an unlock through your tax adviser, is billed by them directly.
Which system wins in a conflict?
You decide during setup. For employee master data the HR system is usually master, for mobile content and shift plans it is teamly. The rule is documented per field so it is clear later which value prevails.
Is the data transfer GDPR compliant?
Transfers are encrypted and processing is covered by a data processing agreement under Article 28 GDPR. teamly data sits in German data centres certified to ISO 27001. Only what the purpose requires is handed over, and the fields involved are listed in the mapping document your works council can review.
Can we start without an integration?
Yes, and many customers do. teamly runs fully with a one-off user import by file. The connector then follows in a second phase, once the app has settled into daily use.
What happens when a sync fails?
Failed runs are logged and reported, to your administrator and to us. The last valid state stays visible in the app, no data disappears. Once the cause is fixed, the sync catches up.
Personal. Direct. No script.
Is teamly a fit for your business?
30 minutes, your industry, your real questions. Alexander, Maximilian or Michael listen first. If it fits, the demo with all your decision-makers comes next.
schedule30-minute callblockNo sales pressureverifiedMade in Germany