HaloPSA Roadmap
Find out about all the exciting, up and coming developments in HaloPSA
In Progress
Microsoft Azure billing Integration
Integrate with Azure for consumption billing data to be imported to Recurring Invoices
Google Workspace multiple tenanted
Google Workspace integration to allow multiple tenants to be integrated simultaeously
PandaDocs Integration
Integration with PandaDocs to push Quote data into PandaDocs documents and allow PandaDocs to handle sign-off of documents
Lighthouse Integration for Windows Defender
Integration with Microsoft Lighthouse for handling alerts created through Defender
CSP and Office 365 automation
Approval processes to automatically create users/assign licenses and update license amounts in Office365 via Azure/CSP/Pax8 and other vendors APIs
Up Next
Go Cardless Integration
Google Maps & Agent Lookup
Adding functionality to track all active agents on Google Maps.
Bulk/Marketing email function
A new area of Halo to send mass/bulk emails to email lists that are created using the report builder
Telnyx Integration
SMS integration to allow sending and receiving of SMS messages
AWS Billing integration
Import billing data from AWS for automating invoice creation
Future
Microsoft Lighthouse Integration
Integration with Microsoft Lighthouse for management of customer tenants
Sentinel One Integration
Handle alerts created from Sentinel One
NMI Payment Gateway
Recently Completed
Added the Coralogix integration
A Coralogix integration is now available, allowing tickets to be created in Halo when alerts are triggered and closed when the alerts are resolved.
Once the integration is enabled, a runbook will automatically be added.
You will need to configure a webhook in Coralogix to post to the URL of your runbook, the UUID of which will need to be entered into the conditions of the first step of the runbook. The notes on the runbook explain exactly what is required and link to Corlogix's guide on how to set up webhooks.
The runbook can be customized to change the content of the tickets created in Halo or to adjust the action added when the alert is resolved.
Adobe Commerce (Magento) Integration is now available
This integration will allow you to import Customers registered to your Adobe Commerce/Mageneto store as well as Orders made on the store. Users are also created from the Orders import, to allow you to link Tickets from Customers to Orders.
Customers and Orders can also be imported on a schedule via the Halo Integrator.
XSOAR integration is now available
This integration allows for the creation of tickets in Halo from incidents in XSOAR.
For instructions on how to configure this please consult the following guide: https://halo.haloservicedesk.com/kb?id=2056
TD Synnex StreamOne ION integration now available
This is for TD Synnex's StreamOne ION Reseller API.
OAuth credentials can be created for any user within in your ION account that has the 'Account Admin' user role.
The Test Configuration button on the integrations page tests whether the Halo API can connect to the StreamOne ION API.
Customers:
Customers can be mapped and imported from StreamOne ION. Mappings can be set up manually or through the generate mapping option. Customer imports can be through the UI or the integrator.
There are further options to choose a top level for imported customers if top levels are enabled in Halo and to update the main site address of existing customers imported through this integration.
Subscriptions:
Subscriptions can be imported for any mapped customer either manually or via the Halo Integrator.
Various improvements to OLAs
OLAs can now be linked to rules. This can either be configured from the OLA or from the ticket rule.
If one of the linked rules is matched, and the workflow is on one of the start steps/stages for the OLA, the OLA will be started against the ticket.
If the rules stop being matched before the OLA is completed, it will be paused. OLAs can be resumed if any of the rules are matched again. All in-progress or paused OLAs will be completed when the ticket closes.
A tab will now show on tickets with OLAs against them, showing their target date, status, and if they were met or not.
Added TechData and Ingram Micro product catalog integrations
Integrations with Tech Data's and Ingram Micro's Catalogs have been added under a new integration group 'Product Catalogs':
These function in tandem with the Etilize integration to provide further information regarding products availability and price when using the 'Add Etilize items' option on billing orders. Below is an example of a returned item:
The cheaper customer price will be selected when adding the item to the order and the default mark up will be applied.
There are also options in the Etilize set up screen to choose a default 'Tenant' to search the catalogs with:
This can be modified on the item search screen itself as well.
Added the ability to import organizations and devices from Cisco Meraki
Meraki Webhooks integration renamed to 'Cisco Meraki'
The existing webhook alerting functionality is part of the 'Alerting' tab, with the addition of the option 'Device Serial Number (Meraki) to Asset ID (Halo)' for asset field matching.
Under the setup tab is where you specify your Meraki URL and API key. You will need to generate an API key in Meraki to allow authorisation for Organisation and Asset imports:
Organisation Imports
This integration will allow you to import organisations from Meraki as organisations. These can be mapped to update existing client information.
Asset Imports
This integration will also allow you to import assets from Meraki as assets. You will need to have organisation mappings in place to import the relevant assets.
Field mappings can be set up to map Meraki fields to asset/custom fields.
LapSafe integration is now available
A LapSafe integration is now available, which allows for the creation of Drop Offs and Collections in LapSafe.
Configuration
To use this integration you need to generate a personal access token in LapSafe and enter it in Halo. Additionally, if you wan tickets to automatically update when a Drop Off/Collection is completed you will need to set up webhooks in LapSafe and enter the secret in Halo.
There are various default settings for the integration, most of which can be overridden at other levels.
- Default Installation - This is the installation to default to when doing actions. This can be overridden at site and action outcome level.
- Default Bay Size - This is the default size of bay to request. This can be overridden at action outcome level.
- Default expiry to x hours from now - This is the default value for when the Drop Off/Collection should expire.
- Status after Drop Off/Collection Completion - This is the status after a Drop Off/Collection is completed or cancelled, either manually or automatically via webhook. This can be overridden at ticket type level.
- Email Template for Drop Off/Collection Actions - This is the email template used to send the user of the ticket their locker name and code.
To include the locker name and code for a Drop Off/Collection in an action, use the $-LOCKERNAME AND $-LOCKERCODE variables respectively. These will use the value for the primary Drop Off/Collection if multiple are linked to the same ticket. Only one of these should be pending at any given time.
Drop Offs
To create a Drop Off, you need to create an action with system use "Create Drop Off" and the fields:
- LapSafe Asset - This defaults to the inventory number of the primary asset of a ticket, otherwise it needs to be populated with a name.
- LapSafe Installation
- LapSafe Bay
- LapSafe Expiry Date
If any of these fields are excluded, they will use the default values specified in the configuration.
When this action is used, it will create a user in LapSafe with the email of the ticket user if one does not already exist.
Then it will create Drop Off in LapSafe and send an email to the user with the locker name and code.
Collections
To create a Collection, you need to create an action with system use "Collection" and the fields:
- LapSafe Location
- LapSafe Asset - This will list all the assets currently available for collection in LapSafe at the location you have selected
- LapSafe Expiry Date
If any of these fields are excluded, they will use the default values specified in the configuration.
When this action is used, it will create a user in LapSafe with the email of the ticket user if one does not already exist.
Then it will create Collection in LapSafe for the specified asset, and send an email to the user with the locker name and code.
NOTE: The user of the ticket must have a valid email to create both Drop Offs and Collections.
Ticket Details
When a ticket is linked to a Drop Off or Collection, an additional tab will be shown.
Here you can view the details of them and go to them in LapSafe.
You can also right-click to manually complete or cancel any of the currently pending ones. This will update LapSafe and add an action to the Halo ticket.
GoCardless integration is now available (CRM)
This integration with GoCardless will allow you to import your GoCardless Customers as Users.
You will then be able to view any payments the User has made on their User Details:
You can double click a Payment to open it in GoCardless.
Payment processing for GoCardless is coming soon.
Avalara integration is now available
You can now connect each of your Avalara Companies to a Avalara Connection in Halo. This will allow you to:
- Import customers and sync them to Avalara
- Create transactions in Avalara in Quotes, POs, SOs and Invoices to calculate the tax
- Allow item code selection at Halo Item Group level