HaloPSA

HaloPSA Guides

Documentation to assist with the setup and configuration of the HaloPSA platform

Guides > Addigy Integration

Addigy Integration

In this guide we will cover:

- Obtaining Addigy API Credentials 

- Connecting Halo to Addigy

- Asset Imports

- Alerting

- Halo Integrator

- Miscellaneous



Obtaining Addigy API Credentials

Log in to your Addigy account and navigate to the Addigy API section in Account > Integrations. Here you can create a new API client or use an existing one. Be sure to take note of the Client ID and Client Secret provided by Addigy.


Connecting Halo to Addigy

After logging into your Halo account as an administrator, go to Configuration > Integrations > Asset Management and Alerting, where you will find the Addigy module. Hover over this and click the plus "+" icon to enable the module. This will then change to a cross "x" when enabled.


Fig 1. Enabling the Addigy module


Click into the module, which will provide the following screen. Enter the Client ID and Client Secret obtained from Addigy into the respective fields at the top.


Fig 2. Addigy configuration screen


You can then click the "Test Credentials" button to verify the connectivity with Addigy. This ensures that the API credentials are correct and the integration is functioning properly. If the details are correct, you will see this popup showing that the validation was successful. If it errors, you will be provided the error details, such as a "Validation Failed - 401 Unauthorized" if the credentials are incorrect.


Fig 3. Validation Successful test popup


Asset Imports

The first part of the "Asset Imports" section is the mapping table. Here you can map each Halo customer to an Addigy Policy.


Fig 4. Asset customer mappings


Clicking the "Add" button will bring up the following popup, where you select the mappings within their respective dropdowns.


Fig 5. Mappings popup


Any customers not mapped here will use the default customer configured below this in the "Default Asset Site". Here you can also configure the rest of your asset defaults and matching values. For instance, the "Addigy Asset Type Field" maps the default Asset Type field in Halo, which will be populated based on the corresponding Addigy field (e.g., Hardware Model). 


Fig 6. Asset Imports configuration


The last part is to define mappings between Addigy asset fields and corresponding fields in Halo. Add mappings for each relevant field, such as serial number, user, location, or other custom fields. These mappings ensure that the data from Addigy is accurately transferred to the corresponding fields in Halo.


Fig 7. Asset Field Mappings table


Once this is mapped, you can click the "Import Assets" button to bring up the import screen and bring in your Addigy assets manually.


Alerting

The next section is an optional method to set up alerts. Upon checking "Enable alert processing", the following fields will show underneath. If you are still using NHServer to process mail, ensure NHServer versions are correct. This will only apply to some on-premise customers as from v2.184 hosted customers will not be using NHServer. Then set the default ticket type and user the alerts will create with. 


Fig 8. Alerting configuration


From v2.184+ when an asset is removed from Addigy the Addigy ID will be removed from the asset in Halo. This will result in the asset in Halo no longer being linked to RMM alerting in Addigy.  


Halo Integrator

If you prefer to import assets on a recurring schedule, the Halo Integrator can be enabled for the module. 


Fig 9. Halo Integrator configuration


Miscellaneous

In the final section, you can configure additional settings, such as deactivating assets in Halo when they are deleted from Addigy. This requires the Halo Integrator.


Fig 10. Miscellaneous Addigy settings.

Popular Guides