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 ActionCreate 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.
Auto-map matches each Lemhi client to its Halo client by Microsoft tenant ID, then name, then email domain. You choose the rest.
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.
An admin in your MSP's Lemhi account connects it and maps clients. Anyone with Compass edit access can push tasks.
Compass, where your team pushes and links tasks. You connect HaloPSA under Settings › Integrations.
A role, an API-only agent and an API application. API-only agents don't use a Halo license.
HaloPSA setup guide, with every role setting and permission you need.
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.
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.
3 application permissions: read:customers, edit:tickets and all:teams. The setup guide walks through the role settings for the API-only agent.
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.
See Lemhi's listing on HaloPSA's own site.
Walk through Lemhi with our team, including how it connects to HaloPSA.