Automation with Power Automate

Flows in Microsoft 365 that keep Linetrack up to date as well.

Approvals sit in SharePoint lists, requests come in through Forms, coordination happens in Teams. At the right point, a Power Automate flow calls the Linetrack REST API through the HTTP action with an API key. These are the same workflows as with Zapier, Make or n8n, built in the tool your IT already manages.

Via the REST APIHTTP action with X-API-KEYTriggers from Microsoft 365Scheduled flows

Power Automate website ↗

In short

Power Automate connects to Linetrack through the REST API: the HTTP action of a flow calls https://app.linetrack.de/api/integrations/v1 and sends the API key in the X-API-KEY header. The flow is triggered by an event in Microsoft 365, such as a new item in a SharePoint list, an email in Outlook or a response in Forms, or by a fixed schedule. That way it creates projects from templates, transfers absences or reads KPIs from Linetrack.

Triggers and actions

What a flow can do in Linetrack

Each card links a Microsoft 365 trigger to what the flow does in Linetrack. Behind it is always an HTTP call to the REST API, with the key in the header and permission for only the areas the flow needs.

SharePointprojects:write

An approval list becomes a project

Order processing keeps new orders in a SharePoint list. When an item changes to “approved”, the flow creates the project from the matching template. The dates follow from the start date and the project calendar.

  • Order number
  • Customer
  • Project manager
  • Template
  • Start date
  • Portfolio

Trigger: item created or modified in SharePoint

Outlookprojects:write

A customer email as an open point

When a change request from the customer arrives in the project mailbox, the flow creates an open point in the project. It reads the order number from the subject and finds the project by its external ID.

  • Subject
  • Order number
  • Open point

Trigger: new email in an Outlook mailbox

Formsprojects:write

FAT defects as to-dos

During the factory acceptance test your inspector records each defect in a form. Every response becomes a to-do on the acceptance task, and the project manager sees in Linetrack what is still open before shipment.

  • Defect
  • Assembly
  • To-do on the task

Trigger: new response in Microsoft Forms

Teamskpis:read

Weekly status in a Teams channel

Every Monday a scheduled flow reads the KPIs of all running projects and posts in the project managers' channel where tasks are overdue or the traffic light is red.

  • Traffic light
  • Overdue tasks
  • Schedule adherence

Trigger: schedule, action: message in Teams

SQL Serverresources:write

Absences from an SQL database

Some time-tracking systems store their data in SQL Server. A daily flow reads the absences there, without the reason if you prefer, and sends the current state to Linetrack. If the database sits in your own network, access runs through the on-premises data gateway.

  • Period
  • Type
  • Personnel number
  • Half days
Schedulekpis:read

KPIs back to SharePoint

A nightly flow writes traffic light, completion and capacity per resource group into a SharePoint list or an Excel table in SharePoint. Controlling keeps working there without needing a Linetrack login.

  • Completion
  • Traffic light
  • Net capacity
  • Planned hours

From project business

Where a flow removes double entry

Project start without retyping

Order processing sets the order for a special-purpose machine to “approved” in the SharePoint list. A few minutes later the project manager finds the project in Linetrack, with tasks from the template up to design release and the FAT.

Absences from time tracking

A Linetrack customer already runs a daily flow that transfers absences from the SQL database of its time-tracking system to Linetrack. Assembly planning no longer has to enter holidays and sick leave by hand.

Monday meeting with the current state

When the project managers meet on Monday, the weekly status is already in the Teams channel. The meeting starts with the overdue tasks, not with the question of who is where.

How to build the flow

Four steps to the first run

  1. 1

    One key per flow

    An administrator creates a separate API key in Linetrack for each flow, for example projects:write for creating projects or resources:write for absences. If a flow is retired, you block exactly its key.

  2. 2

    Choose the trigger

    You start the flow with the matching Microsoft 365 trigger, for example a modified SharePoint item, or as a scheduled cloud flow.

  3. 3

    Set up the HTTP action

    Method, the Integration API address and the X-API-KEY header are all it takes; you build the body from the trigger's fields. The “Parse JSON” action breaks Linetrack's responses down for the next steps.

  4. 4

    Test and monitor

    A test run shows every step with its input and output. Later you find errors in the flow's run history, and Linetrack logs every call.

Practical examples

How do plant builders, special-purpose machine builders and building-services companies use Power Automate with Linetrack in practice?

A Power Automate flow calls the Linetrack REST API through the HTTP action and keeps projects, open items and KPIs up to date. Three typical flows from machinery and plant engineering, special-purpose machinery and building and energy services, described as scenarios rather than customer reports.

Machinery and plant engineering

Defects from the factory acceptance test become to-dos

Starting point
During the factory acceptance test of a production line, the inspector walks through the plant with the customer. The defects end up on paper or in an Excel list and reach the project days later. By the time design and assembly hear about them, the delivery date has often been confirmed.
How Linetrack is used
The inspector records each defect with assembly and description in a Microsoft Forms form. A flow starts on every new response, finds the project through the external ID and creates a to-do on the acceptance activity through the HTTP action. The flow's API key carries only projects:write.
Result
On the day of the test, the defects already sit as to-dos on the acceptance activity. Design and assembly see them in the project instead of digging them out of an email. The inspector keeps working in the form.
Linetrack in machinery and plant engineering →
Special-purpose machinery

Change requests from the project mailbox as open items

Starting point
Customers of a special-purpose machine builder send change requests to a shared project mailbox, often in the middle of design. The emails are read, forwarded and eventually noted in a list. Which order a request belongs to is settled by a phone call in the end.
How Linetrack is used
A flow starts on every new email in the mailbox, reads the order number from the subject and looks up the matching project in Linetrack through the external ID. There it creates an open item with the email subject through the HTTP action. A key with projects:write is enough.
Result
The change request sits in the right project before anyone has forwarded the email. Project management checks whether it affects dates or purchased parts and decides together with sales. The mailbox stays the inbox, the item is managed in Linetrack.
Linetrack for special-purpose machinery →
Building and energy services

Project KPIs for controlling in SharePoint

Starting point
A company doing electrical design, control cabinet building and commissioning reports project status to management every month. Controlling works in Excel and SharePoint and has no Linetrack access. The project managers send the figures by email.
How Linetrack is used
A nightly flow reads status light, completion and net capacity per resource group with a key for kpis:read and writes them to a SharePoint list. The key is read-only, so the flow changes nothing in Linetrack.
Result
Controlling finds the figures in the morning in the list it works with anyway. The project managers no longer have to send anything, and Linetrack remains the source of the figures.
Linetrack in building and energy services →

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

FAQ

Frequently asked questions

Any questions?

Book a call with our team.

Does the HTTP action need a premium licence?

Microsoft lists the HTTP action as a premium connector, as it does SQL Server and the on-premises data gateway. The flow therefore usually needs a Power Automate Premium licence for the account it runs under. Your licensing partner knows the exact terms of your agreement.

Can Power Automate reach a database in our network?

Yes, through Microsoft's on-premises data gateway. It runs on a server in your network and connects to the database. The flow then sends the data it has read to Linetrack.

How does Power Automate differ from Zapier, Make or n8n?

For Linetrack, it does not: all of them call the same REST API with the same key model, and the recipes on the Automations page apply just the same. Power Automate is the natural choice when your processes already live in SharePoint, Outlook and Teams and your IT wants to manage flows centrally.

What happens when a flow fails?

Power Automate records the error in the run history. With the “Run after” setting you add a notification that tells your IT when a step fails. In Linetrack every call can be traced with time, path and result.

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