HR & absences

A new absence in Factorial, a new state in capacity.

Factorial is HR software for small and mid-sized companies, with leave management, approvals and a team calendar. Because Factorial can report changes by webhook, Linetrack does not have to wait for the night: shortly after it is entered, an absence shows up in project planning. New employees of a growing team come in the same way.

Via the REST APIWebhook as triggerComplete state per periodMaster data by employee number

Factorial website ↗

In short

Factorial is connected through the Linetrack REST API. When Factorial reports a new or changed absence by webhook, a flow in Make, n8n or Zapier reads the period's state from the Factorial API and sends it to Linetrack, matched by employee number. New employees are created by the master data sync. There is no dedicated Factorial connector.

How it works

An event from Factorial, the full state to Linetrack

The webhook only says that something has changed. The flow answers with the whole picture of the period. That way no change gets lost, even if a notification fails to arrive once.

Webhook

Factorial gives the signal

A webhook subscription in Factorial calls your flow in Make, n8n or Zapier as soon as an absence is created or changed. Without a webhook, the same flow runs on a schedule.

  • Make
  • n8n
  • Zapier
  • Schedule
Full state

Whole periods, not single changes

Instead of sending only the changed absence, the flow delivers every absence of the affected employees in the period. Linetrack reconciles against that state: new entries are added, cancelled ones disappear, entries made in Linetrack itself stay.

  • Period
  • Employees
  • Empty list = no absence

Endpoint: PUT /resources/absences/bulk

TypesHalf days

Holiday, sickness, half a day

Every absence arrives with type and share of the day. Half a day counts as half a day, and planning sees whether someone is on holiday, off sick or on a training course.

  • Holiday
  • Sickness
  • Assembly
  • Training
  • Other
  • Share of day
Growth

New employees at the pace of hiring

Anyone created in Factorial comes to Linetrack with employee number, email and initials, straight into the right resource group if you wish. The sync updates existing records and only writes the fields it is given.

  • Employee number
  • Email
  • Initials
  • Resource group
  • Portfolio

Endpoint: PUT /resources/users/bulk

Not synchronised

Working time stays in Linetrack

If you also use shift or working-time features in Factorial, that data stays there. Each person's regular week is set in the resource calendar in Linetrack, and the sync does not change it.

Planning

Team calendar and project view

In Factorial's team calendar, the department head sees their own people. In Linetrack, the same absence sits next to the tasks of every project, in the resource histogram and in the KPI dashboard with net capacity and over- or under-coverage.

  • Resource view
  • Resource histogram
  • KPI dashboard
  • Net capacity

Day to day

When the plan knows the same day

Sick note in FAT week

On the Monday of FAT week, the controls programmer calls in sick and the team lead records it in Factorial. Shortly afterwards his task in Linetrack carries a warning, and the project manager settles before noon who takes over the PLC changes for the customer.

A growing assembly team

A special machine builder is expanding its assembly team and hires throughout the year. Every new fitter is in Linetrack with his Factorial record and in the assembly group before the assembly manager plans him for the next site job.

Holiday called off

A design engineer moves her holiday out of the week before the delivery date to finish the production drawings. Factorial reports the change, the flow sends the new state, and in Linetrack her capacity for that week is back.

Setup

Webhook, flow, safety net

  1. 1

    Prepare access

    In Linetrack, an administrator creates an API key with the resources:write scope. For Factorial, the flow needs API access to your Factorial account.

  2. 2

    Connect webhook and flow

    The webhook from Factorial starts a flow in Make, n8n or Zapier. It reads the absences of the affected employees and sends the state to Linetrack via an HTTP module.

  3. 3

    Nightly run as a safety net

    On top of that, a nightly run reconciles the coming months. If a webhook ever goes missing, planning is still right the next morning.

FAQ

Frequently asked questions

Any questions?

Book a call with our team.

Is there a ready-made Factorial integration in Linetrack?

No. The connection is made of the Factorial API, the Linetrack REST API and a flow in between. Your IT, your IT partner or we together with you build it.

Why does the flow send the whole period and not just the change?

Because the Linetrack API expects a complete state per period. That makes the sync robust: a missed or duplicated notification still leads to the right result with the next run.

How are employees matched between Factorial and Linetrack?

By employee number, which has to be the same in both systems. For master data, the email address serves as a fallback as long as no employee number is stored in Linetrack yet.

Can everyone in Linetrack see why someone is away?

Only if you want them to. In the privacy-compliant variant only the period arrives; Linetrack shows a neutral “Absence” and matches by employee number, initials or Linetrack ID.

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