Hudu

Map Level groups to Hudu companies and keep their device assets current without manual re-entry.

Overview

Devices in mapped groups sync into Hudu as assets. Hudu does not create tickets from Level alerts.

How it works

  • Map devices to the right company.

    Match any Level group or subgroup to the company it belongs to in Hudu.

  • Keep documentation current.

    Devices in mapped groups sync into Hudu as assets when the integration is enabled.

  • See the sync as it runs.

    Group statuses and the Level Events tab expose progress and failed requests.

Set up the integration

  • Generate a Hudu API key.

    Create a dedicated key in Hudu for the Level connection.

  • Connect Hudu in Level.

    Add the Hudu URL and API key, then test the connection.

  • Map companies and enable sync.

    Choose which Level groups feed each Hudu company and turn the integration on.

Explore other integrations.

Connect Level to the rest of your stack.

DeskDayPSA and TicketingAlgaPSAPSA and TicketingRegentraPSA and ComplianceHaloPSAPSA and TicketingConnectWise PSAPSA and TicketingilertIncident ResponseZestMSPPSA and TicketingLevel Public APIDeveloper Platform

Questions about this connection.

What does the Hudu integration sync?

Devices in mapped groups sync into Hudu as assets. Hudu does not create tickets from Level alerts.

Does Level replace Hudu?

No. Level is the RMM. Hudu stays the system of record for its own job.

Where is the setup guide?

The setup steps live in the Hudu integration guide.

Is there a free trial?

The first 10 devices are free forever. No time limit.

Does Hudu create tickets?

No. Hudu is documentation. Devices in mapped groups sync into Hudu as assets.

Keep Hudu documentation aligned with Level.

Start free, follow the setup guide, and keep Hudu assets current with the managed fleet.

Start for freeBook a demo