Navigation
10.24. Level RMM Integration: Sync Groups and Ingest Alerts from level.io
Connect Level (level.io) to AlgaPSA with an API key, map Level groups to clients, sync devices, and push alerts into tickets through a Level automation webhook.
Level (level.io) organizes endpoints into a group hierarchy, and this integration mirrors that into AlgaPSA: groups map to clients, devices in mapped groups sync into Assets, and Level alerts become routed tickets through an automation webhook you create in Level. Level is an Enterprise Edition integration.
For the model all RMM integrations share, see How RMM Integrations Work in AlgaPSA. For alert rules and maintenance windows, see Turn RMM Alerts into Tickets.
Connect AlgaPSA to Level
- Create an API key in Level under Settings > API.
- Navigate to Settings > Integrations > RMM in AlgaPSA and select Level.
- Paste the key into the API key field on the Level Connection card.
- Click Save Configuration, then Test Connection. A successful test marks the integration Connected and shows the connection time.
Map Level groups and sync devices
The Sync & Group Mappings card drives discovery and device sync:
- Click Discover Groups. AlgaPSA imports Level's group hierarchy into the mapping table.
- Assign each group you manage to an AlgaPSA client using the Mapped Client dropdown on its row.
- Click Run Device Sync. Devices from mapped groups become AlgaPSA assets.
Two mapping behaviors are worth knowing:
- Subgroups inherit. A subgroup without its own mapping uses the nearest mapped ancestor, so mapping a client's top-level group usually covers its whole tree.
- Unmapped groups are skipped. Devices in groups with no mapping (and no mapped ancestor) do not sync.
The summary line above the table tracks your progress: mapped groups, devices, and active alerts.
Push alerts with a Level automation
Level cannot register webhooks through its API, so you create one in Level yourself. The Alert Webhook card gives you the three pieces to paste:
| Field | What it is |
|---|---|
| Webhook URL | The AlgaPSA endpoint Level posts alerts to. |
| Header | X-Alga-Webhook-Secret and its secret value. The eye icon reveals the secret; use the copy buttons. |
| Payload template | The JSON body for the automation's HTTP POST action. |
In Level, create an automation that fires on alert events and add an HTTP POST action using that URL, header, and payload. From then on, Level alerts reach AlgaPSA in real time and flow through your alert rules.
Backfill Alerts (on the Sync & Group Mappings card) fetches Level's current alerts on demand. Use it after setup to ingest existing alerts, or whenever you suspect the automation missed an event. Level has no scheduled polling card; the webhook is the live feed and backfill is the manual catch-up.
Operational checks
- The Level Connection card shows Connected with a recent timestamp.
- After mapping and device sync, spot-check one client's asset list against its Level group.
- Fire a test alert in Level and confirm a ticket appears through your alert rules; check the automation's delivery log in Level if it does not.
Related topics
- How RMM Integrations Work in AlgaPSA — the shared model behind every provider
- Turn RMM Alerts into Tickets — alert rules and maintenance windows
