HaloPSA Extension

Announcements
1

New Extension: HaloPSA

We’ve shipped a new extension, ext-halopsa, that connects LimaCharlie to HaloPSA - the PSA platform a lot of you MSPs already live in for ticketing, asset management, and time tracking.

The goal is simple: let your D&R rules and AI agents drive your HaloPSA tenant directly. No more bouncing detections through a separate orchestrator just to open a ticket, attach an asset, or log billable time.

What it does

Six outbound actions, callable from D&R rules, Playbooks, or AI agents:

  • create_ticket - open a ticket against the right client/site, with type/priority/assets.

  • update_ticket - change status, reassign, set priority, swap linked assets.

  • search_tickets - dedupe before you create, or pull existing work for an asset.

  • add_action - append a private note (default) or public reply, optionally with billable time.

  • link_asset_to_ticket - resolve a hostname to a HaloPSA asset (creating it if missing) and attach it. Bridges LC sensor telemetry straight into the MSP CMDB.

  • lookup_client_site - resolve client/site IDs by name. Useful plumbing for AI agents mapping an LC org to a Halo client.

Why it matters for MSPs

  • Detections become tickets, automatically. A D&R rule can open a HaloPSA ticket with the right client, site, type, and priority - billable from the second it’s created.

  • AI agents can do triage in your PSA. An agent can search for an existing ticket, append findings as a private note, log time, and link the affected asset - all under the right client.

  • Asset linkage is idempotent. Re-running link_asset_to_ticket won’t produce duplicates, so you can wire it into rules without worrying about cleanup.

Getting started

  1. Create a HaloPSA API Application (OAuth2 client_credentials, log on as the Application) with read/edit on tickets, customers, assets, actions.

  2. Subscribe to ext-halopsa from the LimaCharlie Marketplace.

  3. Store the client secret in Secrets Manager.

  4. Configure the extension with instance_url, client_id, and a hive:// reference to your secret.

Full setup and action reference: HaloPSA extension docs.

Feedback and feature requests welcome - drop them in this thread.