<style>p { margin: 0; }span.fr-emoticon.fr-emoticon-img { background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle; } span.fr-emoticon { font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0; } blockquote { border-left: solid 2px #5e35b1; color: #5e35b1; margin-left:0; padding-left:5px;}blockquote blockquote{ border-color: #00bcd4; color: #00bcd4;}blockquote blockquote blockquote{ border-color: #43a047; color: #43a047;} table.grid{ border-collapse: collapse;} table.grid td, table.grid th { border: 1px solid #ddd;} .fr-fic.fr-dib{ display: block; margin: 5px auto;}.fr-fic.fr-dib.fr-fir{ text-align: right; margin: 5px 0 5px auto;}.fr-fic.fr-dib.fr-fil{ text-align: left; margin: 5px auto 5px 0;}.fr-fic.fr-dii{ float: none; margin: 5px auto;}.fr-fic.fr-dii.fr-fil{ float: left; margin: 5px auto;}.fr-fic.fr-dii.fr-fir{ float: right; margin: 5px auto;}img.fr-dib.fr-fir { margin-right: 0; text-align: right;}img.fr-dib.fr-fil { margin-left: 0; text-align: left;}img.fr-dib { margin: 5px auto; display: block; float: none;}img.fr-bordered { box-sizing: content-box; border: solid 5px #CCC;}img.fr-shadow { box-shadow: 10px 10px 5px 0px #cccccc;}img.fr-rounded { border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;}</style><style>
p {
margin: 0;
}
span.fr-emoticon.fr-emoticon-img {
background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle;
}
span.fr-emoticon {
font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0;
}
blockquote {
border-left: solid 2px #5e35b1; color: #5e35b1; margin-left: 0; padding-left: 5px;
}
blockquote blockquote {
border-color: #00bcd4; color: #00bcd4;
}
blockquote blockquote blockquote {
border-color: #43a047; color: #43a047;
}
table.grid {
border-collapse: collapse;
}
table.grid td,
table.grid th {
border: 1px solid #ddd;
}
.fr-fic.fr-dib {
display: block; margin: 5px auto;
}
.fr-fic.fr-dib.fr-fir {
text-align: right; margin: 5px 0 5px auto;
}
.fr-fic.fr-dib.fr-fil {
text-align: left; margin: 5px auto 5px 0;
}
.fr-fic.fr-dii {
float: none; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fil {
float: left; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fir {
float: right; margin: 5px auto;
}
img.fr-dib.fr-fir {
margin-right: 0; text-align: right;
}
img.fr-dib.fr-fil {
margin-left: 0; text-align: left;
}
img.fr-dib {
margin: 5px auto; display: block; float: none;
}
img.fr-bordered {
box-sizing: content-box; border: solid 5px #CCC;
}
img.fr-shadow {
box-shadow: 10px 10px 5px 0px #cccccc;
}
img.fr-rounded {
border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;
}
</style><style>
p {
margin: 0;
}
span.fr-emoticon.fr-emoticon-img {
background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle;
}
span.fr-emoticon {
font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0;
}
blockquote {
border-left: solid 2px #5e35b1; color: #5e35b1; margin-left: 0; padding-left: 5px;
}
blockquote blockquote {
border-color: #00bcd4; color: #00bcd4;
}
blockquote blockquote blockquote {
border-color: #43a047; color: #43a047;
}
table.grid {
border-collapse: collapse;
}
table.grid td,
table.grid th {
border: 1px solid #ddd;
}
.fr-fic.fr-dib {
display: block; margin: 5px auto;
}
.fr-fic.fr-dib.fr-fir {
text-align: right; margin: 5px 0 5px auto;
}
.fr-fic.fr-dib.fr-fil {
text-align: left; margin: 5px auto 5px 0;
}
.fr-fic.fr-dii {
float: none; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fil {
float: left; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fir {
float: right; margin: 5px auto;
}
img.fr-dib.fr-fir {
margin-right: 0; text-align: right;
}
img.fr-dib.fr-fil {
margin-left: 0; text-align: left;
}
img.fr-dib {
margin: 5px auto; display: block; float: none;
}
img.fr-bordered {
box-sizing: content-box; border: solid 5px #CCC;
}
img.fr-shadow {
box-shadow: 10px 10px 5px 0px #cccccc;
}
img.fr-rounded {
border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;
}
</style><p id="isPasted"><strong>In this guide we will cover:</strong></p><p id="isPasted"><strong>- What is the Addigy Integration?</strong></p><p><strong>- Connecting Halo to Addigy</strong></p><p><strong>- Import Assets Automatically on a schedule</strong></p><p><strong>- Alerting</strong></p><p><br></p><p data-pasted="true"><span style="color: rgb(235, 107, 86); font-size: 11pt;"><strong>Important: From the 30th June you must use the Addigy V2 API for this Integration. If you are not currently on this version, please switch over to the Addigy V2 API in order to use the integration.</strong></span></p><p><br></p><p><strong><span style="font-size: 14pt;">What is the Addigy Integration?</span></strong></p><p id="isPasted">Addigy can be integrated with Halo to sync assets and generate alert tickets. Assets can be imported on a recurring schedule using the Halo integrator, keeping your assets and their details completely up to date. Alerts can be processed using both the Halo integrator and webhooks. Webhooks are only supported when using v2 of the integration (which is recommended). </p><p><br></p><p><strong><span style="font-size: 14pt;">Connecting Halo to Addigy</span></strong></p><p>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.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImM2MDgyYTM3LTg2MmMtNDFhNC05N2M4LTRiMTc3ZWEyMGEwMCJ9.8GPhhe063GO6qek5NIg-SYwQiUxdOzRbycyFwTyNyZs" width="88" height="111" class="fr-fic fr-dii"></p><p><strong><span style="font-size: 10pt;">Fig 1. Enabling the Addigy module</span></strong></p><p><br></p><p>Click into the module and create a new connection to begin configuration. The integration supports multiple instances of Addigy being connected to a single Halo instance. </p><p><br></p><p>When creating a new connection, you will need to give the connection a name and choose which API version you would like the integration to use.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImMyZDJjNTZlLWI2NTgtNGNlMi1iMGE2LTc0ODNjNzMxYjM2OCJ9.VMGh4z14dUvMlOSko7GtiU3he_I81JmtajcoLmD1iLU" class="fr-fic fr-fil fr-dib" width="1012" style="width: 1014px; height: 730.5px;" height="730"></p><p><strong><span style="font-size: 10pt;">Fig 2. New Addigy Connection. </span></strong></p><p><br></p><p><strong>API Version -</strong> Choose between v1 and v2. </p><ul><li><strong>v1 </strong>-Connections setup before v2.204 will use v1. When used alerts will be able to be processed using the Halo integrator only. Your Client Secret will be encrypted when saved within Halo, however when a request is made to the Addigy API the secret will be decrypted and sent as plain text. This is a limitation of Addigy's v1 API and is less secure than v2.</li><li><strong>v2 </strong>- We recommend setting up new connections with this version. This version supports the processing of alerts using both the Halo integrator and webhooks. Webhooks allow for much faster processing. Your API Key will be encrypted when saved within Halo and added as an authentication header when making requests. This is more secure than API v1.</li></ul><p>The connection details required will also depend on the API version you have selected. But both API versions will require you to enter your organisation ID too. </p><p><br></p><p>If using v1 you will need a client ID and secret. If using v2 you will need an API key. </p><p><br></p><p><strong><span style="font-size: 12pt;">Obtaining Addigy API Credentials</span></strong></p><p><strong><span style="font-size: 11pt;">Client ID and secret</span></strong><span style="font-size: 11pt;"><br></span></p><p>Log in to your Addigy account and navigate to the <a href="https://support.addigy.com/hc/en-us/articles/16938210315411-API-Documentation-v2" target="_blank" rel="noopener noreferrer"><strong>Addigy API</strong></a> 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. For more information on how to obtain a client ID and secret in Addigy checkout <a data-fr-linked="true" href="https://support.addigy.com/hc/en-us/articles/4403542544275-Generating-Addigy-API-V1-Key-and-Secret" id="isPasted" target="_blank" rel="noopener noreferrer">Addigy's v1 documentation here.</a></p><p><br></p><p><strong>API Key</strong></p><p>For information on how to obtain an API key in Addigy checkout <a data-fr-linked="true" href="https://support.addigy.com/hc/en-us/articles/16938210315411-API-Documentation-v2" id="isPasted" target="_blank" rel="noopener noreferrer">Addidy's v2 API documentation here.</a></p><p><br></p><p><strong><span style="font-size: 12pt;">Connecting</span></strong></p><p>Once you have obtained the required credentials head back to the integration setup page in Halo and enter the connection details in the respective fields. </p><p><br></p><p>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.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjM4Nzk1MjAxLTUxODQtNDBiMC1hNmE5LTlkOGVmYjYyMzE0NCJ9.nEiClpsByrWcw0R2tL-8yEzXYap2eUPlYigNBQxLgUs" width="216" height="124" class="fr-fic fr-dii"></p><p><strong><span style="font-size: 10pt;">Fig 3. Validation Successful test popup</span></strong></p><p><br></p><p><strong><span style="font-size: 14pt;">Asset Imports</span></strong></p><p><strong><span style="font-size: 12pt;">Site Mappings</span></strong><span style="font-size: 12pt;"><br></span></p><p>Once connected head to the 'Assets' tab to configure how assets will be imported from Addigy.</p><p><br></p><p>The first part of the "Asset Imports" section is the mapping table. Here you can map each Halo customer/site to an Addigy Policy.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjA1MzQ4Zjc5LWIwNWUtNGEyMC1iN2IwLTQ3YTM3MDkwMTc3YSJ9.BDKqbFc5MfsXvSHmwlIHga0PkG_tcL_kcsn0d_DY55U" width="1213" style="width: 1215px; height: 282.989px;" height="283" class="fr-fic fr-dii"></p><p><strong><span style="font-size: 10pt;">Fig 4. Asset customer mappings.</span></strong></p><p><br></p><p>Mapping customers and policies ensures assets are assigned to the correct site when they are imported. </p><p><br></p><p>Clicking the "Add" button will bring up the following popup, where you select the mappings within their respective dropdowns.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjhmMGVhY2NjLTQ5NDctNDhiNy05YjRhLTRlNDM4OTg3ZGIwMiJ9.c7BpLKpixKA6XHxEuqMMV6tg1yUVArhuNJlYGSfo9Fg" width="716" height="340" class="fr-fic fr-dii"></p><p><strong><span style="font-size: 10pt;">Fig 5. Mappings popup.</span></strong></p><p><br></p><p>If an asset belongs to a policy that is not mapped here the asset will be created under the default site, set in the "Default Asset Site" field. </p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6Ijc0M2NkNmJmLTRkNWMtNDU3NS1hNGI0LTg2NWQ2NjRjYTllNiJ9.i7pW9HCGHXvO9ozGjemgY2ZZrrBUJFN7PYYwoBSACL0" width="1218" style="width: 1220px; height: 442.821px;" height="443" class="fr-fic fr-dii"></p><p><strong><span style="font-size: 10pt;">Fig 6. Asset Imports configuration.</span></strong></p><p><br></p><p><strong><span style="font-size: 12pt;">Determine Asset Types<br></span></strong></p><p>The "Addigy Asset Type Field" will be used to set the asset type of all imported assets. This field should contain the type of the asset. Asset types will be attempted to match based on name. If the type does not exist within Halo, a new type with this name will be created.</p><p><br></p><p>You will also need to choose an asset group for any new asset types that are created to be created under. This is set in the "Default Group for new Asset Types" field. </p><p><br></p><p>Alternatively, if you do not have a field in Addigy containing asset type information you can have all assets imported as the same type. To do this set the "Addigy Asset Type" field to "Choose one existing Device Type" and pick the Halo asset type you would like all assets to be created as. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjA4YmYxMjUyLTdlZjQtNGQxOC05MjJmLWNhODNmNGFkNGM2OCJ9.5LVEa5UV2aSspWEpEbQ-KRenel-oXSxBwUrv9behRMU" class="fr-fic fr-fil fr-dib" width="778" style="width: 780px; height: 417.361px;" height="417"></p><p><strong><span style="font-size: 10pt;">Fig 7. Import all assets as the same type. </span></strong></p><p><br></p><p><strong>Asset Matching Field</strong> - This field is used to match assets to existing records if the Addigy asset has not been imported before. If matched, the existing record will be updated. This should be the unique identifier of the asset. </p><p><br></p><p><strong>Asset Matching Value Exclusions </strong>- Here you can set assets to not be matched using the matching field if the matching field contains a certain value. For example, if two assets have the matching field set to be 'None' they would match even though they are separate assets. By adding the value 'none' to the matching value exclusions list you can ensure the assets are matched using their Addigy ID instead (only assets created by importing them from Addigy will have an Addigy ID). </p><p><br></p><p><strong><span style="font-size: 12pt;">Additional Settings</span></strong></p><p><strong>Do not import Software Licences </strong>- When enabled, any software licences assigned to devices in Addigy will not be imported and created against the respective asset in Halo. </p><p><strong>Don't update the Asset type for existing or matched Assets</strong> - When enabled, asset types will be set when assets are created from Addigy, but not when existing asset in Halo are updated. Allowing you to change/reorganise the asset types of assets in Halo without Addigy reverting the types next time a sync runs. </p><p><strong>Deactivate Assets in HaloPSA when they are deleted from Addigy (Halo Integrator only)</strong> - When enabled, when assets are deleted from Addigy they will be deactivated in Halo. This only applies when using the Halo integrator to import assets automatically, not when importing assets using the 'Import assets' button. </p><p><br></p><p><strong><span style="font-size: 12pt;">Field mappings</span></strong></p><p>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.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjUzODQ0NzdkLWUyNTQtNDZhYi1iNjlhLThjNDRmZTllZmZkNSJ9.kp58iCS-pdHCgpbwdGT5c5XC6_Cgs3k__0_TAmQvNQY" width="1218" style="width: 1220px; height: 250.173px;" height="250" class="fr-fic fr-dii"></p><p><strong><span style="font-size: 10pt;">Fig 8. Asset Field Mappings table.</span></strong></p><p><br></p><p>Once this is mapped, you can click the "Import Assets" button to bring up the import screen and bring in your Addigy assets manually.</p><p><br></p><p><strong><span style="font-size: 14pt;">Import Assets Automatically on a schedule</span></strong></p><p>To have assets from Addigy imported automatically, allowing updates from Addigy to sync across, you will need to enable the Halo integrator for the integration.</p><p><br></p><p>Head to the "Halo Integrator" tab and enable "Enable the Halo Integrator for the Addigy integration". Once enabled select "Devices" as an entity to sync. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImE3YzU4OWY2LTc3YTgtNGFjZi05YjM1LTU0YWM3NWRlY2M0OCJ9.zlPUReAZkKP2fMyQtU3_Of2vLnQfl8VFNbKDpDqc8uA" class="fr-fic fr-fil fr-dib" width="822" style="width: 824px; height: 509.97px;" height="510"></p><p><strong><span style="font-size: 10pt;">Fig 15. Enable integrator to sync device (asset) information.</span></strong></p><p><br></p><p>Now, the integrator will run a daily import of assets. Updating existing assets and creating and new assets automatically. </p><p><br></p><p><strong><span style="font-size: 14pt;">Opening the Asset in Addigy</span></strong></p><p>Assets imported from Addigy will show a button at the top of the page to open a link to the same device in Addigy.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjVhMDUzODE0LTNmMjctNDllMC1iYjE1LWM5M2JkMzk0ZTIyMiJ9.Z6RduDA-IwjigGqI6kdJRsAoMOKt0MOWWZXDB8tfazA" class="fr-fic fr-fil fr-dib" width="85" height="33"></p><p><strong><span style="font-size: 10pt;">Fig 16. Addigy button on an Asset.</span></strong></p><p><br></p><p><br></p><p><strong><span style="font-size: 14pt;">Alerting</span></strong></p><p>The next section is an optional method to set up alerts. Alerting allows alerts in Addigy to automatically log tickets in Halo. Allowing you to manage/be notified of alerts from Halo.</p><p><br></p><p>To begin head to the "Alerts" tab and check "Enable alert processing". Once enabled you will need to choose the alerting method you would like to use.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjQ5YmU0NWU1LTM0NTEtNDliZi1hZGUzLTVkZDE4Njc0YTY0YiJ9.GQHhpLFJ-qGN08NQgasG9lE_PDdYx4_ATzMwvcxlDIQ" class="fr-fic fr-fil fr-dib" width="650" style="width: 652px; height: 477.802px;" height="478"></p><p><strong><span style="font-size: 10pt;">Fig 17. Alerting Methods.</span></strong></p><p><br></p><p><strong>Halo integrator</strong> - When chosen will import alerts on a schedule. Alerts will be imported once a day. This method is compatible with both the Addigy v1 and v2 API. </p><p><strong>Webhooks</strong> - When chosen alerts will be imported as soon as they are raised in Addigy. This method is only compatible with the v2 Addigy API.</p><p><br></p><p>Follow the next section in line with which method you have chosen to process alerts. </p><p><br></p><p><strong><span style="font-size: 12pt;">Halo Integrator</span></strong></p><p>If you are still using NHServer to process mail, ensure NHServer versions are correct. This will only apply to some On-Prem customers as from v2.184 hosted customers will not be using NHServer. </p><p><br></p><p>Then set the ticket type you would like alerts to be created as, and user alerts tickets should be assigned to.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImRhMzdlOGE0LWI0YTctNGYzMS04NDQyLWMyZjY0NTViZjYwZSJ9.ftsADmGUFdftgo24QpKY8RAZTPYX7Z-oTrPT59vtAC0" width="1214" style="width: 1216px; height: 294.298px;" height="294" class="fr-fic fr-dii"></p><p><strong><span style="font-size: 10pt;">Fig 18. Alerting configuration</span></strong></p><p><br></p><p>Now head to the "Halo Integrator" tab and ensure "Alerts" are added as an entity to sync here.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjdjOWRhMTBlLTBkNDQtNGJkMy05ZWM1LTk0YTMyY2VkNzAxNyJ9.iaucBfei8Z5Ifx3XjHWDHEogrIa2AfkdVwkszlwiSWs" class="fr-fic fr-fil fr-dib" width="762" style="width: 764px; height: 440.769px;" height="441"></p><p><strong><span style="font-size: 10pt;">Fig 19. Alerts as an entity to sync.</span></strong></p><p><br></p><p>When an alert is import from Addigy the ticket logged will have the device that triggered the alert as an associated asset. The alert will match to an asset in Halo based on the asset's Addigy ID (not the matching field). Keep in mind, when an asset is removed from Addigy the Addigy ID will also be removed from the asset in Halo. This will result in the asset in Halo no longer being linked to RMM alerting in Addigy. </p><p><br></p><p><strong><span style="font-size: 12pt;">Webhooks</span></strong></p><p>To have alerts processed using webhooks you will need to setup a webhook in Addigy to be sent to Halo when certain events occur. </p><p><br></p><p>For information on how to create a webhook in Addigy checkout <a data-fr-linked="true" href="https://support.addigy.com/hc/en-us/articles/28063696813331-Event-Webhooks#:~:text=Creating%20a%20Webhook,specific%20event%20in%20Addigy%20occurs" id="isPasted" target="_blank" rel="noopener noreferrer">Event Webhooks</a>.</p><p><br></p><p>The "Action Callback" of the webhook will need to be: </p><ul><li><a href="https://YOURHALODOMAIN/api/notify/Addigy?orgid=1">https://YOURHALODOMAIN/api/notify/Addigy?orgid=1</a></li></ul><p>Once you have created your webhook, obtain the validation token and enter this into the "Validation Token" field in Halo.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjIzOTRjZTFlLTM4ZDItNDkxNi1hOGM3LTQ0NWEzZTg4ODYwZCJ9.yfedEAtHHZZwQNAKaSTHybiMMZJGVy8KYSFz6TyPhe8" class="fr-fic fr-fil fr-dib" width="990" style="width: 992px; height: 625.932px;" height="626"></p><p><strong><span style="font-size: 10pt;">Fig 20. Validation token field.</span></strong></p><p><br></p><p>Then set the ticket type you would like alerts to be created as, and user alerts tickets should be assigned to.</p><p><br></p><p><strong><em>Note: Properties of the ticket logged from the alert (such as the assigned user) can be customised using variables in the webhook payload. </em></strong></p><p><br></p>
