HaloPSA

HaloPSA reports runs through its outbound integration machinery: a Custom Integration method that POSTs to LumaTrack, callable from runbooks and automation steps.

The method

Under Configuration, Integrations, Custom Integrations:

1. Create a custom integration named LumaTrack, base URL https://your-lumatrack-host.
2. Add a Method: type POST, endpoint /api/v1/runs, header Authorization: Bearer <API key> (use Halo's credential storage, never a hard-coded value in the body template).
3. Body template:

{
  "automation": "ticket-triage",
  "status": "success",
  "source": "halopsa",
  "external_id": "$-TICKETID",
  "metadata": {"ticket": "$-TICKETID"}
}

Halo's $- variables substitute ticket fields into the payload; external_id from the ticket or runbook execution id makes retries idempotent.

1. Call the method as a step in the runbook or automation that does the work, and add a failure-path call with "status": "failure" where the runbook handles errors.

What this buys a MSP

Halo automations that close or triage tickets are exactly the invisible work clients never see. Each reported run books the tech minutes one manual handling takes (your labeled assumption) at the role's loaded rate, per client workspace, into a report a client can audit; see the MSP guide for the per-client setup.

Field reference: Recording runs. Batch-shaped automations (N tickets swept per run) can report units and be valued per unit.