Setting Up the HaloPSA Integration with CloudRadial UCP

Connecting your HaloPSA instance (henceforth just referred to as "Halo") to your CloudRadial tenant allows you to submit tickets from CloudRadial to Halo as a part of your client portal experience.

Integrating the two will also allow you to sync users into CloudRadial from customers listed in Halo. 

• Creating and Configuring an API Key in Halo
• Tying the API Key to CloudRadial 
  • Setting up the Connection Information Section
  • Setting up the Ticket Settings Section
• Tying Halo to Specific Companies in CloudRadial 

Step 1: Creating and Configuring an API Key in Halo

To connect the data between the two systems, start by gathering the necessary data from Halo.

1. Log into your HaloPSA instance
2. Navigate to Configuration > Integrations > HaloPSA API

3. Take note of your Resource Server, Authorisation Server, and Tenant - and copy them down exactly as they are shown. These will be important in a later step.
   
   HaloPSA On-Premise Considerations

   When configuring a HaloPSA On-Premise integration, note the following differences from cloud-hosted instances:

   Tenant ID: On-premise instances do not have a Tenant ID. Use your HaloPSA Company Name in all lowercase instead.

   URL formatting: On-premise URLs often include a trailing slash. Remove this slash to ensure the integration functions properly.
   
   
    

4. Under the Applications menu, select the View Applications button
5. Select the New button at the top right
6. Complete the following configuration options to generate an appropriate API key 
   • For Application Name, enter your desired name. We recommend Client Portal
   • Ensure that the Active checkbox is ticked on
   • For the Authorization Method, select Client ID and Secret (Services)
   • Copy your Client ID and Client Secret keys. They will not be visible after this step. 
   • For Login Type, select Agent
   • For Agent to log in as, select a system admin within your HaloPSA instance with full permissions
     
     
7. Next, navigate to the Permissions tab at the top
8. Select both options for All and All:Teams 
9. Select the Save button to finalize your changes
   • There is no need to modify the Security tab of the API area. You may skip this part. 

At this point, you should have your Tenant, Client ID, and Client Secret copied down. Now, we'll plug those values into CloudRadial. 

Step 2: Tying the API Key to CloudRadial 

1. Log into your CloudRadial tenant
2. Navigate to Partner > Settings and select the PSA option at the top right, under the Setup column
   
   
    
3. Select Halo for the PSA

Setting up the Connection Information Section

1. Fill out the Connection Information section
   • Enter the Halo Tenant from your instance (Ex: cloudradial)
   • Enter the Halo URL of your instance.
     • You can get this by copying the URL when in your Halo instance.
   • Enter the Client ID that you gathered earlier
   • Enter the Client Secret that you gathered earlier
   • Now, you will see the text button to Test Credentials. Select the option and ensure that you get a green "OK" message stating your connection was successful.
     • If not, double-check the steps in the first part of these instructions and create a new API key
     • If the system is still not working, please reach out by submitting a ticket for assistance

Setting up the Ticket Settings Section

• For Statuses for "Client Closed / Ticket is Resolved":
  • List one or more statuses that indicate the ticket is closed and should be marked as such. Tickets matching this status (or statuses) will display under the Closed tab within the ticket view under Support > Support Tickets.
     
• For Statuses for "Ticket Waiting":  
  • Ensure that CloudRadial will flag the status(es) listed here as needing attention. Typically, this is used for approval workflows to let people know there is an action to be taken (such as approve, deny, escalate, etc).
     
  • These statuses must already exist in the PSA. This will do the following:
    • Allow the ticket with the waiting status to show up under the Waiting tab (under Support > Support Tickets) for better visibility
       
• For Status for "Client Comments":
  • Sets the status to whatever is filled in this field, should a client comment on a ticket from within the portal.
     
• For Exclude Ticket Statuses:
  • Select any statuses to be invisible within the portal and therefore NOT display in the ticket view area.
     
• For Priority for "User Priority":
  • Set the default priority level for users marked as "priority". More information on this can be found in this article. 
     
• For Add internal alerting note when file is attached to ticket?:
  • Check the box to allow internal alerting when files are added from the portal to Halo.
     
• For Other Settings: Send email advisories on failed ticket submissions?

  • As a best practice, we recommend having these go to an individual or distribution group. Sending advisories to a catch-all PSA email address, like a support email, can work - however, be advised that advisory emails will not be attributed to the submitting user and will need to be manually attributed.

    Please note: Advisory emails are not intended to fix errors in submission. They are there as stopgaps to ensure that a user's ticket makes it to the Partner while giving the Partner ample time to fix the routing issue(s) in CloudRadial.

    
                       

Step 3: Tying Halo to Specific Companies in CloudRadial

Once the connection has been secured, we will need to use PSA identifiers to ensure that users and ticket data are matched with the correct company in CloudRadial.

1. Navigate to Partner > Clients in CloudRadial
2. Select the 3 blue-dot menu on an existing client
3. Select Edit
   
                                   
   
    
4. Once in the Company panel, look for the PSA Company Identifier field under the Details tab
   • Note:  Steps 4-8 apply both when editing an existing client in CloudRadial or when adding a brand new one, via the +Add button at the top right of Partner > Clients. 
5. Use the Lookup button to find their company identifier in Halo
6. Press enter on the blank field to load all companies, or type the letters of the company you're trying to find, and then press enter
   
   
   
    
7. Select the corresponding company 
8. The ID will now be in place. Select Submit at the bottom of the company panel to finalize the PSA identifier assignment.

Ticket Dashboard Charts

Ticket dashboard charts - including volume trends, user submissions, and ticket type breakdowns - are now available for HaloPSA partners. The Charts button appears automatically on the support ticket grid. No additional configuration is required.

This brings HaloPSA to parity with ConnectWise, Autotask, Syncro, and Kaseya BMS for ticket analytics.

Ticket Workflow Actions

Approve, Mark Resolved, and Escalate workflow actions are fully supported for HaloPSA tickets. Status and priority updates are applied immediately in Halo when a workflow action is triggered from the portal.

Key details for HaloPSA:

• When a ticket is resolved through the portal, the closed-ticket flag (Hasbeenclosed) is set correctly in HaloPSA
• If a workflow action fails (ticket not found, invalid status, API failure), a clear error message is returned to the user
• Workflow actions use the same status workflow configuration as other PSAs - no Halo-specific setup is required beyond the standard integration

Service Team Filtering

HaloPSA Service Teams (the equivalent of ConnectWise Boards and Autotask Queues) are now integrated with CloudRadial. Partners can filter ticket boards by service team so that clients only see tickets relevant to their service area.

To configure service team filtering:

1. Navigate to Partner > Settings in CloudRadial
2. Under the PSA configuration section, configure the desired Halo Service Teams
3. Once set, ticket boards in the portal will be filterable by service team

Auto-Status on Client Comment

HaloPSA partners can optionally configure automatic ticket status updates when a client adds a comment. To enable this:

1. Navigate to your Halo partner settings in CloudRadial
2. Set the PsaUpdateStatus value to the desired status name
3. You can use a literal status name (e.g., "Client Responded") or a @Variable reference for dynamic resolution

When configured, any comment added by a client through the portal will automatically update the ticket status in HaloPSA.

The data from HaloPSA will now be flowing into the relevant (and currently supported) areas of CloudRadial. Simply repeat the ID entry steps for any loaded-up clients or for new clients added to the portal. If you are experiencing any issues with ticket submissions follow this link: Troubleshooting: Service Ticket Failures in HaloPSA – CloudRadial

If you are still having trouble, we're here to help! Submit a ticket here for assistance, and don't forget to check our status page to ensure there are no outages in your area.