← frankieryan.com

Index / Integrations

LIFECYCLE INSIGHTS

Integrating with HaloPSA

Originally published on Lifecycle Insights's help center · View live article ↗

Why this piece is featured

A full role, permission, and API-scope walkthrough across two connected systems — exact HaloPSA ticket, asset, and API-scope permissions in table form, paired with the Lifecycle Insights side of the connection.

This article guides you through integrating HaloPSA with Lifecycle Insights.

Before you begin

Who can use this feature? Administrator users. What you'll need: Admin access to a HaloPSA account.

HaloPSA configuration

Creating an application

The first task is configuring an application for Lifecycle Insights within HaloPSA. When complete, you'll have the Client ID and Client Secret required to finish the integration in Lifecycle Insights.

  1. Log into HaloPSA and navigate to Configuration > Integrations > HaloPSA API.
  2. In the Applications section, click View Applications, then click New.
  3. Populate the Add an Application page: - Application Name: Lifecycle Insights (or any name you choose). - Ensure Active is checked. - Authentication method: Client ID and Secret (Services). - Login type: Agent. - Agent to log in as: select an agent with Read and Modify permissions for Sales, Assets, Customers, Contracts, Projects, Tickets, Invoices, and Item costs.

Note

The agent used to log in needs access to any relevant departments in order to sync tickets, opportunities, and contracts to or from those departments.

Before proceeding, copy both the Client ID and Client Secret and keep them accessible — you'll need them to complete the integration in Lifecycle Insights.

  1. Click Save before continuing.

Setting up application permissions

  1. From the new application's page, click the Permissions tab, then Edit.
  2. 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:invoices, read:assets, edit:assets.

Note

read:projects and edit:projects are permissions Lifecycle Insights will require in the future — they aren't used immediately.

  1. Click Save.

Setting up ticket types

You can create opportunities within Lifecycle Insights and export them directly into HaloPSA. To enable this, set up allowed ticket types for each customer you want to integrate and use vCIO (virtual CIO) tools with.

  1. Navigate to Customers, select a customer, and click Edit.
  2. From the navigation bar, click Settings and expand Ticket Types.
  3. Check Allow use of all Ticket Types to make sure the opportunity types you've created in HaloPSA appear in the list.
  4. Click Save, and repeat for each of your vCIO customers.

Preparing integration API information

To complete setup, gather the Resource server URL, Authorization Server URL, and Tenant name, alongside the Client ID and Secret you already collected:

  1. Navigate to Configuration > Integrations > HaloPSA API.
  2. Expand API details and copy the Resource server URL, Authorization Server URL, and Tenant Name.

Before proceeding, confirm you have all five values: Client ID, Client Secret, Resource Server URL, Authorization Server URL, and Tenant Name.

Lifecycle Insights configuration

  1. Log into Lifecycle Insights via app.scalepad.com and open the Lifecycle Insights icon.
  2. From the left navigation panel, click Integrations under Administration, then Halo.
  3. Check Halo Integration Active.
  4. Fill in the Resource Server URL, Authorization Server URL, Tenant Name, Client ID, and Client Secret gathered earlier.
  5. Click Test Settings — you should see Connection Successful.
  6. Click Save Settings.

Once saved, Lifecycle Insights immediately begins the initial sync process.

Note

The initial data sync can take up to an hour. This delay only applies to the initial sync, and you'll receive an email notification once it's complete.

Once complete, HaloPSA is successfully integrated with Lifecycle Insights.

← Back to index