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, within HaloPSA
Dive deeper into an asset from HaloPSA by opening up SuperOps with a single click
Comprehensive Asset Management and Synchronization
Automated Ticketing and Escalations
Configuring the integration
Before you start, you’ll need the following information from HaloPSA:
Client ID
Client secret key
Account URL
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.
Now that you’ve gotten all the necessary information and set up the new application, you can now jump into SuperOps to complete the configuration process.
Go to Settings > Marketplace. You’ll find the HaloPSA integration under the professional services section. Click 'Integrate' to start setting up the integration.
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. If they're not existing clients in SuperOps, 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 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.
Mapping asset class in SuperOps to HaloPSA asset types
Once you've mapped your sites and clients, you can now choose which asset class from SuperOps you'd like to map to asset types in HaloPSA.
Choose the asset class from the drop down list.
3. Below you can map each key field in the SuperOps asset class to their corresponding key fields in Halo’s asset type.
4. You can also create new custom fields and map them to the corresponding fields in HaloPSA.
Please note, users can map both standard and custom fields to any field, whether it's a default or a custom one. Custom field names will automatically be prefixed with "CF".
Creating SuperOps alerts as tickets in HaloPSA
You now have the option to create tickets in HaloPSA from the alerts generated in SuperOps. This is optional.
2. Once you have enabled the option you can also choose the type of ticket to be created in HaloPSA from the drop down list available.
Note:
You cannot create new asset types from within SuperOps. Create new asset types in Halo before mapping them in SuperOps.
If you are on the earlier version of this integration, please migrate to the new version.
With this, your HaloPSA account is now connected to SuperOps 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 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.
