What can you do with the HaloPSA integration?

LiveContext exposes 17 operations on HaloPSA, covering ticket, client, site and user. Common uses include removing a ticket raised in error, reporting on the open ticket queue and showing a ticket's conversation history.

LiveContext

All integrations

HaloPSA integration

HaloPSA REST API for service desk and professional services automation, against a self-hosted or vendor-hosted instance: read and raise tickets, log actions against them, and manage the clients, sites, users and assets they refer to. The instance host and an access token obtained from HaloPSA's own client-credentials token endpoint are both supplied by the connected credential.

17 toolsTokenAPI docs

Connect HaloPSA How integrations work

Common HaloPSA use cases

removing a ticket raised in error
reporting on the open ticket queue
showing a ticket's conversation history
showing device details next to a ticket
onboarding a customer contact from a CRM
raising a ticket from a monitoring alert
finding the asset behind a reported fault
resolving a client id from a company name
showing the site contact next to a ticket
resolving a site id before raising a ticket

What you can do with HaloPSA

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Ticket, 4 operations

POSTcreate_ticket
Creates a HaloPSA ticket, or updates an existing one by including its id.
DELETEdelete_ticket
Deletes a HaloPSA ticket permanently.
GETget_ticket
Retrieves a single HaloPSA ticket by identifier.
GETlist_tickets
Lists HaloPSA tickets with filtering and paging.

Client, 3 operations

POSTcreate_client
Creates a HaloPSA client, or updates an existing one by including its id.
GETget_client
Retrieves a single HaloPSA client by identifier.
GETlist_clients
Lists HaloPSA clients with paging and search.

Site, 3 operations

POSTcreate_site
Creates a HaloPSA site under a client, or updates an existing one by id.
GETget_site
Retrieves a single HaloPSA site by identifier.
GETlist_sites
Lists HaloPSA sites with paging and search.

User, 3 operations

POSTcreate_user
Creates a HaloPSA end user at a site, or updates an existing one by id.
GETget_user
Retrieves a single HaloPSA end user by identifier.
GETlist_users
Lists HaloPSA end users with paging and search.

Action, 2 operations

POSTcreate_action
Adds a note, update or time entry to a HaloPSA ticket.
GETlist_actions
Lists the actions, notes and emails logged on a HaloPSA ticket.

Asset, 2 operations

GETget_asset
Retrieves a single HaloPSA asset by identifier.
GETlist_assets
Lists HaloPSA assets with paging and search.

Use HaloPSA from Claude Code, Cursor or Codex

Connect HaloPSA in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its HaloPSA operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect HaloPSA

Create your workspace
Sign up free. Nothing to install.
Connect HaloPSA once
Add your HaloPSA connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

HaloPSA integration FAQ

What can you do with the HaloPSA integration?: LiveContext exposes 17 operations on HaloPSA, covering ticket, client, site and user. Common uses include removing a ticket raised in error, reporting on the open ticket queue and showing a ticket's conversation history.