Halo PSA Ticketing

Configuring the Halo PSA Ticketing integration

In your Halo instance head to Configuration > Integrations > Halo PSA API
Click on View Applications
Click on New to add a new API application.
Enter the Application Name. For example CIPP Integration
Make sure Active is checked.
Set the Authentication Method to Client ID and Secret (Services).
Store the Client ID and Client Secret securely.
Set the Login Type and Agent to login as appropriately. &#xNAN;This setting will determine who appears to be responsible for these API calls. You may want to create a dedicated agent user for this purpose. This agent needs to be an administrator in Halo, other roles maybe possible but have not been tested
Select the Permissions tab.
Grant the application the permissions required for your purposes. &#xNAN;Generally speaking you want to limit the API to only the permissions it needs. For CIPP this currently requires read:tickets, edit:tickets, read:customers, edit:customers.

In your CIPP instance head to CIPP > Integrations > HALOPSA
Enter your HaloPSA URL in the HaloPSA Resource Server URL field adding /api at the end, for example https://yourcompany.halopsa.com/api
Enter your HaloPSA URL in the HaloPSA Authorisation Endpoint URL field adding /auth at the end, for example https://yourcompany.halopsa.com/auth
If you are self-hosting Halo, you can leave the HaloPSA Tenant blank, otherwise enter the first part of your HaloPSA URL in the *HaloPSA Tenant field, for example yourcompany
Paste in the Client ID and Client Secret that you captured during the first part in to the respective fields
After entering the credentials, click the Test button, if you get a green success banner then all good, but if you get a red error banner, double check the settings in both HaloPSA and CIPP and correct where necessary
Make sure the Enable Integration button is enabled, and then click on the Submit button to save the config
Map the tenants in CIPP to the customers in Halo in the Tenant Mapping screen, either manually or using automap. Remember to click on the Submit button to save the mappings

To get the Ticket Type ID, follow these steps:

Navigate to Configuration -> Tickets -> Ticket Type
Click on the desired ticket type and then the URL will display the ticket type ID.

Example: https://{halo instance url}/config/tickets/tickettype?id=1

Last updated 2 months ago

Was this helpful?

Configuring the Halo PSA Ticketing integration

In your Halo instance head to Configuration > Integrations > Halo PSA API
Click on View Applications
Click on New to add a new API application.
Enter the Application Name. For example CIPP Integration
Make sure Active is checked.
Set the Authentication Method to Client ID and Secret (Services).
Store the Client ID and Client Secret securely.
Set the Login Type and Agent to login as appropriately. &#xNAN;This setting will determine who appears to be responsible for these API calls. You may want to create a dedicated agent user for this purpose. This agent needs to be an administrator in Halo, other roles maybe possible but have not been tested
Select the Permissions tab.
Grant the application the permissions required for your purposes. &#xNAN;Generally speaking you want to limit the API to only the permissions it needs. For CIPP this currently requires read:tickets, edit:tickets, read:customers, edit:customers.

In your CIPP instance head to CIPP > Integrations > HALOPSA
Enter your HaloPSA URL in the HaloPSA Resource Server URL field adding /api at the end, for example https://yourcompany.halopsa.com/api
Enter your HaloPSA URL in the HaloPSA Authorisation Endpoint URL field adding /auth at the end, for example https://yourcompany.halopsa.com/auth
If you are self-hosting Halo, you can leave the HaloPSA Tenant blank, otherwise enter the first part of your HaloPSA URL in the *HaloPSA Tenant field, for example yourcompany
Paste in the Client ID and Client Secret that you captured during the first part in to the respective fields
After entering the credentials, click the Test button, if you get a green success banner then all good, but if you get a red error banner, double check the settings in both HaloPSA and CIPP and correct where necessary
Make sure the Enable Integration button is enabled, and then click on the Submit button to save the config
Map the tenants in CIPP to the customers in Halo in the Tenant Mapping screen, either manually or using automap. Remember to click on the Submit button to save the mappings

To get the Ticket Type ID, follow these steps:

Navigate to Configuration -> Tickets -> Ticket Type
Click on the desired ticket type and then the URL will display the ticket type ID.

Example: https://{halo instance url}/config/tickets/tickettype?id=1

We value your feedback and ideas. Please raise any on GitHub.

Last updated 2 months ago

Was this helpful?