HaloPSA

The HaloPSA integration with Hudu allows you to bring core client information, assets, and related data directly into Hudu—helping you centralize everything in one place for easier management and visibility.
Before setting up your HaloPSA integration, read our Understanding Integrations article to learn basic concepts and useful tips.

What You'll Need

  • Access to retrieve HaloPSA API credentials.
  • Admin or super-admin user role within Hudu.

    At any time, you can come back to your Hudu admin area >> Integrations >> HaloPSA to make changes to the integration.

Integration Features

Hudu’s integration with HaloPSA allows you to sync:

  • Companies into Hudu

    • Create client spaces in Hudu directly from HaloPSA companies, or merge them into existing client spaces.

  • Users into Hudu

    • Pull users from HaloPSA and organize them into an asset layout of your choice (for example: People, Contacts, or Company A Employees).

  • Assets into Hudu

    • Sync asset information from HaloPSA and sort it into asset layouts based on configured sort rules and primary sync locations.

  • Contracts into Hudu

    • Import active contracts to provide visibility within client spaces in Hudu.

  • Sites into Hudu

    • Sync sites and locations from HaloPSA.

  • Central and Company KB articles into HaloPSA

    Use our Hudu Assist browser extension feature to bring the power of the Hudu interface into the tools your team is already using. For more information, visit our Hudu Assist article!

You can use Connected Fields to map information from this integration into Hudu custom fields. This allows data to appear in list views and be fully searchable across your account. Learn more →

What Hudu needs from HaloPSA

  • Resource Server
  • Tenant
  • Client ID
  • Client Secret

Creating an API Application and Setting up HaloPSA Permissions

API Application Setup
  • In HaloPSA, navigate to:
    Configuration → Integrations → HaloPSA API
  • Select View Applications, then choose Create New Application
  • Enter a name for the application and ensure it is set to Active
  • Under Authentication Method, select Client ID and Secret
  • Generate the credentials and store the Client ID and Client Secret securely
API Permissions
  • Open the Permissions tab and enable:
    • read:customers
    • read:assets
Halo KB Sync Permissions

If using Knowledge Base sync, additional permissions are required. For more information, visit our Halo PSA Knowledge Base Sync article.

Agent and Login Type
  • Select a Login Type and assign an Agent
    • A dedicated integration user is strongly recommended to prevent permission or auditing issues
Agent Role Requirements
  • Ensure the assigned Agent:
    • Has visibility to all required clients (missing client access is a common cause of sync failures)
    • Has a Role with at minimum:
      • Client Access: Read
      • Asset Access: Read
      • User Access: Read
Using Knowledge Base Sync?

If you plan to sync Knowledge Base articles from Hudu to HaloPSA, additional API permissions are required.

  • read:kb
  • edit:kb

For full setup instructions, see: Halo PSA Knowledge Base Sync → 

Linking Back to Hudu from Halo

Halo can create direct links back to Hudu records. This allows technicians to quickly open related Hudu documentation directly from within Halo, reducing context switching and making it easier to access passwords, procedures, and other stored information.

linkingbacktohudu.png

Enabling the HaloPSA Integration

  • Integrations can be enabled at any time, during Hudu environment testing or in production.

  • Once enabled, integrations can be merged into existing documentation based on predefined rules.

  • This allows you to configure the integration upfront or connect it later as needed.

  • To enable the HaloPSA integration:

    • Navigate to the Hudu admin area (Admin → Integrations).

    • Select HaloPSA from the list.

Setting up the Integration in Hudu

Step 1. Connect to Halo
  • Enter the resource server
    • Do not include a trailing / in server URLs.
  • Enter the tenant
    • Leave Tenant blank for self-hosted Halo
  • Enter the client ID
  • Enter the client secret 
  • Select Default Asset Layouts
    • Choose asset layouts (must be active asset layouts) from the list to designate as the default asset layouts
    • The default asset layouts store information that is pulled in but not explicitly mapped to another asset layout via sort rules
    • The HaloPSA integration requires three default asset layouts:
      • Users
      • Sites
      • Assets
halo_default.png

    If you don't see/have not created any asset layouts yet, you’ll need to create these. Visit Asset layouts for additional information!

  • Select any asset types to skip (optional)
  • Select any additional options:
    • Auto-update names of Assets - If name is changed in Halo, the name will automatically be updated in Hudu
    • Do not update basic company details - This will prevent the company details from being changed in Hudu if they are changed in Halo
    • Do not match assets on primary serial - This will prevent assets from matching on primary serial; instead a new asset will be created for each serial number
  • Save the settings
Step 2. Test connection and run an initial sync
  • On the integration overview page, click Test Connection
  • If successful, start an initial sync to bring in Halo clients

    Make sure to test the integration for a successful connection before continuing; do not continue on until you see a connection successful message display.

Step 3. Match Halo Clients
  • Before clients from Halo can be brought into Hudu, they must be matched to:
    • Existing companies in Hudu, or
    • New companies you create in Hudu
  • Hudu recommends matching one client first for testing to ensure data imports correctly
  • When the integration runs successfully for the first time:
    • Clients from Halo are imported
    • They appear in the Matched Companies List for the integration
  • Navigate to Hudu Admin → Integrations → Halo
  • Open the integration and click Match Companies
  • Review the list of companies and choose one of the following options:
    • Bulk create and/or match all companies
    • Match a company to an existing Hudu company
    • Create a new matched company in Hudu from a Halo client
    • Leave a company unmatched (it and its data will not be imported)
  • After matching companies, re-run the integration import to populate data for the matched or newly created companies

syncro_matched_companies.png

Step 4. Choose where Halo assets will fill to
  • Add Sort Rules
    • Sort Rules determine how data types from Halo are mapped to asset layouts in Hudu
    • They let you define specific rules that control where each asset type is placed
    • Any asset types imported without an assigned Sort Rule will automatically be placed into the default asset layout
    • Asset layouts used for Sort Rules can be created ahead of time in the Hudu admin area (Admin → Asset Layouts) and must be marked as Active
    • You can also create new asset layouts directly from this section if needed.

halo_sort.png

FAQ

Getting "Failed: Undefined" error for the test connection?

Answer: The user assigned to the Hudu/Halo application does not have permissions to view clients within Halo Instance. To fix: Go to Halo instance → Teams & Agents → Agents and find the user that is assigned to the Hudu application. On the "Permissions" tab, ensure that the user has Read Only access (at least) on the field "Client Access Level". Save and retry Test Connection in Hudu.

How often do integrations sync?

Answer: Native integrations will automatically re-sync (update) every 3 hours.
You can also use either the global or the card-specific re-sync features to refresh native integration syncs at any point.

Why is my integration taking a long time to finish?

Answer: If the Halo sync has been loading for a significant amount of time (it can take up to 10 minutes), follow the steps below:

  •  
    • Test the connection to ensure Hudu and Halo are communicating correctly.
    • Verify your Halo credentials.
    • Refresh the page (while a sync is actively running).
    • Stop the sync and restart the sync.
Accidentally deleted an integration card; how do I get this back?

Answer: It should appear on subsequent re-syncs. If it is still not appearing, ensure that it has not been archived; and still exists in your sort rules.

Notes: Active integrations sync automatically every 3 hours; manual re-syncs can be performed either within an integrations’ settings page or by clicking the top right re-sync button.

 

Related to

Was this article helpful?
0 out of 0 found this helpful