All Collections
Integrations
How Tos
Integrating HaloPSA with SuperOps.ai
Integrating HaloPSA with SuperOps.ai

Learn how you can connect HaloPSA to SuperOps.ai’s RMM module and keep work flowing smoothly between both tools.

Manish Balaji avatar
Written by Manish Balaji
Updated over a week ago

What the integration does

Here’s what you can do with this integration:

  • Get a list of all your client’s assets monitored in SuperOps.ai, within HaloPSA

  • Dive deeper into an asset from HaloPSA by opening up SuperOps.ai with a single click

Configuring the integration

  1. Before you start, you’ll need the following information from HaloPSA:

    • Client ID

    • Client secret key

    • Account URL

  2. The account URL is what you usually use to log in to HaloPSA.
    This is how your account URL looks like: https://domain.halopsa.com/

    If you’re using a custom URL, you can find it in Configurations > Integrations > HaloPSA API > API details, under Resource Server or Authorization Server. (Make sure to copy the URL without ‘/api’ or ‘/auth’.)

3. Select View Application, and click New on the top right. Give the application a name, select the Active checkbox, and choose Client ID and Secret (Services) as the authentication methods. Copy the Client ID and Client Secret, and keep them handy.

4. Choose "Agent" as the login type and select the agent you want to be logged in as. Click Save to save the new application.

5. Within the new application, go to Permissions and choose All. This is to ensure that the app has the necessary permissions to perform all the actions that an agent can. Click save once you’re done.

Next, you’ll need to create asset types to map the different types of assets you monitor between HaloPSA and SuperOps.ai. Here’s how:

  1. Go to Settings > Asset management > Asset types

  2. Inside, you’ll see a list of asset types that have already been created. Click New to add a new asset type.

  3. Here, you’ll need to create 3 new asset types with the following information:

    Asset type name: Windows Workstation/Laptop with the following fields

    Fields that need to be added to the asset type:

    • Serial Number (Should be marked as a key field in every asset type)

    4. Once you’ve added the field, click edit on the right. Under Key Field, select “This field is the 1st Key Field for this Asset Type”. Fill in responses for the rest of the fields accordingly and click save.

    5. Next, add these remaining fields to the asset type:

    • Manufacturer

    • Model

    • IP Address

    • OS Version

    • Host Name

Click save once you’re done to save the asset type. Now, repeat the same process for the two remaining asset types below:

  1. Asset type name: Windows Server

Fields that need to be added to the asset type:

  • Serial Number (Should be marked as a key field in every asset type)

  • Manufacturer

  • Model

  • IP Address

  • OS Version

  • Host Name

2. Asset type name: Macbook

Fields that need to be added to the asset type:

  • Serial Number (Should be marked as a key field in every asset type)

  • Manufacturer

  • Model

  • IP Address

  • OS Version

  • Host Name

📝 Note:

The asset type names and the field names are case-sensitive and must be an exact match as given above.

Now that you’ve gotten all the necessary information and set up the new application, you can now jump into SuperOps.ai to complete the configuration process.

  1. Go to Settings > Marketplace. You’ll find the HaloPSA integration under the professional services section. Click 'Integrate' to start setting up the integration.

  2. Fill in the client ID, client secret key, and account URL from your HaloPSA account, and click Connect.

3. Once you’re done, you can start mapping clients between both tools. Choose which customers from HaloPSA you'd like to map to existing clients in SuperOps.ai. If they're not existing clients in SuperOps.ai, you can add them as new clients using the drop-down list. Click import once you’re done to start the client mapping and migration.

4. The next step is to map sites between both tools. The process is identical to how you mapped clients—each client’s sites are listed in order and you can either map sites in HaloPSA to existing sites in SuperOps.ai or you can create them as new sites under a client using the drop-down list. Click import once you’re done to start the site mapping and migration.

With this, your HaloPSA account is now connected to SuperOps.ai’s RMM module. You can now access a list of all your client’s assets by logging into HaloPSA and going to the Assets module to the left.

5. You can open up an asset to learn about it in detail. If you want to delve deeper into the asset, click Open in SuperOps to jump into your SuperOps.ai portal to see granular information about the device.

6. You’ll be taken directly to the asset’s summary page where you can get right to work.

7. You can also click Initiate remote session to immediately start a remote session to troubleshoot the asset.

Did this answer your question?