HR software

HR approves in HRworks, project management plans with the result.

In HRworks, your holiday requests, sick notes and employee master data come together. Linetrack takes from it what changes capacity: approved absences and new employees. A nightly flow between the HRworks API and the Linetrack REST API brings both into project planning, without anyone retyping a list.

Via the REST APIApproved absencesNew employees with resource groupNightly sync

HRworks website ↗

In short

HRworks is connected through the Linetrack REST API. A flow in Make, n8n, Power Automate or a script reads approved absences and employee data through the HRworks API and sends them to Linetrack, matched by employee number. Absences arrive with type or without a reason, and new employees are created with their resource group. There is no dedicated HRworks connector.

What arrives

From the approved request to the first working day

HRworks knows every absence along with its request and approval. Project planning needs less: who is away when, and who is joining. That is exactly what the sync collects.

Absences

Approved absences

The flow sends what is approved: holiday, sickness, training and other, with a share of the day for half days. Open requests are left out until they are decided.

  • Employee number
  • Start
  • End
  • Type
  • Share of day

Endpoint: PUT /resources/absences/bulk

Mapping

Which type goes where

Together with you, we map your HRworks absence types onto the five types in Linetrack. A business trip to a customer is not one of them: in Linetrack it is not an absence, and whoever travels stays available for project work.

  • Holiday
  • Sickness
  • Assembly
  • Training
  • Other
Onboarding

New employees with group and portfolio

With employee number, email, names and initials, the master data sync creates new colleagues and assigns them to an existing resource group and portfolio. Linetrack sends no invitation email; your administrator assigns roles in permission management.

  • Employee number
  • Email
  • First name
  • Last name
  • Initials
  • Resource group
  • Portfolio

Endpoint: PUT /resources/users/bulk

Licences

Licences stay within limits

New users are only created while free licences are available. Anything beyond that comes back as skipped, and existing employees are still updated. Nobody is deleted, not even after leaving the company.

  • Created
  • Updated
  • Skipped, no licence
  • Free licences
Nightly

One run per night

A scheduled flow queries the HRworks API and sends the state to Linetrack, for the next twelve months for example. Whatever your planners entered in Linetrack themselves stays untouched.

  • Make
  • n8n
  • Power Automate
  • Script
Privacy

Away, no reason given

If no absence reason should leave HR, the flow uses the privacy-compliant variant. Linetrack then stores only the period and shows “Absence”.

Endpoint: PUT /resources/absences/bulk/privacy-compliant

In the project business

HR data that affects delivery dates

Bridge days before design release

In May, HR approves a good number of bridge days in mechanical design. The next morning, the head of design sees in Linetrack that hours up to design release are getting tight and moves the date with the project manager in good time.

First day in electrical design

A new electrical design engineer starts on the first of the month. As soon as HR has created him in HRworks, the next nightly run brings him into Linetrack with his resource group. Project management assigns him tasks from day one.

A business trip is not a holiday

A service technician flies out for three days to an acceptance meeting at the customer's site. HRworks holds the trip for travel expenses, but it does not go to Linetrack as an absence. The project manager keeps him planned for the acceptance documentation, which he writes on the road.

Process

How the nightly sync comes about

  1. 1

    Agree types and scope

    With HR, we decide which HRworks absence types are transferred, and whether with type or without a reason.

  2. 2

    Set up access

    In Linetrack, an administrator creates an API key with the resources:write scope. On the HRworks side, your HRworks administrator sets up API access.

  3. 3

    Build the flow

    In Make, n8n or Power Automate, a flow reads employees and absences from HRworks and calls the two Linetrack endpoints for master data and absences.

  4. 4

    Check the response

    Every run reports what was created, updated, skipped or rejected. In the first weeks, we are glad to go through these reports with you.

FAQ

Frequently asked questions

Any questions?

Book a call with our team.

Is there a ready-made HRworks integration?

No, Linetrack has no dedicated HRworks connector. Both systems have an API, and a flow in middleware connects them. We are happy to check with you and your IT partner which data your HRworks account provides for this.

Do open holiday requests reach Linetrack too?

You decide that in the flow. We recommend sending only approved absences, so planning does not count on requests that may still be turned down.

Do new employees get access to Linetrack automatically?

They are created as users but receive no invitation email. They can request the “Set password” email themselves at any time through sign-in support, and your administrator assigns further roles.

What happens when someone leaves?

The master data sync deletes no employees. Whoever leaves the company stays in Linetrack until your administrator deactivates them, and their project history is kept.

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