Connecting MetronHR to n8n

n8n receives webhooks from MetronHR with the Webhook node and calls the REST API with the HTTP Request node. The API key goes into the credentials as a bearer token, and the delivery's signature can be verified in a Code node. There is no ready-made MetronHR node.

As of:15. September 2026

In the app directory ofn8n there is no ready-made MetronHR entry, and this page claims none. What there is, is the route n8n 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 n8n
    Webhook-Knoten
    What to do
    Creates an address that is entered as the target in MetronHR. The headers come through in full, so webhook-id, webhook-timestamp and webhook-signature are available.

  • n8n asks MetronHR

    Block in n8n
    HTTP-Request-Knoten
    What to do
    A call to app.metronhr.de/api/v1 with the authentication "Header Auth" or "Generic Credential": header Authorization, value Bearer plus the key.

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.

Writing approved holiday into a team calendar

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

  1. 1In MetronHR create a webhook target and subscribe only to absences.approved.
  2. 2In n8n create the Webhook node and enter its production address as the target.
  3. 3In the Code node verify the signature and stop on a mismatch.
  4. 4With the calendar node create the entry, taking the period and the person from data.
  5. 5In MetronHR trigger the test delivery and check the run in n8n.

What to watch for on then8n side

  • The signature belongs verified before the body is processed. A Code node can form the HMAC-SHA256 over the id, the timestamp and the raw text; for that the unchanged body has to be available in the Webhook node.
  • When self-hosting, the address has to be reachable from outside. MetronHR checks against internal networks when the target is created and does not accept an address in a private range.
  • Duplicate deliveries are possible. webhook-id stays the same across every retry and works as the key against processing something twice.

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 n8n

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.