Skip to main content

HaloPSA integration setup guide

Covers the HaloPSA configuration you need to complete before setting up the integration in Support Fusion.

This guide covers the HaloPSA configuration you need to complete before setting up the integration in Support Fusion.

Prerequisites

  • Administrator access to your HaloPSA instance.

  • Familiarity with HaloPSA agent and role configuration.

  • Familiarity with HaloPSA OAuth2 API applications.

Step 1: Create an API agent and role

Set up an agent that Support Fusion authenticates as, so all integration activity is attributable to one account you can audit and manage.

  1. Navigate to Configuration > Teams and Agents > Agents and select +New (or reuse an existing agent).

  2. Set Name to Support Fusion Integration, add a monitored Email, assign a role, and tick Is an API-only Agent. Save.

For the role, either assign one that matches your other agents, or create a dedicated role under Configuration > Teams and Agents > Roles with these minimum access levels: Read and Modify on Tickets, Customers, Users, and Assets, and Read Only on CRM. If you need to limit which customers sync, restrict customer access in the role, though most setups use full customer access.

Note: An API-only agent can't sign in interactively and doesn't consume a user licence, which makes it well suited to an integration.

Step 2: Create an OAuth2 application

HaloPSA authenticates the integration through an OAuth2 application tied to the agent, which is where you get the client ID and secret.

  1. Navigate to Configuration > Integrations and select HaloPSA API. Note the Resource Server URL shown here, in the form https://[tenant].halopsa.com/api: this is your API URL.

  2. Select View Applications, then +New.

  3. On the Details tab, set Application Name to Support Fusion Integration, Authentication Method to Client ID and Secret (Services), Login Type to Agent, and select the agent from step 1.

  4. Copy the Client ID and Client Secret and store them securely.

  5. On the Permissions tab, set the scope to all:standard. This grants access to everything the agent's role allows, with admin privileges excluded.

  6. Save the application.

Important: The client secret may be shown only once. Copy it before leaving the page; if you lose it you'll need to regenerate it.

Next steps

With HaloPSA configured, set up the integration in Support Fusion from Settings: choose HaloPSA, then enter the API URL, client ID, client secret, and the scope all:standard. Support Fusion appends /api to the URL if you leave it off. Save the configuration and test the connection. For the per-relationship settings, see HaloPSA integration.

Troubleshooting

Authentication failed. Check that the client ID and secret were copied in full, that the API URL is correct (with or without /api), and that the scope is all:standard.

Permission denied. Confirm the agent's role has the access levels in step 1, that the agent is selected on the application's Details tab, and that the agent can reach the customers you're syncing.

Invalid API URL. Use the Resource Server URL from Configuration > Integrations > HaloPSA API, with no extra spaces or characters.

Agent access issues. Verify Read and Modify access to Tickets, Customers, Users, and Assets, and check any customer access limits if sync fails for specific organisations.

Did this answer your question?