If your primary Lifecycle Insights integration is IT Glue, you can supplement your IT Glue data with Tickets from HaloPSA by adding it as a supplemental PSA integration.

This article covers how to set up and add a PSA integration alongside your Primary IT Glue integration.

Halo Configuration

Creating an application

The first task will be to configure an application for Lifecycle Insights within HaloPSA.

The below steps will guide you through the process of configuring the required permissions in Halo. When completed, you'll have the Client ID and Client Secret required to complete the integration in Lifecycle Insights.

1. Log into HaloPSA and navigate to the Integrations page (Configuration > Integrations)
   
2. Click HaloPSA API
3. In the Applications section, click View Applications
   
4. Create a new application by clicking New in the upper right of the screen
5. Populate the Add an Application page with the following information:
   • Application Name: Lifecycle Insights (or any appropriate name you choose)
   • Ensure that the Active checkbox is checked
   • Select Client ID and Secret (Services) as the authentication method
   • Login type: Agent
   • Agent to log in as... This can be any agent with Read and Modify access to Sales, Assets, Customers, Contracts, Projects and Tickets in HaloPSA
     
     IMPORTANT - Before proceeding, be sure to copy both the Client ID and Client Secret and keep them accessible. These will be required to integrate with Lifecycle Insights.
     
      
6. Click Save before proceeding to the next section

Setting up application permissions

Now that the application has been set up and the API credentials generated, the next step will be to apply the correct application permissions so that Lifecycle Insights can retrieve data from HaloPSA. The below set of instructions will guide you through this process.

1. From the newly created application page, click the Permissions tab beneath the name of the application
2. Click Edit in the toolbar at the top of the page to allow you to choose the required permissions
3. Check the following permissions:
   • read:tickets
   • edit:tickets
   • read:customers
   • read:crm
   • edit:crm
   • read:contracts*
   • read:projects*
   • edit:projects*
   • read:sales
   • edit:sales
   • read:assets
   • edit:assets
     
     Note: Selections marked with an asterisk (*) denote permissions that Lifecycle Insights will require in the future. These won't be used immediately.
      
4. Click Save

Setting up ticket types

You can create opportunities within Lifecycle Insights and export them directly into HaloPSA. In order to enable this functionality, you need to set up allowed ticket types.

You will need to complete the following steps for each customer that you wish to integrate with Lifecycle Insights and use our vCIO tools with.

1. Navigate to the Customers module in HaloPSA (Return to the Home screen and click Customers)
   
2. Select a customer from the list by clicking the customer name, and then click Edit at the top of the page
3. From the navigation bar beneath the customer name, click Settings (You may need to scroll to the right to see this option)
   
4. Expand the Ticket Types section
5. Ensure that the Opportunity types you have created in HaloPSA appear in the list. You can do this by checking the box that reads Allow use of all Ticket Types
   
6. Click Save

Repeat these steps for each of your vCIO customers to ensure tha available ticket types can be created in Lifecycle Insights

Preparing Integration API information

To complete the setup in HaloPSA and prepare to enable the integration in Lifecycle Insights, you'll need to collect some final details.

As well as the Client ID and Client Secret that you already gathered, you will need the Resource server URL, Authorization Server URL and Tenant name.

This information can be retrieved from HaloPSA by following these steps:

1. Navigate to the Integrations page of HaloPSA (Configurations > Integrations)
2. Click HaloPSA API
3. Expand the API details section
4. Copy the following information and keep it accessible:
   • Resource server URL
   • Authorization Server URL
   • Tenant Name
     

Before proceeding, ensure that you have the following information. It will be required to complete the integration in Lifecycle Insights:

• Client ID
• Client Secret
• Resource Server URL
• Authorization Server URL
• Tenant Name

Lifecycle Insights Configuration

Now that the application has been set up and you have all of the data required from HaloPSA, the integration can be enabled in Lifecycle Insights. These steps will guide you through the process of finalizing the integration.

1. Log into Lifecycle Insights via app.scalepad.com and click the Lifecycle Insights icon
   
   
2. From the navigation panel on the left, click Integrations under the administration section
   
   
   
3. Click Halo from the list of available integration sources under PSA Integrations
   
   
   
4. Check the boxes beside
   
   • Pull Tickets from Halo
   • Enable Halo Opportunity Integration
     
     
5. Fill in the required information that was gathered from HaloPSA in the previous section of this article:
   • Resource Server URL
   • Authorization Server URL
   • Tenant Name
   • Client ID
   • Client Secret
     
     
6. Click Test Settings. If everything was entered correctly, you will see a message reading "Connection Successful"
   
   
7. Click Save Settings. If this is your first time saving your HaloPSA credentials, Lifecycle Insights will immediately begin the initial sync process.
   
   Note: It can take up to an hour for the initial data sync to complete. This delay should only apply to the initial sync. You will receive an email notification upon its completion.

Linking Companies from IT Glue with HaloPSA

The final steps required to integrate HaloPSA as a supplementary integration is to match your active companies syncing from IT Glue with those syncing from HaloPSA.
This allows Lifecycle Insights to understand how tickets from HaloPSA are associated with companies from IT Glue.

1. From the HaloPSA supplementary integration you just set up, click the Link Companies to IT Glue tab.
   
   
2. After the initial HaloPSA sync is completed, choose the company from the dropdown under Halo Company (Link) that matches the corresponding company under ITGlue Company (Active in LCI)
   
   

Auto Mapping Companies

As an alternative to manually mapping companies, you can use the Automap feature to match the companies syncing from IT Glue and HaloPSA.

To use the auto mapping feature, click the blue Automap button at the top of the list



Lifecycle Insights will attempt to match any exact or near-exact matching company names and associate them accordingly.

Once the Auto Mapping process is complete, the companies that were matched will be highlighted in green in the table.

Company names that do not match exactly may not be identified using the Automap feature. Be sure to review the matches and ensure they are correct by using the drop down to manually adjust them.

Once you have confirmed that the matches are correct and complete, click Save changes at the top of the list.

After completing the above, your HaloPSA supplementary integration with Lifecycle Insights is complete!