This page lists problems with the Halo PSA integration, the message or symptom you see, and how to fix each one. Most answers start on the connection itself: go to Settings → Integrations → PSA provider and click Manage Connection.
"credential test failed"
Cause: Halo rejected the test request made with the details you entered on Test and save or Test connection.
Fix:
- Check Client ID and Client secret were copied correctly from the SuperIT API application in Halo.
- Check the application is set to Active, uses
Client ID and Secret (Services), and its Agent to log in as is the dedicated SuperIT agent, which must itself be active. - Check API URL is the Resource Server URL from Configuration → Integrations → HaloPSA API, starting
https://. - If Halo shows a Tenant ID, enter it in Tenant ID (optional). Otherwise leave it as
Halo. - If the secret was lost or may be exposed, generate a new one on the application in Halo, enter it in SuperIT and click Update connection.
Still stuck: note the full message after "credential test failed" and contact SuperIT support. Never send your client secret.
API permission errors
Symptoms:
- The connection shows Permissions degraded.
- Rows on the Permissions tab show Not working.
- Some data syncs but other data doesn't, for example clients arrive but assets don't.
Cause: The API application is missing a scope, or the SuperIT agent it logs in as is missing a permission.
Fix:
- Open Manage Connection → Permissions and note the scope each Not working row names.
- On the API application's Permissions tab in Halo, check these scopes are enabled, add any that are missing, and save:
all:teams,admin:webhooksread:tickets,edit:ticketsread:customers,read:assets
- On the SuperIT agent's Permissions tab, check the ticket, customer and asset access levels, and that Can add new tickets, Can view unassigned tickets and Can view tickets assigned to other agents are
Yes. For assignment, see Ticket assignment not applying. - Check the asset type and ticket type restrictions aren't excluding data SuperIT needs.
Still stuck: send support the Not working rows with their last status code and error.
Ticket assignment not applying
Symptoms:
- SuperIT reports assigning a ticket, but the ticket stays unassigned in Halo.
- Assignment works for some tickets and not others.
- After an engineer is assigned, SuperIT can no longer add notes or change the status of that ticket.
You do not have permission to update this Ticketin sync logs.
Halo returns success for an assignment it did not apply. Every other field in the same request lands, so the ticket does update, just without the agent. Nothing in Halo's response reports it.
Fix:
Check the three assignment permissions
On the SuperIT agent, open Permissions → Tickets Permissions and confirm all three are Yes:
- Can always update Ticket Statuses and re-assign Tickets outside of actions: without this, assignment never applies.
- Can assign to Agents in Teams the Agent is not a member of: without this, assignment works only for agents in the SuperIT agent's own teams.
- Can Edit Tickets Which Are Not Assigned To Them: without this, the ticket becomes read-only to SuperIT the moment an engineer is assigned.
Ticket access level: Read and modify and Can Re-assign Tickets: Yes are not sufficient on their own.
Check team membership
Open the agent's Departments & Teams tab. The agent must be a member of every team whose tickets SuperIT works on.
Team membership is enforced independently of the permissions above. An agent with all three set but no membership of a ticket's team still cannot assign or edit it.
Halo caches this in the agent's session. After changing it, use Revoke All Tokens on the agent so the integration picks it up.
Check the agent id exists
An agent id that does not exist in Halo is also silently ignored: Halo returns success and leaves the previous assignee in place, even when all permissions are correct.
SuperIT compares the assignee in Halo's update response with the agent it asked for, so a dropped assignment surfaces as an error rather than a false success. The same error appears whatever the cause: a missing permission, missing team membership, or an agent id that no longer exists. Check the permissions and team membership above first, then confirm the requested agent is still active in Halo.
Investigation notes and ticket updates arrive up to an hour late
Cause: The Halo webhook isn't reaching SuperIT, so changes arrive only through the hourly polling fallback. Common reasons are a webhook that was never created, was switched off in Halo, points at the wrong URL, or is signed with the wrong secret.
Fix:
- In SuperIT, open the connection's Webhooks tab and copy the Inbound Webhook URL and the Webhook Secret (click Reveal).
- In Halo, open Configuration → Integrations → Webhooks and check the SuperIT webhook is enabled, its Payload URL matches exactly, and its secret matches.
- Check the four events are selected:
New Ticket Logged,Ticket Updated,Ticket Updated by Agent,Ticket Updated by User. - Check Ticket polling fallback is on (Configure & Test tab) so changes still arrive hourly while you fix it.
See Halo webhooks.
Still stuck: check Halo's delivery log for the webhook and send support the response SuperIT returned.
Halo's webhook log shows "Missing X-Halo-Signature header" or "Invalid signature"
Cause: SuperIT rejected the request because it wasn't signed, or was signed with a different secret from the one SuperIT holds for the connection.
Fix:
- On the connection's Webhooks tab, click Reveal under Webhook Secret and copy it.
- In the Halo webhook, set authentication to sign the request body with a secret key, paste the secret, and set the signature header to
X-Halo-Signature. - Save the webhook and update a test ticket.
"No webhook secret configured for this connection"
Cause: You clicked Reveal on the Webhooks tab for an older connection that has no stored webhook secret.
Fix: contact SuperIT support to add a secret to the connection, then set it in Halo.
Tickets aren't being triaged or investigated
Cause: The ticket's status has no category. SuperIT starts triage and investigation only for tickets in a status categorised NEW or OPEN.
Fix:
- On the team that has the PSA connected, usually your service provider team, go to Settings → Ticket automation → Custom triage instructions and open the Status tab.
- Set Category on every status you use, or click the Manage with button (it shows your AI agent's name) to do them in bulk.
- Check the ticket's category and type are included in the Ticket Filters on the connection's Filters tab.
Still stuck: send support the ticket number, its status, category and type.
The SuperIT tab on Halo tickets is blank
Cause: Halo isn't allowed to show the SuperIT panel because the connection has no Halo URL recorded.
Fix: if the Pod tab says "No Halo URL is recorded for this connection", open Configure & Test and save the connection again. See Add the SuperIT Pod to Halo PSA.
Before you contact support
Collect:
- The connection name and the exact message you see.
- What the Permissions tab shows for any Not working row.
- Last poll and any Poll error from the connection card.
- An example Halo ticket number and what you expected to happen.
Never send your client secret or webhook secret.