No island: hours and personnel data go to your tax advisor, leave and shifts into the calendar, people clock in at a tablet on site – and if you like, you connect your own systems via API and webhooks.
At the end of the month you close it, and your tax advisor gets everything needed for payroll – no timesheets by email.
| What | How it works |
|---|---|
| Payroll report as PDF | Hours, premium hours under § 3b EStG, absences, joiners and leavers and changed master data per employee and month – clearly laid out for your tax advisor. |
| Import file for DATEV LODAS | Hours, premium hours and absence days per personnel number as movement data. You set up the wage type numbers once together with your tax advisor. |
| Excel and CSV export | Payroll report and reports (working time, absences, staff) as a formatted Excel file with filters or as CSV for other payroll software. Plus each employee's monthly times as Excel or CSV and timesheets per project or customer as PDF. |
| Share link for your tax advisor | Your tax advisor downloads PDF, CSV and DATEV file via a protected link with an access code – without a Floowa account. |
| Payslips back to the team | Upload the finished payslips as PDF. Floowa assigns them by personnel number or file name, and everyone only sees their own. |
| Import master data | Import employees from a CSV, Excel or OpenDocument file. Exports from DATEV (personnel master data, LODAS ASCII file) and Lexware work directly; Floowa maps the columns by their names. |
Payroll report, DATEV file and share link are part of the payroll preparation add-on; uploading payslips is part of the Pro plan.
Who is off or on shift when shows up where your team looks anyway.
| What | How it works |
|---|---|
| Calendar subscription | Everyone subscribes to their personal Floowa calendar in Outlook, Google Calendar or Apple Calendar (iCal link). It updates itself. |
| What it contains | Your own absences, the public holidays of your region, your own shifts and – for managers – the absences in the team. |
| Private stays private | For colleagues it only says “absent”, the reason stays private. You can create a new link at any time; the old one then stops working. |
Not everyone sits at a PC. People clock in where they work.
| What | How it works |
|---|---|
| Terminal tablet at the entrance | An Android tablet with the Floowa app (coming soon to Google Play) becomes the time clock: connect it to your account once via QR code, mount it on the wall, done. If you like, only the employees of one department clock in there. |
| With chip, QR code or PIN | Hold an NFC card or key fob to the tablet, show the printed QR badge to the camera or type personnel number and PIN. |
| Even without internet | If the Wi-Fi drops, the tablet stores the punches and sends them later. |
| Smartphone and PC | Employees clock in in the browser on PC and smartphone; Floowa can be added to the home screen like an app. There is also the Floowa app for Android (coming soon to Google Play). |
| No surveillance | No photos, no fingerprints, no location. |
For everything else there is a documented REST API and signed webhooks. Use them to connect Floowa to your ERP, your payroll accounting or automation tools such as n8n, Make or Zapier.
| What | How it works |
|---|---|
| REST API | Read and write employees, departments, hours and time clock, customers, projects and project time, absences, shifts, payroll months, qualifications, inventory, documents and payslips – always within the rights you give the access. |
| Access | Personal API tokens with rights per function and an expiry date, created under Settings → API access. |
| Webhooks | Floowa reports events to an HTTPS address of your choice, signed with a secret key. If delivery fails, Floowa retries several times. |
Floowa reports every request via webhook. A flow in n8n, Make or Zapier fetches the name via the API and posts a message to Microsoft Teams or Slack – with period and number of days.
Your ERP creates or updates employees in Floowa via the API. In return, Floowa reports every change to master data via webhook.
As soon as a month is closed, the event “month closed” arrives. Your system then fetches the monthly figures per employee via the API.
It's that simple: n8n, Make and Zapier receive Floowa's webhooks directly and call the API – no extra app or plug-in needed.
For each webhook you choose which events you want to receive.
| Event | When | Technical name |
|---|---|---|
| Employee created | An employee is created – manually, by import or via the API. | employee.created |
| Employee updated | An employee's master data changes. | employee.updated |
| Employee deleted | An employee is deleted. | employee.deleted |
| Absence requested | Someone requests leave or another absence. | absence.requested |
| Absence approved | A request is approved or an absence is entered directly. | absence.approved |
| Absence rejected | A request is rejected. | absence.rejected |
| Absence cancelled | A request or an absence is withdrawn. | absence.cancelled |
| Time recorded | A time entry is created – when clocking in, when adding it later or at the terminal. | time_entry.created |
| Time changed | A time entry changes, for example when clocking out. | time_entry.updated |
| Time deleted | A time entry is deleted. | time_entry.deleted |
| Month closed | A month is closed in payroll preparation. | payroll.closed |
| Month reopened | A closed month is reopened for corrections. | payroll.reopened |
| Shift published | A shift is published with the shift plan. | shift.published |
| Shift changed | A published shift changes. | shift.changed |
| Shift removed | A published shift is deleted. | shift.deleted |
Authentication, signature, limits and the full reference are in the developer section.