Time tracking with OptiControl

Absences from OptiControl, in capacity planning every day.

OptiControl by OptiTime records working time and plans staff, equipment and vehicles, with a particular focus on construction companies. Linetrack takes the absences from it every day: a Power Automate flow reads them from OptiControl's SQL Server database and sends them to the REST API. If you prefer, only the period arrives, without the reason.

Via the REST APIDaily syncPrivacy-compliant without reasonHalf days

OptiTime / OptiControl website ↗

In short

OptiTime / OptiControl is connected through the Linetrack REST API. A daily Power Automate flow reads the absences from OptiControl's SQL Server database and transfers them to Linetrack, either privacy-compliant with the period only or with a type such as holiday or sick leave, half days included. Employees are matched by ID, short code or personnel number.

What is transferred

Absences from OptiControl, as detailed as needed

The focus is on absences, because they determine capacity. How much Linetrack learns about the reason is up to you, through the choice of endpoint. Linetrack has no dedicated OptiControl adapter; the data arrives through the REST API.

PrivacyNo reason

The period only

In the privacy-compliant variant the flow sends start and end, but neither type nor description. Linetrack shows the entry neutrally as “Absence”, so planning only learns that someone is unavailable.

  • Start
  • End
  • Employee

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

With typeHalf days

Absences with type

If planning should see why someone is away, the flow sends the type along. You define once in the flow which OptiControl code maps to which type. Half a day of holiday arrives as half a day and reduces capacity accordingly.

  • Holiday
  • Sick leave
  • Assembly
  • Training
  • Other

Endpoint: PUT /resources/absences/bulk

Matching

Matching by ID, short code or personnel number

For each absence the flow names the employee by Linetrack ID, short code or personnel number. If the personnel number is maintained identically in OptiControl and Linetrack, it is the most reliable key.

  • Linetrack ID
  • Short code
  • Personnel number
DailyFull state

A daily state instead of single messages

Once a day the flow sends the complete state for a period. Whatever was cancelled in OptiControl therefore disappears from Linetrack too. Entries your planners made directly in Linetrack are left untouched.

  • Period
  • Full state
  • Only API entries replaced
Master data

Employee master data if needed

The same route works for the employees themselves: an endpoint creates or updates them by personnel number. Nobody is deleted, and the sync takes your licences into account.

  • Personnel number
  • First name
  • Last name

Endpoint: PUT /resources/users/bulk

Power AutomateSQL Server

The route through Power Automate

OptiControl keeps its data in an SQL Server database. Power Automate reads it, through the on-premises data gateway if the database is in your own network, reshapes the rows and calls the Linetrack API with the HTTP action.

  • SQL Server
  • Data gateway
  • HTTP action
  • X-API-KEY
  • resources:write

Scenes from planning

What planning needs the absences for

An assembly team for the site

Assembly management puts together the team for installing a line at the customer's site. Because absences from OptiControl arrive in Linetrack every day, no fitter who is on holiday that week ends up in the plan.

Sick leave before commissioning

If the commissioning engineer calls in sick, Linetrack has it after the next run, shown only as an absence in the privacy-compliant variant. The project manager sees the gap on the task and finds a replacement before the customer is left waiting.

Summer weeks in the KPI dashboard

In the KPI dashboard the net capacity of assembly drops noticeably during the holiday weeks. Management sees this before promising a customer a commissioning date in August.

How it runs

Three building blocks for the daily sync

  1. 1

    A key with resources:write

    An administrator creates an API key in Linetrack that may write resources and absences and nothing else.

  2. 2

    A query on the OptiControl database

    Your IT or IT partner decides which tables the absences come from and how the codes correspond to the types in Linetrack. This is also where you decide whether the reason goes along.

  3. 3

    A daily flow

    A scheduled Power Automate flow reads the absences for the period and sends them to Linetrack. Linetrack logs every call.

FAQ

Frequently asked questions

Any questions?

Book a call with our team.

Is there a ready-made OptiControl interface in Linetrack?

No, Linetrack has no dedicated adapter for OptiControl. The data comes in through the Linetrack REST API, triggered by a Power Automate flow or another tool that can read the database.

Does it have to be Power Automate?

No. Any tool that can read the OptiControl data and send an HTTP request will do, for example n8n on your own server or a script from your IT partner. Power Automate is the obvious choice if you use Microsoft 365 anyway.

Does Linetrack learn why someone is away?

Only if you use the endpoint with type. In the privacy-compliant variant, only the period arrives. Which variant fits is best agreed in advance with the works council and the data protection officer.

Do booked hours come from OptiControl too?

The connection described here transfers absences and, if needed, employee master data; nobody books working hours in Linetrack itself. We are happy to check with you and your IT partner whether further data from OptiControl is worth taking over.

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