How the integration works
Telivy talks to the HaloPSA REST API with an API application you create in your Halo instance. The application signs in with a client ID and secret (the OAuth 2.0 client credentials flow), so no Halo user password is shared with Telivy. Telivy stores the secret encrypted and never shows it again after you save it.Tickets
Once HaloPSA is connected and a company is mapped, each finding in a category you chose to sync opens one ticket. You can group a category into one ticket per scan instead. When a scan raises a finding in a category you chose to sync, Telivy creates a Halo ticket against the Halo client you mapped to that company. The ticket title starts with[Telivy] and the severity, and the ticket body explains the finding, the risk, the recommended fix and the Telivy references, with a View in Telivy link that opens the finding directly on the assessment’s Risk tab. The Halo priority follows the finding severity: Critical findings get priority 1, High get 2, Medium get 3, Low and Info get 4.
If the finding is still present on the next scan, Telivy updates the title of the existing ticket instead of opening a second one.
Resolutions read back from Halo
Every hour Telivy checks the tickets it opened. A ticket that Halo shows as closed (Halo records a close date when a ticket reaches a closing status such as Closed) marks the finding as Resolved in PSA in Telivy, with the ticket number and status in the reason. If the issue is still there, the next scan raises the finding again. You can also run this check on demand with Check HaloPSA for updates on the assessment’s PSA card.Decisions made in Telivy
When you resolve or accept a finding in Telivy, Telivy moves its Halo ticket to the status you choose in the ticket settings.
Permissions Telivy needs
The API application needs exactly three permissions. Telivy does not ask forall, administrator permissions or webhooks.
One PSA at a time
An agency connects one PSA. While ConnectWise or Autotask is enabled, the HaloPSA switch is disabled and Telivy shows Disable ConnectWise to connect HaloPSA (or Autotask). Disabling a PSA keeps its credentials and company mappings, so you can switch back later. When you switch, your sync settings under Alerts → Policies carry over to the newly connected PSA. Company mappings do not carry over, because each PSA has its own company records, so map your companies again after switching.
Prerequisites
- A HaloPSA instance and a Halo account with access to Configuration → Integrations.
- A Halo agent account the integration can act as.
- A Telivy account with access to Account → Integrations.
Step 1: Create the API application in HaloPSA
Open the Halo API settings
https://yourcompany.halopsa.com.
Choose Client ID and Secret

Copy the client ID and secret, and pick the agent

Grant the three permissions

Step 2: Connect HaloPSA in Telivy
Pick HaloPSA as your platform

Enter the connection details
- HaloPSA URL: the address you sign in to Halo with, such as
https://yourcompany.halopsa.com. It must start withhttps://. - Client ID and Client Secret: the values you copied in Step 1.

Choose the ticket settings
- Ticket Type: the type Telivy opens tickets as, for example Incident. Leave it blank to use Halo’s default.
- New Ticket Status: the status a new ticket starts in. Leave it blank to use Halo’s default.
- Resolved Status: the status Telivy sets when you resolve a finding in Telivy. Choose Closed so Halo records the ticket as closed. Leave it blank if Telivy should not change ticket status.
- Accepted Risk Status: the status Telivy sets when you accept a finding’s risk. If you leave it blank, Telivy uses the Resolved Status.

Step 3: Choose which findings open tickets
Go to Alerts → Policies and turn on PSA sync for the finding categories that should open tickets, with an optional severity floor such as High and above. These settings apply to whichever PSA is connected. See Alerts for the policy controls. To receive one ticket per scan instead of one per finding, see Grouped PSA tickets. Under Account → Integrations → Ticket settings, the Close tickets when a finding is accepted or resolved switch controls whether resolving or accepting a finding in Telivy updates its ticket.Step 4: Map each company to a Halo client
Telivy needs to know which Halo client a company’s tickets belong to. Map each company once. A Halo client can belong to one Telivy company at a time. Mapping a client that is already mapped moves it to the new company, and the previous company shows Not mapped again.Open the mapping dialog
Search for the Halo client

Turn on PSA sync for the assessment
Work with tickets from Telivy
Finding tables on the Risk tab have a PSA column. Each dot shows whether the finding is synced, synced but not yet resolved or accepted in Telivy, failed, or not synced. Click a dot to open the existing ticket, or to create one for a finding that has none. To open tickets for many findings at once, select them and click Sync to PSA. Find unsynced in HaloPSA lists the assessment’s findings that should have a ticket but do not, and queues them. The PSA card on the assessment’s Configuration tab has Check HaloPSA for updates, which runs the hourly read-back straight away for that assessment. The same card has Unmap, which stops new tickets for that company. Tickets already in Halo stay as they are, and findings that were synced before do not sync again if you map the company somewhere else. Deleting a company in Telivy releases its Halo mapping, so the Halo client can be mapped to another company.Check that it works
- Account → Integrations shows HaloPSA as Connected.
- The company shows the Halo client name in the PSA column on Companies.
- New tickets appear in Halo for the mapped client, with titles starting with
[Telivy]. - When a technician closes one of those tickets in Halo, the finding shows Resolved in PSA in Telivy within the hour, or straight away after Check HaloPSA for updates.
Troubleshooting
Test Connection fails
Test Connection fails
https://, that the client ID and secret were copied without extra spaces, and that the application is Active in Halo. If someone clicked Generate in Halo after you copied the secret, the old secret no longer works. Copy the new one and reconnect.Telivy says the API application is missing a permission
Telivy says the API application is missing a permission
The HaloPSA switch is greyed out
The HaloPSA switch is greyed out
Findings are not creating tickets
Findings are not creating tickets
Closed tickets are not resolving findings in Telivy
Closed tickets are not resolving findings in Telivy