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:
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. Only published articles sync; draft and archived articles are not sent to HaloPSA.
Visit HaloPSA Knowledge Base Sync for additional information on syncing Knowledge Base articles to Halo.
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, including Halo custom fields, into Hudu custom fields. This allows data to appear in list views and be fully searchable across your account. For more information, visit Connected Fields and Connecting Halo Custom Fields to Hudu Connected Fields.
What Hudu needs from HaloPSA
- Resource Server
- Tenant
- Client ID
- Client Secret
Creating an API Application and Setting up HaloPSA Permissions
- 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:customersread: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:kbedit:kb
The assigned Agent's Role and your Halo Knowledge Base configuration also need additional settings.
Visit HaloPSA Knowledge Base Sync for additional information on required permissions and setup.
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.
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.
The HaloPSA integration page shows the integration's status and sync totals at the top, with four tabs below: Cards, Settings, Logs, and Deletion Options. Setup is done on the Settings tab. Test Connection, Sync Now, and Pause Integration are in the top right of the page.
Setting up the Integration in Hudu
Each section of the Settings tab saves separately, so save each section before moving on to the next.
In the Halo Credentials section:
- Enter the Resource Server
- Do not include a trailing
/in server URLs.
- Do not include a trailing
- Enter the Tenant
- Leave Tenant blank for self-hosted Halo
- Enter the Client ID
- Enter the Client Secret
- After the secret is saved, it's hidden. Click the edit icon next to the field to change it.
- Click Save Credentials
- Click Test Connection in the top right of the page
In the Options section, select any of the following:
- 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
Under Skip the following, select anything you don't want to bring into Hudu:
- Inactive accounts
- Contacts
- Sites
- Assets
Click Save Options.
When matching assets on serial number, Hudu ignores capitalization and separators such as dashes or colons, so existing assets aren't duplicated.
Before data from Halo can be brought into Hudu, each Halo client must be matched to an existing Hudu company or to a new company created from the Halo client. Hudu recommends matching one client first for testing to ensure data imports correctly.
In the Companies section:
- The Unmatched tab lists Halo clients that aren't matched yet. Matched clients move to the Matched tab.
- Use the filters to narrow the list: All match types, Suggested matches, or No suggested matches. You can also search by name.
- Hudu suggests a match for each client where it finds one. Accept the suggestion, choose a different Hudu company, or use Match new company to create a new company in Hudu. A confirmation window appears first, so you can confirm or cancel before the company is created.
- To handle every client at once, click Accept/Create for All
- Leave a client unmatched if you don't want it or its data imported
- Your search and filters stay in place after you accept or change a match, so you can keep working through the list
- After matching, click Sync Now to import data for the matched companies
Visit Understanding Integrations for additional information on company matching.
In the Asset Layouts section:
- Select the default asset layouts. The HaloPSA integration requires three default asset layouts:
- Users
- Sites
- Assets
- Default asset layouts store information that is pulled in but not mapped to another asset layout by a sort rule
- Add Sort Rules to control which asset layout each Halo asset type is placed in. Asset types without a sort rule go to the default Assets layout.
- Asset layouts must be Active to be selected. You can create them ahead of time in Admin → Asset Layouts.
Visit Asset Layouts for additional information on creating asset layouts.
By default, Hudu uses each asset's Halo inventory number as its name. You can choose a different Halo asset key field to use as the name, set individually for each asset type.
In the Custom Asset Names section:
- Click Add Asset Name Rule
- Select the asset type and the Halo key field to use as its name. Only key fields in Halo are available to select.
- Repeat for any other asset types
- Click Save Asset Rules. Asset names update on the next sync.
Asset types without a rule keep using the Halo inventory number as their name.
Choose a field your team already uses to identify devices, such as a hostname or device name field, so assets are easy to find when searching Hudu.
To bring other Halo custom field values into Hudu asset fields, visit Connecting Halo Custom Fields to Hudu Connected Fields.
The Hudu to Halo Knowledge Base Sync section lets you sync your Central KB and company KBs from Hudu to HaloPSA. From here you can set Halo access control for synced articles, choose how articles are attributed to Hudu inside Halo, and select which KBs to sync.
Visit HaloPSA Knowledge Base Sync for additional information on setup, required permissions, and Hudu attribution options.
FAQ
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 key field is selected for an asset type, Hudu uses the Halo inventory number as the asset name. To change this, open Admin → Integrations → HaloPSA, add an asset name rule for that asset type in the Custom Asset Names section of the Settings tab, and click Save Asset Rules. Asset names update on the next sync.
Answer: Admins and Editors can use the Move button on the integration card to rematch it to a different asset.
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.