Connecting MetronHR to the rest of your systems

There are four routes: a REST API for fetching and writing,15 events as webhooks, an MCP server for AI assistants and sign-in through Microsoft Entra ID. Anyone who wants to work without writing code connects through n8n, Make, Zapier or Power Automate.

As of:15. September 2026

Which route for what

The choice depends on who is asking: a system, a process, an assistant, or a person who wants to sign in.

  • REST API

    What for
    A system fetches data regularly or writes some: payroll, controlling, a dashboard of your own.
    Included in
    Professional
  • Webhooks

    What for
    A system should learn at once that something happened, instead of asking on a schedule.
    Included in
    Professional
  • MCP server

    What for
    An AI assistant should answer questions about the business, and optionally change something too.
    Included in
    Professional
  • Single sign-on

    What for
    Signing in with the company's Microsoft account, with account creation on demand.
    Included in
    every plan

As of 15. September 2026. What is binding for the interface is the app's OpenAPI document, not this overview.

The technical details of the first three are on the page about the REST API, webhooks and MCP, and the sign-in is described on the page about single sign-on with Microsoft Entra ID.

What an access point may do, and what it may not

All routes share the same permission model. The rights hang per resource on "read" or "read and change", not on a role and not on all or nothing. A key for payroll therefore gets time entries and absences to read and nothing else.

Personal data under Art. 9 GDPR leaves the product through none of these routes. Bank details, date of birth, social insurance number and any disability status stay inside; for absences the type goes along, not the note. What sits where is set out in the Trust Center.

Questions about the integrations

What we are asked most often about it.

No. There is no MetronHR entry in the directories of Zapier, Make, n8n or Power Automate. The connection runs through the route all four provide for any HTTP service: an incoming webhook as the trigger, an HTTP block for the call. That is set up in half an hour.

The REST API, webhooks and the MCP server belong to the Professional plan, at no extra charge and with no minimum number of licences. They are not included in the Team plan. Sign-in through Microsoft Entra ID is independent of that.

With an API key as a bearer token, created by management in the company settings. The rights are ticked per resource, "read" or "read and change". The plain text appears exactly once; only the checksum is stored.

A system that fetches data regularly: the REST API. A system that wants to know at once when something happens: webhooks. An AI assistant that is meant to answer questions: the MCP server. A process without code of your own: an automation platform with both.

The hours can be output as an Excel or CSV file and fetched through the REST API. A ready-made route into a particular payroll program is not part of the package; MetronHR records hours and does not run payroll on them.

Question not answered here? Every step is explained in the help centre.

Try the connection with your own data

Keys, webhook targets and AI connections are in the company settings.

See the prices

No credit card, cancel any time