# Integrations ## Halo Integrator [Self Service Portal (haloservicedesk.com)](https://support.haloservicedesk.com/portal/kb?id=1062) The Halo Integrator is a separate application from the Halo Web tool, designed specifically for executing integration imports on a regular schedule. ## Automate Integration [Halo Support Portal - ConnectWise Automate Integration (haloservicedesk.com)](https://support.haloservicedesk.com/portal/kb?id=1035) ### Integration Questions - Do we want to import printers? - How can we sort alerts by type/sub-type/item (or Halo equivalent) ### Integration Considerations - Create, append, and auto-complete/close tickets based on Automate alerts? - Alerts will go into Halo from Automate via email. - Alerts must all be renamed to include the device tag in the subject line of the email. ## NinjaOne Integration - Can import software from Ninja into Halo. - Alerts use a webhook so that if an alert is automatically resolved in NinjaOne, then the ticket will be automatically closed in Halo. If the ticket is closed in Halo, then the alert will be reset in NinjaOne. ## Auvik Integration - Alerts are created using Auvik webhooks. When a ticket is closed in Halo, the linked Alert will be automatically dismissed in Auvik. If the alert is resolved automatically in Auvik, then the linked Ticket will be automatically closed in Halo. ## Addigy Integration [Halo Support Portal - Addigy Integration (haloservicedesk.com)](https://support.haloservicedesk.com/portal/kb?id=1704) - There is no Addigy integration. # Halo Academy ## Service Desk - Generally tickets are all visible - Ticket templates are going to be a great way to push standards. - Load balancing ## Questions - Can we pull information from other tools (Automate or other API calls) for custom fields? To pull local admin password for example.