Evo now integrates with Halo PSA to help streamline customer and license management.

The Evo integration with Halo PSA simplifies synchronization between the two platforms — allowing you to import customers, align licensing data, and automate updates between Evo and Halo PSA. Companies can define unit costs and pricing for each license type, which are automatically created and updated within Halo PSA under the configured contracts.

With Evo and Halo PSA, you can:

Note: There is a new permission needed for roles to be able to manage the PSA integrations. Under Role-Based Permissions (On the Home Tab, select Access and Role-Based Permissions). The option to select for the appropriate role is "Manage PSA Integrations"

You can find the integration by navigating to Integrations on the Left side of your Evo Portal and selecting PSA and then HaloPSA

To configure the PSA integration, you'll need to create a new Client ID and API key ( Secret ) for Evo to integrate with HaloPSA.

Note: An application with these privileges is required to perform this configuration correctly.

To Create API Credentials on Halo PSA, you will need to click “Configuration” on the home Page

Once in here you would then Click on “Integrations”

From here you will then click on “HaloPSA API”

Then once you are on the “HaloPSA API” Page, there will be a button that says “View Applications”. After clicking into View applications you will click “+New”

After clicking into View applications you will click “+New” at the top right

When creating an application, the Authentication Method should be "Client ID and Secret" This will generate the Client ID and Secret needed when configuring the integration with Evo. You will also need to set a name and an agent to login as

Retrieving the Base URI

Lastly, you will need to locate your Base URI, which can be found on the Halo PSA API page. This page displays both your Resource Server URL and Authorization Server URL.

For the Evo integration setup, use the base portion of either URL — omitting the suffix:

This resulting value is your Base URI, which will be entered in the Evo Portal during integration setup.

At this stage, you’ve gathered all the required details to configure and finalize the Halo PSA integration in the Evo Portal.

After entering the three required values obtained from Halo PSA, click Create to complete the integration setup. Once the integration has been created, you can proceed to configure synchronization settings for Companies, Billing, and Tickets within the Evo Portal

Recurring Products (Item Group Configuration)

When the HaloPSA integration is first created, Evo licenses are automatically created as items within Halo. In order for these licenses to properly link to contracts and invoices, they must be assigned to an Item Group with a Group Type of Recurring Products.

Verifying or Creating the Recurring Products Item Group

This step is required for Evo licenses to be billable through HaloPSA.

As part of the HaloPSA integration, Evo automatically imports and links contracts (referred to as Agreements in Halo) to their corresponding companies. However, Evo licenses can only be billed when they are associated with a Recurring Invoice, which must be linked to the relevant agreement.

If a linked agreement does not have a recurring invoice, a warning will appear on the Integrations page stating:

When this warning is present, billing for the affected company or contract will be disabled until a recurring invoice is created.

Creating a Recurring Invoice

Once the recurring invoice is in place, Evo license billing will be enabled for the associated company and contract.

To enable ticket creation and automated workflows with the HaloPSA integration, several required ticket fields must be configured within HaloPSA. These fields are synchronized into the Evo portal and are used when defining ticket automation rules, including automatic ticket creation and closure.

The required ticket fields are:

Impact and Urgency values are managed within HaloPSA’s Lookup Codes and must exist prior to enabling ticketing automation.

Verifying Impact and Urgency Levels

These values will be automatically synced and made available in the Evo portal for ticket configuration.

Ticket Categories and Types are configured under HaloPSA’s ticket settings and are also required for automated ticket handling.

Verifying Ticket Types

Verifying Ticket Categories (Category 1)

The Evo integration uses Category 1 values for ticket categorization.

These Category 1 values will be synchronized into the Evo portal and used for ticket classification during automated ticket creation.

Once all required ticket fields are configured in HaloPSA, they will be available within the Evo portal for ticket automation and workflow setup.