Automations

Zapier, Make and n8n: released in the ERP, planned in Linetrack.

When order processing releases an order in the ERP, the workflow creates the project from your template, with project manager and order number. When HR approves a holiday in Personio, those days drop out of assembly planning shortly afterwards. For Personio there is also the direct connection; automation is the second option. The building blocks are on this page; if you like, we set up the first workflow together with your IT.

In short

Linetrack can be automated with Zapier, Make and n8n without writing code. The HTTP module of each tool calls the Linetrack REST API and authenticates with an API key that an administrator creates in Linetrack and restricts to individual areas such as projects:write. A workflow is started by a webhook from the source system, for example the ERP or Personio, or by a fixed schedule.

How it works

From the key to the first run.

1

Create a key

An administrator creates a key in Linetrack under company administration → API keys and grants only the areas the workflow needs. For syncing absences, resources:write is enough.

2

Set the trigger

Personio or your other HR system reports an approved holiday by webhook. If your ERP cannot send webhooks, the workflow checks for new orders on a schedule, for example every hour.

3

Call Linetrack

The HTTP module sends the data to the REST API, with the key in the X-API-KEY header. You decide in the tool which trigger fields go where.

Examples

Six workflows from project business.

Each card shows the trigger, the result and the REST API endpoint the workflow calls. On the right you see how to set up the call in Zapier, Make or n8n. The example there creates a project from a template.

Holiday approved in Personio → capacity adjusts

HR approves two weeks of holiday for a commissioning engineer. Personio reports this by webhook, the workflow sends the current state to Linetrack, and exactly those days drop out of assembly planning. If you prefer, only the period arrives, without the absence type. This is the second option: for Personio there is also the direct connection.

PUT /resources/absences/bulkTo the Personio integration →

Order released in the ERP → project from template

Order processing releases the order for a special-purpose machine in SAP or another ERP. The workflow creates the project from your template, assigns it to the right group, sets the project manager and takes the order number as external reference. Linetrack calculates the dates from the start date.

POST /projects

Defect reported → open point in the project

During commissioning at the customer's site, the fitter notices a missing safety cover and reports it through a form or a chat message with the project number. The issue then sits as an open point in the right project, not in somebody's inbox.

POST /projects/{id}/open-points

Monday, 7 a.m. → key figures in the Teams channel

Every Monday at 7 a.m. the workflow fetches the key figures of all running projects and posts them to the project management team's Teams channel. Everyone going into the weekly meeting has already read the numbers.

GET /kpis/company

Bookings from ERP or time tracking → workload

Service assignments, training or hours on other orders kept in another system also occupy employees in resource planning. The workflow transfers these days as workload, half days included. The source system stays in charge: each run replaces the previous state.

PUT /resources/utilizations/bulk

Start of the month → workload per resource group in Excel

On the first working day of the month the workflow reads capacity and workload per resource group for the coming months and files them as an Excel sheet for controlling and management. A bottleneck in electrical design shows up in the monthly review, not when the wiring diagrams are missing.

GET /kpis/resource-groups

Security

One key per workflow, and you can block it at any time.

Permissions per area

You grant reading and writing separately per area, for example projects:read or resources:write. The key-figure report for Teams gets by with kpis:read. If it tries anything else, Linetrack rejects the call.

Bound to your company

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

Block and rotate

If the service provider who built the workflow is no longer involved, an administrator blocks the key or replaces it. This applies from the next call.

Every call logged

Linetrack records time, method, path and result. We store the key itself only as a hash.

Practical examples

How do machine, plant and special-purpose builders use Zapier, Make and n8n with Linetrack?

Linetrack is connected to Zapier, Make or n8n through the REST API: a workflow takes data from the ERP and writes it into the plan, or it reads key figures from Linetrack and passes them on. The three scenarios show this for woodworking machinery, water and wastewater technology and agricultural special-purpose machinery; they are typical cases, not customer reports.

Woodworking machinery

Goods receipt in the ERP ticks off the milestone

Starting point
A manufacturer of CNC machining centres and edge-banding machines builds machines to customer variants. Spindles, vacuum pumps and controllers arrive as bought-in parts, and assembly starts only when all of them are there. The goods receipt is booked in the ERP, but the milestone “Bought-in parts complete” in Linetrack is only ticked off when purchasing remembers or the assembly lead asks.
How Linetrack is used
IT builds a workflow in n8n. The ERP sends no webhooks, so a Schedule Trigger checks hourly for newly booked goods receipts. Once the last item of an order has arrived, the HTTP Request node sets the milestone to done through the Linetrack REST API, addressed by its ERP ID. The API key gets only the scopes the workflow needs.
Result
Assembly planning sees the milestone as done shortly after the goods receipt and releases the machine for build-up without asking purchasing. Design, production and assembly work from the same status as the ERP.
Linetrack in mechanical and plant engineering →
Water and wastewater technology

Suppliers from the ERP as project partners

Starting point
A plant builder for pumping stations and membrane filtration systems buys membrane modules, pumps and valves from changing suppliers. Acceptance at the operator's site depends on a fixed shutdown window. When a module is late, project management first has to look up the right contact at the supplier, because suppliers were entered in Linetrack by hand and are often out of date.
How Linetrack is used
A Make scenario reads the suppliers from the ERP overnight and transfers them through the REST API as project partners, with supplier number and contacts. Purchasing keeps maintaining the master data only in the ERP. Project management then assigns the supplier to the project.
Result
Ahead of FAT, SAT and acceptance, project management finds the supplier on the project with the number from the ERP and the current contact. A delay is settled directly, without searching the ERP or old emails.
Integrating suppliers in Linetrack →
Agricultural special-purpose machinery

Schedule status per order back to sales

Starting point
A special-purpose builder of implements and bodies for agriculture delivers to fixed seasonal windows. Sales promises delivery dates to dealers and asks project management for the status almost daily. The answers come from conversations and Excel lists. When a bought-in part is late, the picture often changes overnight.
How Linetrack is used
A Zapier Zap fetches the key figures of all running projects through the REST API each morning, with traffic light, overdue tasks and on-time rate, each with order and item number. The Zap stores them where sales already works, in the order list or in the ERP as far as its interface allows. The key for this needs only kpis:read.
Result
In the conversation with a dealer, sales sees the order's traffic light with the status from the morning and asks only when it is red. Project management answers fewer status requests and uses that time for planning.
Linetrack in special-purpose machinery →

Examples without a reference label describe typical workflows in the respective industry and therefore name no company.

FAQ

Frequently asked questions

More questions?

We walk through your first workflow with you in a meeting.

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.