> For the complete documentation index, see [llms.txt](https://docs.incidenthub.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.incidenthub.cloud/incidenthub-documentation/channels/integration-for-halopsa.md).

# Integration for HaloPSA

How to integrate HaloPSA with IncidentHub to receive vendor outage notifications

*This integration is in Beta*

You can integrate IncidentHub with HaloPSA to receive vendor outage notifications as tickets.

IncidentHub will create tickets in your HaloPSA instance when any of the following happens:

1. An incident is triggered (started).

IncidentHub does not send follow up notifications to HaloPSA for the same incident, including for updates and resolved events. It also does not send upcoming maintenance reminders to HaloPSA.

## In Your HaloPSA Account

1. Login to your HaloPSA account and click on Configuration in the left sidebar.
2. Click on Integrations -> Halo API - Applications to view your current list of applications.
3. Create a new application by clicking on New on the top right.
   1. Add a name and a description.
   2. Choose "Authentication Method" as Client ID and Secret (Services).
   3. Note down the Client ID and Client Secret (you will need them in subsequent steps).
   4. Choose Login Type as Agent and the name of the agent to login as. The tickets will be logged as coming from this Agent.
   5. Click on the Permissions tab and set the following permissions. These permissions are required to create tickets.
      1. read:tickets
      2. edit:tickets
   6. Click Save

<figure><img src="https://1097519083-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1UERJeGV9Jx1B0oddXCx%2Fuploads%2FWu0IHjFZ5n8c1up8eozf%2FScreenshot%202026-11-16%20at%2014-18-22%20Configuration%20Integrations%20Halo%20API%20Applications.png?alt=media&amp;token=9df95dd9-d559-4c96-9373-18155cfdfcfa" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1097519083-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1UERJeGV9Jx1B0oddXCx%2Fuploads%2Fvucsz2QDsIdTwBUYdhvM%2FScreenshot%202026-11-16%20at%2014-18-40%20Configuration%20Integrations%20Halo%20API%20Applications.png?alt=media&amp;token=ed3d66cf-2e74-4cc5-a32e-5919f6f5612d" alt=""><figcaption></figcaption></figure>

## In Your IncidentHub Account

1. Login to your IncidentHub account and click on Channels -> Add -> HaloPSA.
2. Add a Name and and a Description.
3. Enter the following details to connect to your HaloPSA instance:
   1. Halo base URL : E.g. \`<https://incidenthub.halopsa.com\\`>
   2. Halo auth URL : E.g. \`<https://incidenthub.halopsa.com/auth/token\\`>
   3. Halo Client ID : Noted down in the previous step
   4. Client Secret : Noted down in the previous step
   5. Halo tenant (optional) : Leave this blank if your auth URL is on your own Halo host. Fill it in if your auth URL is `https://auth.haloservicedesk.com`, which serves multiple Halo instances and needs the tenant to identify yours.
   6. Halo customer id to raise tickets against : The numeric ID of the Halo customer record under which vendor outage tickets get filed, usually your own company or a record you create for this purpose. Open that customer in Halo and copy the number from the address bar. This is not the same as the Client ID in your API application.

<figure><img src="https://1097519083-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1UERJeGV9Jx1B0oddXCx%2Fuploads%2F4fPBNqVUi4CIXyquXZTN%2FScreenshot%202026-11-16%20at%2014-54-29%20IncidentHub.png?alt=media&amp;token=fef89ddc-a0da-4920-8aad-cf6343620054" alt=""><figcaption></figcaption></figure>

4. To ensure that the details are valid and IncidentHub is able to connect to your HaloPSA account,  click on "Create a test ticket". This will create a test support ticket in your HaloPSA instance.
5. Click Save.

## Notification Example

A HaloPSA ticket created by IncidentHub looks like this:

<figure><img src="https://1097519083-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1UERJeGV9Jx1B0oddXCx%2Fuploads%2FGr6b8CDROnGCVKEBBaCa%2FScreenshot%202026-11-16%20at%2012-45-35%20HaloPSA.png?alt=media&amp;token=af24e581-792a-4201-89a6-ad4cb783651c" alt=""><figcaption></figcaption></figure>

## HaloPSA Notifications with Client Information

If you are an MSP, you would have set up [per-client status pages](https://docs.incidenthub.cloud/incidenthub-documentation/per-client-public-status-pages.md) for your clients.&#x20;

During a vendor outage, HaloPSA can automatically include a list of the clients (status page titles) who are affected by that outage when logging the ticket. This lets you notify those clients proactively about the outage, or respond to their queries faster.
