Halo PSA Integration

HaloPSA is an ERP system for MSPs to manage most of their workflows. Here’s a list of main modules/features that they provide:



It’s a platform that helps MSPs plan, track, and manage their work. Zomentum Grow is integrated with their sales and customer relationship management (CRM) module, to allow linking of opportunities and quotations with HaloPSA. This update enables HaloPSA users to drive their sales using Zomentum. Users will save time and get that data in Halo to continue with the next process.


Entity mapping between Zomentum and HaloPSA

 

Required HaloPSA Settings:

1. Getting AuthServer and resource server 
In HaloPSA, go to Configurations > Integrations > HaloPSA API.

2. Getting ClientId and Client Secret
In HaloPSA, go to Configurations > Integrations > HaloPSA API.

Note: Assign Login Type as Agent in HaloPSA under the registered application.

 

The following are the minimum required permissions:

"admin"
"read:customers"
"edit:customers"
"read:sales"
"edit:sales"
"read:items"
"edit:items"
"read:quotes"
"edit:quotes"
"read:assets"
"read:suppliers"
"Edit:suppliers"
"Read:POS" and "Edit:POS"

Note: Admin permission is required to create Webhooks in HaloPSA.We create Webhooks in HaloPSA while integrating so that any update in Halo Entities and can be pushed realtime from haloPSA to Zomentum.

HaloPSA do not  have any other permission which can give us access to create or update Webhooks,

Admin is the only permission which gives access to create Webhooks.

Read: POS and Edit: POS permissions: This is a Purchase orders permission.


Getting credentials for setting up with Zomentum:

You need to get the credentials from HaloPSA. It includes Auth Server, Resource Server, Tenant, ClientID, and Client Secret. And after adding the necessary credentials hit on “Check credentials” that would check for a few permissions.

 

Zomentum and HaloPSA integration

With HaloPSA, we integrate with their sales and CRM module. As a prerequisite, an MSP has to enable the below two modules within Zomentum:

1. Sales module - This will enable Zomentum to create opportunities in HaloPSA
2. Quotation module - This will enable Zomentum to create quotations in HaloPSA

Getting credentials for setting up with Zomentum

You need to get the credentials from HaloPSA. It includes Auth Server, Resource Server, Tenant, ClientID, and Client Secret. And after adding the necessary credentials hit on “Check credentials” that would check for a few permissions.

Setting up your HaloPSA account with Zomentum

(a) Connect

1. Navigate to Settings > Integrations tab

2. Under 3rd party integrations-> HA -> Click on Connect.
   

3. Enter the Halo PSA credentials in the ‘Connect.’. Click on check credentials (this may take a few seconds), and hit ‘Save and proceed’.
   Note: After you add the credentials and hit on ‘check credentials,’ the system will take a few seconds to check with HaloPSA if all permissions are available. If anything is missing, you would see an “X” near the respective modules.

(b) Settings

With the real-time sync ability, all account, and quote-related information will be synced between Zomentum and HaloPSA depending on the filters. Do note that the Products are not synced in real-time. The products are only synced once every hour.

You can also apply the below filters:

1. Only Sync Opportunities where the Team is
   You can select a particular team and only opportunities belonging to that team would sync.
   
   

2. Only Sync Opportunities where the Assigned Agent is

   You can select an assigned agent and only opportunities belonging to that assigned agent would sync.
   
   

3. Only Sync Opportunities where the Status is
   You can select a particular status and only opportunities belonging to that status would sync.
   
   

4. Only Sync Opportunities where the Type is
   You can select a particular type and only opportunities belonging to that type would sync.

Note: The respective team, agent, status, and type can be selected for filtering the opportunities alone.

(c) Field Mapping

We have two different types of mapping :

1. Selected Pipeline:

   Ability to set the default pipeline and map opportunity stages between Zomentum and HaloPSA.

 

2.  Tax Mapping - 
   
You have the option to import tax rates and map the tax categories between Zomentum and HaloPSA.

You can set Default Tax Rate while exporting if the mapping is not present. Also, you can set Default Tax Category while importing if the mapping is not present.

 

3. Opportunity - 

Opportunity fields can be mapped here.

Note: Ensure the data type of the fields being mapped is the same. Wrong data type field mapping may cause the field not to be updated.

If an opportunity stage is not mapped, the data won't sync when the opportunity is moved to that stage.

4. Client:

Client fields can be mapped here.

Note: Ensure the data type of the fields being mapped are same. Wrong data type field mapping may cause field not to be updated.

5. Contact:
Contact fields can be mapped here.

Note: Ensure the data type of the fields being mapped are the same. Wrong datatype field mapping may cause the field not to be updated.All the contacts that are created in Zomentum will be synced under the default Site in HaloPSA

6.  Product Mapping - 
We have the option to create and sync the below fields in Zomentum from HaloPSA. Here are three options

1. Map Product Type with Asset Group

2. Map Product Type with Asset Type

3. Sync all items as type 'Other' to Zomentum
   
   

And we provide the option to map product type and description:

Here are more options:

 

All the request outbound from the Zomentum server goes through the following set of IP addresses. You must white list the following IP addresses in your firewall settings to allow inbound requests from Zomentum to your HaloPSA instance -

• 3.210.175.249 

• 34.224.144.84 

• 50.17.76.20 

• 34.197.122.8
  
  Note: Any updates take at least 3 minutes to sync from Zomentum to Halo PSA

FAQs

1. There are two settings to set in HaloPSA to enable new products to sync to Xero without further input in HaloPSA:

2. The minimum permissions required for creating a Zomentum user are as follows: 
“Admin”
“Read customers”
“Edit: customers”
“Read sales”
“Edit: sales”
“Read items”
“Edit: items”
“Read quotes”
“Edit: quotes”
“Read assets”
“Read: suppliers”
“Edit: suppliers”

Note: Admin permission is required to create Webhooks in HaloPSA.We create Webhooks in HaloPSA while integrating so that any update in Halo Entities and can be pushed realtime from haloPSA to Zomentum.

HaloPSA don’t have any other permission which can give us access to create or update Webhooks,

Admin is the only permission which gives access to create Webhooks.

3. Changes made to the product are not synced back to Zomentum because
Products are not imported in real-time from HaloPSA.  It will be imported by periodic sync or the customer can save and sync again.


4. ​​Documents get synced from Zomentum to Halo PSA whenever there is a status update, the document should be changed from one status to another for the document to get pushed from Zomentum to Halo PSA. From a Zomentum perspective when a document is created it is set to “Draft” status, so any status updated from the draft status would trigger the sync.
​
5. The target date is Halo PSA is mapped with an estimated close date in Zomentum.


6. Once there is a status change of a document in ZM it is pushed to Halo under the “Quotations” section. We just push the information to the HaloPSA quote further actions is to be taken by the client on the HaloPSA side and everything is manual.

7. If an entity is synced with PSA, and the client deletes it on the PSA side, we stop syncing it with the PSA. 


8. There should be no mandatory fields set on the Opportunity Type on Halo PSA.