Connecting MetronHR to Power Automate

Power Automate receives deliveries from MetronHR with the trigger "When an HTTP request is received" and calls the REST API with the HTTP action. The HTTP action is a premium action. Data policies in the Microsoft tenant can restrict access to external services.

As of:15. September 2026

In the app directory ofPower Automate there is no ready-made MetronHR entry, and this page claims none. What there is, is the route Power Automate provides for any HTTP service: an incoming webhook as the trigger and an HTTP block for the call. Both are set up in half an hour and need no connector.

The two directions

MetronHR reports of its own accord through Webhooks and answers requests through the REST API. Both routes belong to the Professional plan.

  • MetronHR reports an event

    Block in Power Automate
    When an HTTP request is received
    What to do
    Creates an address when saved. A JSON schema for the body can be generated from a sample delivery, and the fields are then available as dynamic content.

  • Power Automate asks MetronHR

    Block in Power Automate
    HTTP-Aktion
    What to do
    A call to app.metronhr.de/api/v1 with the Authorization header and the bearer token. The answer is processed further with "Parse JSON".

As of 15. September 2026. The interface address is https://app.metronhr.de/api/v1, and what is binding is the app's OpenAPI document.

Reporting published shifts to a Teams channel

A process that works in this shape. Steps one and three happen in MetronHR, the rest inPower Automate.

  1. 1In MetronHR create a target and subscribe to shifts.published.
  2. 2In Power Automate start a flow with the HTTP request trigger and save it.
  3. 3Enter the address it creates as the target in MetronHR and trigger the test delivery.
  4. 4Generate a JSON schema from the sample payload.
  5. 5With the Teams action send a message, taking the fields from data.

What to watch for on thePower Automate side

  • The HTTP action is premium. Without the matching plan there is no outgoing call to MetronHR.
  • Power Platform data policies apply here too. A policy blocking the HTTP connector blocks the route to MetronHR; that is a setting for the Microsoft administration.
  • The trigger address carries an access key in its parameters. It belongs treated like a secret, and the signature check does not replace it.
  • Anyone wanting an assistant rather than a process takes the MCP server in a Copilot Studio agent, not Power Automate.

A key carries only the rights ticked when it was created, per resource "read" or "read and change". For a process that only reports, reading is enough. Anyone who would rather have an AI assistant ask instead of a process takes the MCP server.

Connects MetronHR to Power Automate

Create a key, enter the target, send a test delivery. All of it in the company settings.

See the prices

No credit card, cancel any time

Related

Where to go from here, and what waits for you there.