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

It is 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 would save time and get the data in Halo to continue with the next process.

Entity mapping between Zomentum and HaloPSA:

Required HaloPSA Settings:
The first step involves fetching the ClientID and Client Secret. 

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

Click on HaloPSA API > View Applications to add Zomentum as a new application.


After adding Zomentum as a new application, generate the Client ID and Client Secret. 

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

Recommended

The agent attached to the Zomentum application must be an admin to avoid any permission issues.

If any other agent is attached to the Zomentum application then make sure that the agent has a team that has access to tickets and has all Read and Modify permissions on haloPSA entities.

For example - Agent: cewixi1535 which is not an admin.

Required Zomentum application permissions:

"admin:webhook" OR "admin" (if "admin:webhook" is visible to you in haloPSA use that else select "admin" permission)

"read:customers"

"edit:customers"

"read:sales"

"edit:sales"

"read:items"

"edit:items"

"read:quotes"

"edit:quotes"

"read:assets"

"read:suppliers"

"Edit:suppliers"

"read:pos" (purchase order read permission)

"Edit:pos" (purchase order write permission)

The second step involves getting the AuthServer and Resource Server credentials. 

Getting AuthServer and Resource Server Credentials

In HaloPSA, go to Configurations > Integrations > HaloPSA API.

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

1. 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 tab. Click on Check Credentials, and hit Save and proceed.
   
   

Note: After you add the credentials and click 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.

2. Settings

With the real-time sync ability, all account and quote-related information is synced between Zomentum and HaloPSA depending on the filters.

The following filters can be applied:

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.

3. Field Mapping

The following mapping types are available:

1. Selected Pipeline

Enable Halo Pipeline Stage mapping in haloPSA as shown in the following images to map Zomentum Pipeline Stages with HaloPSA pipeline stages:

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 the 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 would not 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 the same. Wrong data type field mapping may cause the fields 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 data type 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
   You can create and sync the following fields in Zomentum from HaloPSA:

1. Map Product Type with Asset Group

2. Map Product Type with Asset Type

3. Sync all items as type 'Other' to Zomentum
   
   You can also map the product type and description:
   

   
   

   
   
   Here are a few 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

FAQs :

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

   

   
   

   
   
2. 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.
   
   
3. Documents are synced in real time whenever there is a change in the quotation level or any status change.
   
   
4. If an entity is synced with the PSA, and the client deletes it on the PSA side, we stop syncing it with the PSA. 
   
   
5. There should be no mandatory fields set on the Opportunity Type on Halo PSA.