Integration
Lemhi HaloPSA

Run your AI practice through your HaloPSA service desk

Connect Lemhi to HaloPSA, map your clients and push AI engagement tasks straight into Halo tickets. Your technicians work them from the queue they already use, and every task shows its ticket number and status.

See Lemhi in Action
How it works

From connection to tickets in 3 steps

  1. Connect HaloPSA

    Create an API-only agent and an API application in HaloPSA, then enter your Halo web address, client ID and secret in Lemhi. Setup takes about 15 minutes.

  2. Map your clients

    Auto-map matches each Lemhi client to its Halo client by Microsoft tenant ID, then name, then email domain. You choose the rest.

  3. Push tasks into tickets

    Push one task, or up to 50 at once, from Compass into HaloPSA tickets with your default ticket type and team. Each task shows its ticket number and status.

What you can do with it

Your AI engagements, worked from the Halo queue

What flows between Lemhi and HaloPSA

  • Lemhi to HaloPSA: each Compass task becomes a ticket with its title, description and guided steps, on the mapped client.
  • Tickets use your default ticket type and team, and you can change the team on each push.
  • Push one ticket per task, or roll a selection of tasks into a single ticket.
  • Link a task to a ticket that already exists in HaloPSA.
  • HaloPSA to Lemhi: each task shows its ticket's current status, with a link to open the ticket in Halo.

What your team does differently

  • Your technicians work AI engagement tasks from the HaloPSA queue they already use.
  • Your vCIO pushes the work from Compass instead of re-keying it into Halo.
  • Your team filters Compass tasks by whether they're in HaloPSA yet, so nothing slips through.
  • Lemhi never creates or edits clients, sites, users or agents in Halo, and never changes a ticket after creating it.
Setup and requirements

What you need to connect HaloPSA

FAQ

Questions about the HaloPSA integration

What does Lemhi send to HaloPSA?

Compass tasks, as tickets. Each ticket carries the task title as its summary, and the task description and guided steps as its details, on the mapped client with your default ticket type and team. Lemhi never creates or edits clients, sites, users or agents, and never changes a ticket after creating it.

How does Lemhi match our clients to HaloPSA?

Auto-map matches each client by Microsoft tenant ID, then exact name, then email domain against the Halo client's website. It never overwrites a mapping you've set. Anything it can't match waits in the Unmapped tab for you to choose.

What permissions does the API application need?

3 application permissions: read:customers, edit:tickets and all:teams. The setup guide walks through the role settings for the API-only agent.

Do we need HaloPSA to use Lemhi?

No. You can also export tenant findings as a CSV to open remediation tickets in any PSA, and attach Lemhi reports to the client record.

Lemhi on HaloPSA

See Lemhi's listing on HaloPSA's own site.

View Lemhi on HaloPSA
Next step

See how Lemhi fits the way your MSP already works

Walk through Lemhi with our team, including how it connects to HaloPSA.