Skip to main content
Triggr works with Halo clients, users, tickets, ticket actions, sites, assets and recurring invoices.

​
Set up HaloPSA

1

Create an agent for Triggr

In Configuration > Teams & Agents > Agents, create an agent such as Triggr API with access to every client and team your workflows use. Triggr can only see and change what this agent can.
2

Create an API application

In Configuration > Integrations > Halo API, click View Applications, then New:
  • Authentication Method: Client ID and Secret (Services)
  • Login Type: Agent, with Agent to log in as set to your Triggr agent
  • Permissions tab: tick all
Save it, then copy the Client ID and Client Secret. You may not see the secret again.
3

Find your Halo address

API Details on the Halo API page shows your Resource Server, such as https://yourcompany.halopsa.com/api. Your Halo address is that URL without /api.
See Halo’s guide to creating API applications.

​
Connect it in Triggr

1

Open the integration

Go to Integrations > HaloPSA and click Configure on the Base Configuration card.
The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button.
2

Enter your Halo details

Enter your Halo address as BaseURL, plus the ClientID and ClientSecret. Leave TenantID blank, then click Save Configuration.
The HaloPSA configuration window with BaseURL, ClientID, ClientSecret and TenantID fields, an Allow insecure TLS switch under Advanced, and a Save Configuration button.
Ticket steps run against the PSA set as Default PSA: in Triggr Core, Settings > General; in Studio, Settings > Org Variables > Setup Wizard. See Connect your PSA.
The Setup Wizard's Preferred PSA question with cards for Halo PSA, ConnectWise PSA, Syncro PSA, Autotask by Datto and Other.

​
Map your clients

On the Client Mapping card, click Apply 100% Matches, then choose the Halo client in Mapped to for anyone left. Triggr saves each match as the client’s haloId variable.
The Client Mapping card with All, Mapped and Unmapped filters, Acme Corp mapped to Acme Corp with a 75% suggested mapping, and Globex unmapped with a Select ConnectWise Manage clients dropdown.

The Client Mapping card, shown here for ConnectWise Manage.

​
Troubleshooting

BaseURL must start with https:// and not end in /api or /. In Halo, check the application is enabled, uses Client ID and Secret (Services) and has the all permission, then re-copy the Client ID and Client Secret.
A Create Ticket step ran for a client with no haloId. Map the client on the Client Mapping card, or set the step’s Client ID to the client’s haloId variable.
The Triggr agent can’t see them. Give it access in Halo, then click Refresh on Client Mapping.
Give the Triggr agent the permission or team access the action needs.
Triggr needs a public address with a certificate from a trusted authority. Publish Halo there and allow Triggr’s IP addresses through your firewall.