Automations

Automate Linetrack with Zapier, Make and n8n.

Connect Linetrack to your systems without custom code: projects are created from orders in the ERP, absences come from Personio, key figures go to your team every Monday. It all runs on the Linetrack REST API.

In short

Linetrack can be automated with Zapier, Make and n8n. The tools call the Linetrack REST API through their HTTP module, signed in with an API key that your administrator creates in Linetrack and restricts to exactly the permissions needed. Workflows are triggered by webhooks from your other systems, such as Personio or the ERP, or on a schedule.

How it works

Three steps to your first automation.

1

Create an API key

An administrator creates a key in Linetrack under company administration → API keys and chooses what it may do – for example projects:write or resources:write.

2

Choose a trigger

The workflow starts with a webhook from your source system – for example as soon as an absence is entered in Personio – or on a fixed schedule.

3

Call Linetrack

The HTTP module of Zapier, Make or n8n calls the REST API, with the key in the X-API-KEY header.

Examples

Workflows you can use right away.

Six examples from everyday project work, each with the matching REST API endpoint. On the right you see how to set up the call in each tool.

Personio → employees and absences

When an employee is created or an absence is entered in Personio, Personio reports it via webhook and the sync runs right away – without names or absence types if you prefer. Alternatively it runs on a schedule, for example every night.

PUT /resources/absences/bulk

New order → new project

As soon as an order is created in the ERP, Linetrack creates the project from your template – with the order number as its reference.

POST /projects

Form → open point

Complaints or change requests from a form end up as an open point in the right project.

POST /projects/{id}/open-points

Weekly status in Teams

Every Monday at 7 a.m. the key figures of all running projects go to your team as a message.

GET /kpis/company

Time tracking → workload

Hours booked in time tracking flow into resource planning as workload.

PUT /resources/utilizations/bulk

Capacity in the monthly report

Once a month, workload per resource group lands with controlling as an Excel sheet.

GET /kpis/resource-groups

Security

One key per automation, with exactly the permissions it needs.

Permissions per area

Reading and writing are separated per area, for example projects:read or resources:write. A call outside these permissions is rejected.

Bound to your company

The key belongs to your company and a technical account that does not use a user licence.

Block and rotate

An administrator blocks a key or replaces it with a new one. This takes effect from the next call.

Every call logged

Time, method, path and result are recorded. The key itself is only stored as a hash.

FAQ

Frequently asked questions

More questions?

Book a meeting with our team.

Do we need programming skills?

No. Zapier, Make and n8n call the REST API through their HTTP module. You enter the method, address and API key and map the fields with a few clicks.

What data can an automation write to Linetrack?

Projects – empty, from a template or with a complete plan –, tasks and dependencies, to-dos and open points, employees, absences and workload, and project partners. Key figures and capacity can be read.

How does an automation react to changes right away?

Through webhooks of the source system: Personio, many ERP systems and form tools report new entries to Zapier, Make or n8n immediately. Where there is no webhook, the workflow runs on a schedule.

Who creates the API key?

An administrator of your company in the “API keys” tab of company administration. A technical user is created in the background that does not use a user licence.

Can we run n8n ourselves?

Yes. n8n runs in the cloud or on your own servers. Linetrack only needs your n8n to reach app.linetrack.de over HTTPS.