Setting Up HaloPSA Integration

This guide walks you through connecting your HaloPSA instance to Triggr.

Overview

The HaloPSA integration enables Triggr to automate tasks within your PSA, including:

• Managing tickets and service requests
• Asset management and inventory tracking
• Client onboarding automation
• Agent and team management

Prerequisites

Before you begin, ensure you have:

• Admin access to your HaloPSA instance
• Access to Configuration > Integrations in HaloPSA

Step 1: Create an API Agent in HaloPSA

First, create a dedicated agent for the Triggr API integration.

1. In HaloPSA, navigate to Configuration > Teams & Agents > Agents
2. Click to create a new agent
3. Set the Name to Triggr API
4. Assign Administrator permissions for full functionality
5. Save the agent

Step 2: Create an API Application

Next, create an API application that Triggr will use to authenticate.

1. Navigate to Configuration > Advanced > Integrations > HaloPSA API
2. Click View Applications
3. Click to create a new application
4. Set the Name to Triggr
5. Set Authentication Method to Client ID and Secret (Services)
6. Set the Agent to Triggr API (the agent you created in Step 1)
7. Save the application

Step 3: Configure Permissions

Set up the required permissions for the API application.

1. Open the application you just created
2. Go to the Permissions tab
3. Enable the All checkbox to grant full API access
4. Save the permissions

Step 4: Add Agent to Teams

Ensure the API agent has access to all teams.

1. Go to the Departments & Teams tab in the application settings
2. Add the Triggr API agent to all teams that require automation
3. Ensure Allow use of all Customers is set to Yes
4. Save the settings

Step 5: Copy API Credentials

Now copy the credentials you'll need for Triggr.

1. In the application details, locate and copy:
   • Client ID
   • Client Secret
2. Note your HaloPSA URL (e.g., yourcompany.halopsa.com)

Important: Store your Client Secret securely - you may not be able to view it again after leaving this page.

Step 6: Configure in Triggr

With your API credentials ready, configure the integration in Triggr.

1. In Triggr, navigate to Integrations
2. Find and select HaloPSA
3. Click + Configure to the right of the Base Configuration card

4. Enter the following details:
   • Client ID: The Client ID from Step 5
   • Client Secret: The Client Secret from Step 5
   • Resource Server Hostname: Your HaloPSA URL (e.g., yourcompany.halopsa.com)
   • Auth Server Hostname: Your HaloPSA auth URL (e.g., yourcompany.halopsa.com/auth)
   • Is On-Premise: Select if using an on-premise installation
   • Tenant ID: Your tenant ID (for cloud instances)

5. Click Save Configuration

Note: When entering hostnames, remove the https:// prefix and any /api suffix. Just use the base domain.

Troubleshooting

Customers Not Visible

If you can't see all customers in Triggr:

1. Verify Allow use of all Customers is set to Yes in the API application
2. Check that the Triggr API agent has been added to all relevant teams
3. Ensure the agent has Administrator permissions

Missing Boards or Teams

If boards or teams don't appear in configuration:

1. Verify the API application has the All permission enabled
2. Check the agent is assigned to the relevant departments
3. Refresh the integration in Triggr

Authentication Errors

If you receive authentication errors:

1. Verify the Client ID and Client Secret are entered correctly
2. Check the hostname format - it should be yourcompany.halopsa.com without https://
3. For the Auth Server, ensure you've added /auth to the hostname
4. Verify the API application is set to Client ID and Secret (Services) authentication

On-Premise Installations

For on-premise HaloPSA installations:

1. Set Is On-Premise to Yes in Triggr
2. Ensure your HaloPSA server is accessible from Triggr's IP addresses
3. Check firewall rules allow inbound API connections

---

Need help? Contact your account manager - we're happy to help configure this integration with you.