HaloPSA

Connect HaloPSA to Uniportal so AI workflows can run directly from your service desk.

This guide walks through connecting HaloPSA to Uniportal, so technicians can run AI workflows directly from tickets instead of switching tools mid-ticket.

Prerequisites

Admin role access to your HaloPSA tenant. Both steps below live under Configuration, which HaloPSA restricts to admins.
Admin/Owner role in your Uniportal tenant.

Setup

Create an API-only agent in HaloPSA

Navigate to Configuration > Agents in HaloPSA.
Create a new agent with the username Uniportal AI.
Assign the Administrator role.
Enable the Is an API-only Agent checkbox. This keeps the credential from ever being used to log into HaloPSA interactively, so if it's exposed, it can only make the specific API calls Uniportal needs, not act as a technician.
Complete any remaining required fields and save.

Create an API application in HaloPSA

Go to Configuration > HaloPSA API.
Record the Resource Server URL (without the /api suffix).
Note the Tenant value.
Create a new application named Uniportal.
Select Client ID and Secret (Services) as the authentication method.
Record the Client ID and Client Secret values.
Set Login Type to Agent and select the integration agent created in the previous step.
Grant the All and All:Teams permissions, so the integration can act across every team's queue, not just one.

Configure the integration in Uniportal

In the Uniportal dashboard, go to Integrations.
Select the HaloPSA tile.
Enter the Account URL, Tenant, Client ID, and Secret from the previous steps.
Click Connect.

Once connected, set how email and phone fields map when syncing end-user details.

From the HaloPSA integration tile, map HaloPSA companies and contacts to the matching company in Uniportal. Select Auto match to let Uniportal suggest matches for you to review and approve, or match them manually yourself.

Mapping is what lets the AI find the right information fast. When a ticket comes in for a specific customer, the AI already knows which HaloPSA company and contacts it's dealing with, instead of searching for them. Uniportal works without mapping, but we recommend doing it: it's what most Skills and Agent Tools rely on to know whose ticket they're looking at.

Add the Uniportal tab to tickets

In HaloPSA, go to Configuration > Tickets > Ticket Types and add the Uniportal tab to the ticket types you want it to appear on.

Once added, technicians can run workflows directly from a ticket, with every action logged as an internal note, so there's an audit trail of what the AI did sitting right in the ticket, not in a separate system you have to go check.