Knowledge Base
Introduction
Configuring MSP Process and HaloPSA to work with one another is a quick and easy process that is composed of a few steps:
- Creating an Agent in HaloPSA that has the appropriate roles and permissions.
- Creating an Application within the HaloPSA API
- Providing MSP Process with the appropriate URL and tokens to communicate with HaloPSA.
- Creating a custom tab in HaloPSA that will display the MSP Process Pod
Once you've completed the steps in this KB article, you'll have MSP Process and HaloPSA communicating with one another, and you'll be ready to move on to the next KB article: Step 2: Setup the MSP Process "Custom Tab" in Halo.
Creating an Agent in HaloPSA
- Sign into your HaloPSA system
- Navigate to Configuration -> Teams and Agents -> Agents
- Click the New button to add a new agent
- Provide a name for the agent; we recommend MSP Process Agent
- Specify a password that meets your organizations security rules
- Assign the agent a Role; we recommend the default Role called 1st Line Support (or your equivalent if you’re modified the Roles in your Halo PSA instance)
- Enable the Is an API-only agent option
- Fill out any other mandatory fields (such as the Team and Working Hours fields)
- Click Save
- Edit the MSP Process Agent account; on the Permissions tab, enable the "Can Delete Tickets" option:
- Click Save
NOTE: The ability to delete tickets is only needed when setting up a Ticket Default in MSP Process, as validating the Ticket Default involves creating and then deleting a ticket in Halo PSA. Once the ticket default has been setup, you can disable the "Can Delete Tickets" option.
Creating an Application within the HaloPSA API
- From the Halo PSA UI, navigate to Configuration -> Integrations -> HaloPSA API
- Take note of the Resource Server URL; you'll need it (including the https:// prefix, but without the /api at the end) during one of the configuration steps with MSP Process
- Within the Applications portion of the page, click the View Applications button
- Click the New button to add a new application
- Specify a name for the application; we recommend MSP Process
- Within the Authorization Method section, select Client ID and Secret (Services)
- Copy the ClientID and Client Secret; you'll need it during one of the configuration steps with MSP Process
- Ensure that the Login Type drop-down menu is set to Agent
- Open the Agent to log in as drop-down menu, and choose the Agent you configured in the Creating an Agent in HaloPSA section
- Click the Save button
- Dismiss any permissions-related messages that appear; we'll be configuring those next
- On the Permissions tab, click the Edit button and enable the following permissions:
- read:tickets
- edit:tickets
- read:customers
- edit:customers
- read:crm
- edit:crm
- read:items
- edit:items
- Click the Save button
Providing MSP Process with the appropriate URL and tokens to communicate with HaloPSA
- Login to the MSP Process UI (https://app.mspprocess.com)
- Navigate to Integrations -> PSA Integrations
- Click on the Add new PSA icon
- Click the HaloPSA icon
- Specify the ClientID and Secret that you obtained in step 7 of the Creating an Application within the HaloPSA API section
- Specify the Resource Server URL (remove the /api at the end) that you obtained in step 2 of the Creating an Application within the HaloPSA API section. Note that the URL must start with https://
- Click Submit to save the HaloPSA configuration settings
- Finally, fill in the ticketing default fields; these values will be used when leveraging MSP Process to create tickets
- Click Submit to finish setting up the HaloPSA module in MSP Process
The final step to take in setting up the MSP Process -> Halo PSA integration is to configure a Custom Tab within Halo PSA that'll contain the MSP Process pod.
The first step is to obtain the URL for your MSP Process pod; to do that, go to Integrations -> PSA Integrations -> Halo
Click on the Get Link to v2 Pod as shown below:
Login to Halo PSA and click on Settings -> Custom Objects:
Click on Custom Tabs:
Create a new custom tab, and specify the details as outlined below:
Once you've saved that Custom Tab, the final step is to associate it with the appropriate Ticket Types - Halo lets you choose which types of tickets have what Custom Tabs, so you can customize what your Technicians can do and see.
Navigate to Configuration -> Tickets -> Ticket Types, and edit the Ticket Type (for example, Incident). On the Allowed Values tab, there is a Custom Tabs section; add the MSP Process custom tab there, or enable the Allow all Custom Tabs option.
Once you've finished modifying the Ticket Type, save your changes. You're done! Now you'll see the MSP Process custom tab show up in your tickets: