HaloPSA

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

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

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

Optionally name imported assets using a Halo custom field instead of the Halo inventory number. See Step 5. Customize asset names below.

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

Sync sites and locations from HaloPSA.

Sync Central and company-specific Knowledge Base articles from Hudu into the HaloPSA Knowledge Base.

• 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

• Open the Permissions tab and enable:
  • read:customers
  • read:assets

• Select a Login Type and assign an Agent
  • A dedicated integration user is strongly recommended to prevent permission or auditing issues

• 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

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

• read:kb
• edit:kb

The assigned Agent's Role and your Halo Knowledge Base configuration also need additional settings.

• 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

• 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

• On the integration overview page, click Test Connection
• If successful, start an initial sync to bring in 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

• 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

By default, assets imported from Halo are named using their Halo inventory number. You can choose a Halo custom field to use as the asset name instead, set individually for each asset type.

• For each asset type listed, select the Halo custom field to use as the asset name in Hudu.
• The custom field must be a key field in Halo. Fields that are not key fields will not be available to select.
• If no custom field is selected for an asset type, the Halo inventory number is used as the asset name.
• Save the settings. Asset names update on the next sync.

If you'd like to sync Knowledge Base articles from Hudu to HaloPSA, this step lets you turn that on as part of the integration setup. You can also control how synced articles are attributed to Hudu inside Halo.

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

Answer: Native integrations 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.

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.

Answer: When no custom field is selected for an asset type, Hudu uses the Halo inventory number as the asset name. To change this, open Admin → Integrations → HaloPSA, select a Halo key field for that asset type under Customize asset names, and save. Asset names update on the next sync.

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 integration's settings page or by clicking the re-sync button in the top right.