Time recording

First the Excel list, then the automatic sync.

Timemaster records working time at the terminal in the workshop or via app and manages holiday requests. For project planning in Linetrack, what counts are the absences that result. To begin with, an Excel import before the planning meeting is enough. Once the routine has proven itself, the sync runs automatically through the REST API.

Via the REST APIExcel import to startREST API for ongoing useHalf days

Timemaster website ↗

In short

Timemaster is connected by Excel import or through the Linetrack REST API. With the Excel import, Linetrack matches absences by name and replaces the state of every person in the file. Through the REST API, a scheduled flow sends absences with type and share of the day, matched by employee number. Working time itself comes from the resource calendar in Linetrack; there is no dedicated Timemaster connector.

Two routes

By file or by interface, with the same result in the plan

In a company with a few dozen employees, the connection does not have to run automatically from day one. We start with what you can already get out of Timemaster today and automate once the benefit is clear.

ExcelRight away

Absences from a list

The Linetrack Excel template takes first name, last name, start, end, type and label. “Upload and overwrite” replaces the state of every person in the file, and the summary lists names that could not be matched to an employee.

  • First name
  • Last name
  • Start
  • End
  • Utilisation type
  • Label

Where in Linetrack: Resources → Management → Import

REST APIAutomatic

Sync on a schedule

Once the route is tested, a scheduled flow takes over the upload. It sends a period's absences to Linetrack and matches them by employee number instead of by name.

  • Employee number
  • Period
  • Type
  • Share of day

Endpoint: PUT /resources/absences/bulk

Half days

The Friday afternoon off

Through the REST API, every absence carries a share of the day. Half a day of holiday then takes only half a day off the capacity, and the workshop keeps planning with the morning.

Resource calendar

Part-time does not come from the terminal

How many hours someone regularly works is set in the resource calendar in Linetrack, part-time or four-day week included. Timemaster only supplies when someone is away outside that. So a part-timer never counts as a full position in planning.

Master data

New colleagues by list or API

New employees come in through an Excel user list with email, names and initials, or through the REST API's master data sync with their employee number. Both take free licences, and nothing is deleted.

  • Email
  • First name
  • Last name
  • Initials
  • Employee number

Where in Linetrack: Company administration → Users → “Upload Excel”

Absence types

Five types are enough

Linetrack distinguishes holiday, sickness, assembly, training and other. We agree with you once how your absence types from Timemaster map onto them, so project management sees at a glance why someone is away.

  • Holiday
  • Sickness
  • Assembly
  • Training
  • Other

In the company

What this means in a smaller machine building company

Monday meeting with current holidays

Every Monday, the workshop manager plans the week with the project managers. Beforehand, the management assistant uploads the current holiday list to Linetrack, and the meeting talks about free capacity instead of shouts across the shop floor.

Part-time in design

A design engineer works Monday to Thursday. Her week is in the resource calendar, her holidays come from Timemaster. For the drawings up to design release, Linetrack counts four days a week, minus her holiday week in June.

From the file to the nightly run

After a quarter of weekly uploads, the company's IT service provider has the sync run every night through the REST API. For the planners only the timing changes: the state is already there in the morning.

Getting started

Three steps from upload to nightly run

  1. 1

    Get the data out of Timemaster

    We look with you at which reports or exports your Timemaster offers for absences and which fields they contain, gladly together with your IT service provider.

  2. 2

    First import by Excel

    You copy the data into the Linetrack template and upload it under Resources → Management → Import. The summary shows straight away which names were not matched.

  3. 3

    Automatic through the REST API

    With an API key holding the resources:write scope, a scheduled flow sends the absences to Linetrack regularly, for example in n8n, Make or as a script on your server.

FAQ

Frequently asked questions

Any questions?

Book a call with our team.

Is Timemaster connected to Linetrack directly?

Not with a dedicated connector. The data comes by Excel import or through the Linetrack REST API, triggered by a flow your IT or service provider sets up.

Why does the Excel import match by name and the API by employee number?

The Excel import is meant for lists the way people keep them and recognises names with umlauts or in the form “Last name, First name”. The REST API is built for automatic operation and works with the unique employee number, so two employees with the same name are never mixed up.

What happens if a holiday is withdrawn in Timemaster?

With the Excel import, “Upload and overwrite” replaces the state of every person in the file. Through the REST API, every run delivers the complete state of the period: a withdrawn holiday is missing from it and is removed in Linetrack.

Does this also work if Timemaster runs on our own server?

Yes. The flow can run inside your network and calls the Linetrack REST API over HTTPS. No incoming connection into your network is needed.

The platforms and brands mentioned belong to their respective owners. Mentioning them describes the technical connection and does not imply a partnership or certification.