Skip to main content

HaloPSA Integration

Connect Palisade to HaloPSA to automatically import domains, create tickets, and synchronize billing.

Step 1: Create an API-Only Agent in HaloPSA​

  1. In HaloPSA, navigate to Configuration > Agents.
  2. Click New to create a new agent.
  3. Check the API Agent checkbox to designate this as an API-only agent.
  4. Assign the agent to the appropriate team and department.
  5. Save the agent.

Step 2: Grant Permissions​

Configure the following permissions for the API agent:

Module Permissions:

  • Tickets: Read and Modify
  • Customers: Read Only

Ticket Permissions:

  • Can add new tickets
  • Can view unassigned tickets
  • Can view others' tickets

Step 3: Create an API Application​

  1. Navigate to Configuration > Integrations > HaloPSA API.
  2. Create a new API application.
  3. Note the following details:
    • Server Host -- Your HaloPSA server hostname (see warning below)
    • Client ID
    • Client Secret
  4. Set the authentication method to Client ID and Secret.
  5. Set the agent to log in as to the API agent you created in Step 1.
  6. Configure the application permissions:
    • Read/Edit Tickets
    • Read Customers
warning

Use your base HaloPSA domain as the Server Host. Do not include https:// or /api in the hostname. Do not use custom domains -- use the original HaloPSA-provided domain.

tip

Copy your Client ID and Client Secret immediately after creation. The Client Secret may not be accessible again later.

Step 4: Configure in Palisade​

  1. In Palisade, navigate to the Integrations page.
  2. Select HaloPSA as your PSA.
  3. Enter the following credentials:
    • Server Host -- Your HaloPSA server hostname (without https:// or /api)
    • Client ID -- From the API application
    • Client Secret -- From the API application
  4. Click Connect to establish the connection.
  5. Once connected, configure the integration:
    • Map organizations -- Link your HaloPSA customers to Palisade organizations.
    • Configure ticket type -- Select the ticket type Palisade should use when creating tickets.
    • Configure statuses -- Map Palisade ticket statuses to your HaloPSA status workflow.
    • Configure priorities -- Map Palisade priority levels to your HaloPSA priorities.

Verification Checklist​

After completing the setup, verify the integration is working correctly:

  • Connection status shows as Connected on the Integrations page
  • Customer organizations are mapped correctly
  • A test ticket can be created in HaloPSA from Palisade
  • Ticket statuses update correctly in both directions
  • Domain import pulls the expected client domains