AlgaPSA

AlgaPSA maps Level groups to clients and imports devices when you run device sync. Tickets are not a native webhook. You create one HTTP request automation, then attach it to the monitors that should open tickets.

Overview

Level groups map to AlgaPSA clients. Devices in mapped groups become assets when you run device sync. Tickets are not a Settings → Integrations or Settings → Webhooks connection. Create one automation with an HTTP request action that POSTs AlgaPSA’s webhook URL, header, and body, then attach that automation to the monitors that should open tickets.

How it works

  • Map once at the client level.

    Match Level groups to AlgaPSA clients and let unmapped subgroups inherit the nearest parent mapping.

  • Keep the asset list current.

    Devices in mapped groups become AlgaPSA assets when you run device sync. There is no scheduled poll.

  • Tickets take an HTTP request action.

    Create one automation that POSTs AlgaPSA’s webhook URL, header, and body. Attach it to the monitors that should open tickets. Settings → Webhooks cannot send the custom header.

Set up the integration

  • Create a read-only Level API key.

    AlgaPSA reads groups, devices, and alerts without writing back to Level.

  • Discover groups and map clients.

    Choose the AlgaPSA client for each managed group, then run device sync.

  • Build one HTTP request automation for tickets.

    POST to AlgaPSA from one automation, then attach it to ticket-opening monitors.

Explore other integrations.

Connect Level to the rest of your stack.

DeskDayPSA and TicketingRegentraPSA and ComplianceHaloPSAPSA and TicketingHuduDocumentationConnectWise PSAPSA and TicketingilertIncident ResponseZestMSPPSA and TicketingLevel Public APIDeveloper Platform

Questions about this connection.

What does the AlgaPSA integration sync?

Level groups map to AlgaPSA clients. Devices in mapped groups become assets when you run device sync. Tickets are not a Settings → Integrations or Settings → Webhooks connection. Create one automation with an HTTP request action that POSTs AlgaPSA’s webhook URL, header, and body, then attach that automation to the monitors that should open tickets.

Does Level replace AlgaPSA?

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

Where is the setup guide?

The setup steps live in the AlgaPSA integration guide.

Is there a free trial?

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

What edition of AlgaPSA do I need?

AlgaPSA Enterprise Edition. Create a read-only Level API key. AlgaPSA reads groups, devices, and alerts without writing back to Level. Built and maintained by Nine Minds.

How do Level alerts open AlgaPSA tickets?

They do not use Settings → Webhooks or a native integration toggle. Create one automation with an HTTP request action that POSTs to AlgaPSA’s webhook URL with AlgaPSA’s header and body. Then attach that automation on the monitors that should open tickets.

Why not Settings → Webhooks?

AlgaPSA’s developer, Nine Minds, chose a custom implementation that requires the X-Alga-Webhook-Secret header and an AlgaPSA-specific payload. Level does not recommend this design. It requires an HTTP request action instead of Settings → Webhooks, and Nine Minds did not build a Settings → Integrations connection.

Put AlgaPSA and Level in the same workflow.

Start free, follow the setup guide, and keep device work moving into the system your team already uses.

Start for freeBook a demo