Integrating SuperOps with HaloPSA allows you to seamlessly sync your clients, sites, assets, and alerts between the two platforms.
What the integration does
Guided Mapping: Enforce mandatory client and site mapping before syncing assets to prevent duplicates.
Asset Synchronization: Map SuperOps asset classes to specific HaloPSA asset types based on platform categories.
Alert Management: Automatically create and resolve tickets in HaloPSA based on SuperOps alerts.
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.
From the main dashboard, navigate to the Integrations page by clicking the Integrations icon in the left-hand navigation menu.
2. Locate HaloPSA in the list of available integrations and click the Integrate button to begin the setup process.
3. In the Configuration section, enter your HaloPSA Account URL, Client ID, and Client Secret in the provided text fields.
4. After clicking Connect, SuperOps will validate your HaloPSA credentials and display a Permission Summary on the same Configuration page. This confirms that the connection was successful and shows the access levels granted to SuperOps within HaloPSA.
5. After connecting, you will be taken to the Map Clients tab where clients are by default imported from HaloPSA. You see the sync summary to see how many clients need to be mapped.
6. For each client in the list, you can choose to Create a new client in SuperOps, select an existing SuperOps client from the dropdown to map them, or check the Ignore box to skip mapping for that specific client.
7. Once you have configured all client mappings, click Save to apply your changes.
8. Proceed to the Map Sites tab to link your HaloPSA sites to SuperOps.
9. Similar to the client mapping process, use the dropdown menus to map the sites from HaloPSA to the corresponding sites in SuperOps.
10. Click Save to confirm your site mappings.
11. Navigate to the MAP Asset Class tab to configure how assets are categorized.
12. Select an asset class from the left menu (e.g., Windows Machine) and choose whether to map by Single asset type or Multiple asset type. If using multiple asset types, map the SuperOps platform category (like Server) to the corresponding HaloPSA Device Type using the dropdowns.
13. Click the Map fields button next to a mapped asset type to open the configuration modal. Here, define the key fields used for mapping (e.g., mapping Host name to Model) and map the default fields (e.g., Name to CFName).
14. You can also scroll down to map custom fields by clicking the Custom Fields button.
15. Select the appropriate custom fields from the dropdown menus to map them between the two systems. Click Continue to save the field mappings, and then click Save on the main asset class page.
16. Finally, navigate to the Choose ticket type tab to configure how alerts are handled.
17. SuperOps automatically pulls all available ticket types from your HaloPSA account and populates the dropdown. Any alert triggered in SuperOps will be created as a ticket in HaloPSA using the ticket type you select here.
Next, map the alert severities in SuperOps (Critical, High, Medium, Low) to the corresponding ticket priorities in HaloPSA. You can also enable the toggle to Auto resolve alerts on Superops when the linked ticket is closed in HaloPSA.
18. Click Save to finalize the integration setup. A success message will appear confirming that the fields have been mapped successfully.
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.
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.
2. You’ll be taken directly to the asset’s summary page where you can get right to work.
3. You can also click Initiate remote session to immediately start a remote session to troubleshoot the asset.
