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.
Table of Contents
How to connect your Zomentum account with Halo PSA?
Required Halo PSA Settings
Connect to Halo PSA in Zomentum
Select what to sync between Halo PSA and Zomentum?
Mappings
Pipeline Mappings
Tax Mappings
Opportunity Field Mapping
Client Mapping
Product Mapping
Entity mapping between Zomentum and HaloPSA
Whitelist IP Addresses
How to connect your Zomentum account with Halo PSA?
The integration between Zomentum and Halo PSA is seamless; however, it does require some one-time settings to be configured within Halo PSA before proceeding. The detailed instructions for these required settings are provided below.
1. Required Halo PSA Settings
Get AuthServer, ClientServer, and Tenant from HaloPSA
1. Navigate to Halo PSA configuration settings
2. Select Integrations.
3. Click on HaloPSA API.
4. Make a note of the following details:
- Authentication Server
- Resource Server
- Tenant Name
5. Fetch Client ID and Client Secret from HaloPSA
- Scroll down to find the ‘View Applications’ button and click on it. Then create a new Application using the ‘New’ button on top.
Note: The following steps vary depending on whether you select and Admin User or a Non-Admin User as the 'Agent to login as' on the 'Add an application' page. We recommend selecting an Admin User to avoid any complexities. However, please refer to the appropriate steps for your user type
- If you selected an Admin User as the ‘Agent to login as’, proceed by entering the required details on the ‘Add an Application’ page, as shown below.
- Please ensure that you select the ‘Login Type as ‘Agent’.
Skip to point 'Enable permissions required for the Application' if you have selected admin user.
- If you selected a Non-Admin user as the ‘Agent to log in as’, please ensure the user has the following specified permissions enabled, as well as unrestricted access to tickets. Otherwise, the workflow may be disrupted.
Follow the steps below to check the permissions:
1. Go to Configuration.
2. From the side menu, select Teams & Agents.
3. In the dropdown submenu, choose Agents.
4. Select the agent whose permissions you want to check.
5. Click on the Permissions tab in the top menu.
6. Verify that the permissions match the ones specified below.
Feature Access
Tickets Access Level - Read and Modify
Clients Access Level - Read, Modify and Delete
Users Access Level - Read and Modify
CRM Access Level - Read and Modify
Assets Access Level - Read and Modify
Calendars and Appointments Access Level - Read and Modify
Knowledge Base Access Level - Read and Modify
Suppliers Access Level - Read and Modify
Items Access Level - Read and Modify
Sales Access Level - Read and Modify
Quotations Access Level - Read and Modify
Tickets Permissions
Can add new Tickets - Yes
Can edit closed Tickets - Yes
Can view Unassigned Tickets - Yes
Can view Tickets that are assigned to other Agents - Yes
Can change a Ticket's Ticket Type - Yes
Can Re-assign Tickets - Yes
Can Edit Advanced Ticket Details - Yes
Editing of Actions - Can Edit All Actions
Can assign to Agents in Teams the Agent is not a member of - No
Can remove To-Do items - Yes
Asset Type Restrictions
Allow use of all Asset Types - Yes
Accessible Ticket Types
Name - Opportunity
Entity - Ticket Type
Permissions - Create, View, Edit
Asset Field Restrictions
Allow use of all Asset Fields - Yes - Proceed with entering the rest of the details on the ‘Add an Application’ page, as shown below.
Enable permissions required for the Application:
You can either Select “all” or below specified 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"
"edit:pos"
Connect to Halo PSA in Zomentum
Go to Settings in Zomentum.
Select Integrations from the submenu on the side.
Find the HaloPSA integration from the list.
Enter the details you noted down previously.
Input the necessary information, including the Client ID and Client Secret.
Select what to sync between Halo PSA and Zomentum?
Enable the Sync Category in the integration settings, and specify the items under the relevant categories as shown in the image below.
Note: Zomentum supports Real-time sync for HaloPSA, which is enabled by default
Important: Once data is imported into Zomentum from HaloPSA without filters, it cannot be undone by adding filters and reconnecting. Therefore, ensure that you select filters during initial sync if you only want to import specific data from PSA.
Mappings
Pipeline Mapping
Select Zomentum Pipeline to import opportunities from HaloPSA and select preference
Map to Zomentum Pipeline Stage to HaloPSA Status
Map to Zomentum Pipeline Stage to HaloPSA Pipeline Stages
To map Zomentum stages with HaloPSA pipeline stages, ensure that the setting below is enabled in HaloPSA. Without this setting, mapping will not be possible in Zomentum.
Tax Mapping
Map Zomentum Tax Region - Tax Category to HaloPSA Tax rates
Import Tax Module Flow
Select Zomentum Tax Region: Choose the tax region under which HaloPSA tax rates will be imported. Then, select one of the following options:
Deactivate Existing Tax Rates and Import:
If this option is selected, all other tax regions in Zomentum will be disabled, and HaloPSA tax rates will be imported as tax categories under the selected Zomentum tax region.
Import and Keep Existing Tax Rates:
If this option is selected, HaloPSA tax rates will be imported as tax categories under the selected Zomentum tax region without affecting the existing tax rates.
Opportunity Field Mappings
Map Zomentum Opportunity Fields with HaloPSA Opportunity Fields
Note: if you cannot find custom fields or other fields from Halo opportunity to map in Zomentum, add the custom fields to the "Field List" for all opportunities types in HaloPSA. Then, restart the connection process Zomentum from the beginning.
For example, below is the field list for the Halo opportunity type “Opportunity.”
Client Mapping
Map Zomentum Client Company Fields with HaloPSA Client and Site fields
Note:
The Zomentum Client Billing Address and Default Shipping Address will be mapped to the Halo Client Site Billing Address and Shipping Address. The field mappings for these addresses are detailed below.
For different shipping addresses in a Zomentum Client, we will create separate Halo Sites with distinct shipping addresses but the same billing address, corresponding to the Zomentum Client.
Product Mapping
You can map the Zomentum product type using one of three options: Halo Asset Group, Halo Asset Type, or by syncing all items as ‘Other’ in Zomentum.
Explanation of Asset Group Mapping Flow:
In the example above, the Zomentum Item Type “Hardware” is mapped to the Halo Asset Group “Non-Serialised,” as well as additional Halo Asset Groups “Asset Group H” and “Asset Group B.” This means that Halo items with these asset groups will be classified as “Hardware” in Zomentum.
Additionally, two custom fields will be automatically created in Zomentum, representing the asset group and asset type values.
An example is shown below in the ‘Edit Product’ drawer of Zomentum:
When exporting from Zomentum according to the above mappings:
“Hardware” will be exported as the Halo Asset Group “Non-Serialised” (Default).
If you want to export “Hardware” as “Asset Group B” in HaloPSA, change the “Halo Item Asset Group” value in the custom fields of the item.
Explanation: “Sync all types as ‘Other’ in Zomentum”
All Halo items will be imported as the Zomentum item type “Other”. The custom fields will reflect the corresponding Halo asset group and asset type values.
Note:
Current Limitations in Item Field Mapping:
The Zomentum Manufacturer Name and SKU can only be mapped to the Halo Manufacturer and SKU.
Alternatively, the Zomentum Item First Pricing Supplier and SKU can only be mapped to the Halo Manufacturer and SKU.
Entity mapping between Zomentum and HaloPSA
Important Points to Note:
Entities in Zomentum are archived if they are marked as Inactive in HaloPSA.
Once a client, contact, or opportunity is exported from Zomentum, updates from HaloPSA will not sync to the same entity for two minutes. This delay is implemented to prevent a continuous update loop between the two platforms.
To re-trigger the export of a won document, move the corresponding Zomentum opportunity to a Non-Won Stage and then back to the Won Stage.
Zomentum Quote Attachments can be found under the Halo Quote Attachment section.
If the agent associated with the “Zomentum Application” in HaloPSA encounters permission issues for opportunities, you may receive a 404 error instead of a 403. This can cause the opportunity to be forced from Zomentum, potentially leading to duplication.
Whitelist IP Addresses
All outbound requests from the Zomentum server are sent through the following IP addresses. To ensure proper communication, please whitelist these 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