Connecting MetronHR to Make

Make receives deliveries from MetronHR with the "Custom Webhook" module and calls the REST API with the HTTP module. The API key goes into a header as a bearer token. There is no ready-made MetronHR connector in the directory, and none is needed.

As of:15. September 2026

In the app directory ofMake there is no ready-made MetronHR entry, and this page claims none. What there is, is the route Make 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 Make
    Custom Webhook
    What to do
    Make creates an address and derives the shape of the payload from the first delivery. The test delivery MetronHR triggers at the target is well suited to that.

  • Make asks MetronHR

    Block in Make
    HTTP module, "Make a request"
    What to do
    Method, address and headers are yours to choose. Authorization with Bearer plus the key; the answer can be parsed as JSON and used further.

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.

Mirroring new time entries into a spreadsheet

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

  1. 1In MetronHR create a target and subscribe to time-entries.created and time-entries.updated.
  2. 2In Make start a scenario with a Custom Webhook and enter the address.
  3. 3Trigger the test delivery so that the connection is established.
  4. 4Set a filter, for instance only entries on a particular project.
  5. 5With the spreadsheet module create a row, taking the fields from data.

What to watch for on theMake side

  • Make determines the data structure from the first delivery. Anyone starting with the test delivery gets the shape of ping rather than that of the business event; for the field mapping, wait for a real delivery or set the structure by hand.
  • Every operation counts towards the plan. A scenario reacting to every time entry can get expensive quickly in a large business; a filter step right behind the webhook is worth it.
  • The signature check goes through another HTTP or Tools module. Leaving it out means accepting every delivery that knows the address.

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 Make

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.