Hudu integrates with the tools you already use, turning it into your team’s central information hub.
Integrations connect Hudu with third-party applications, creating a secure communication channel that syncs data and enhances your overall experience.
Types of Integrations
There are three main types of integrations:
-
Native Integrations
Built by Hudu. These automatically resync every three hours and can also be re-synced manually at the integration or card level. -
Third-Party Tools
External tools that push data between applications, including alerting integrations and authentication methods. -
Partner-Built Integrations
Integrations built by third-party applications (not by Hudu). Some are listed in the Partner-built section of Admin → Integrations, where you can create and delete the Hudu API key each one uses without leaving the page. Others are set up in the partner's platform using a Hudu API key created in Admin → API Keys.
Native integrations automatically resync every three hours; but integrations can be resynced manually, both at an integration level (via the re-sync button) or at an individual card level.
Enabling Integrations
Integrations can be enabled during testing or in production and can be merged into existing documentation at any time.
To enable an integration:
- Navigate to Admin Area → Integrations.
- Select the integration you want to configure.
- For native integrations, follow the setup guide for that integration.
- Enter the required API or connection details.
- Test the connection.
- Run the first sync to bring in companies from the integration.
- Match companies to existing Hudu companies or create new ones. See Matching Companies below.
- Sync again to import data for the matched companies.
Matching Companies
Before integration data can be imported, companies must be matched to existing or newly created Hudu companies.
When an integration runs successfully for the first time, it pulls in companies from the integration so they can be matched.
To match companies:
- Go to Admin Area → Integrations and select your integration.
- Open the integration's company matching list. The setup guide for each integration shows where to find it.
- For each company, choose to:
- Match it to an existing Hudu company
- Create a new Hudu company with Match new company. A confirmation window appears first, so you can confirm or cancel before the company is created.
- Leave it unmatched (no data will be imported)
- Your search and filters stay in place after you accept or change a match, so you can keep working through the list.
- Re-run the integration to import data for matched companies.
If your account uses a different name for companies (for example, Clients), the Match new company option uses that name instead.
Default Asset Layouts
Default asset layouts act as a holding area for imported data that hasn’t been assigned elsewhere.
Most integrations require default layouts for items such as contacts, configurations, devices, or locations. The required layouts depend on the integration.
You will need to first create these Asset layouts in Admin > Asset Layouts for them to be available in the dropdown selector.
Sort Rules
Sort rules determine where imported data is placed within Hudu.
- Assign integration data types to specific asset layouts.
- Any data type without a sort rule is placed in the default asset layout.
- Asset layouts can be created in advance (Admin Area → Asset Layouts) or created during setup.
After updating sort rules, save your settings and restart the integration sync.
Cards: How Integration Data Is Stored
Hudu stores integration data using cards.
- Cards allow data from external sources to be stored, moved, and stacked under a single asset.
- Cards live inside customizable asset layouts within each client.
- A card can contain data from only one source (manual, CSV import, or integration).
- Multiple cards with the same company and asset name are stacked together.
- When matching integration data to existing assets, serial numbers and MAC addresses match regardless of capitalization or separators (such as dashes or colons), so the same device isn't duplicated.
- If a card is attached to the wrong asset, Admins and Editors can use the Move button on the card to re-match it to a different asset.
Visit The "Card" to learn more!
Some data points on integration cards can now be mapped to custom fields. For more information, please see our article on Connected Fields.
Troubleshooting Integrations
If an integration sync appears to be stuck, the Sidekiq queue may be backed up and need to be cleared.
To check Sidekiq, log in to your Hudu instance as an administrator and navigate to:yourhuduinstance/sidekiq
From there, you can:
- Stop any running processes
- Delete dead jobs
- Clear queued jobs
If you need assistance, please send screenshots of your Sidekiq pages to our support team at support@hudu.com.
Deletion Functionality
⚠️ Danger Section
Actions in this section can cause permanent data loss. Proceed with caution.
Only available for integrations that pull agreements and contracts.
Using this function will delete all agreements and contracts that may be being pulled in from ALL integrations. ONLY use this function if you'd like to remove these completely.
Only available for integrations that pull configurations.
Using this function will delete all configurations that may be being pulled in from the integration. ONLY use this function if you'd like to remove these completely.
Using this function will delete all integration cards that may be being pulled in from the integration.
- This will not affect alternate information that may have been added to an asset created by the integration or pulled in from another integration.
- The integration cards that are deleted will show up on subsequent re-syncs with the integration unless functionality is further removed or integration is fully deleted.
Using this function will delete all assets that may be being pulled in from the integration.
- If an asset was created inside of Hudu from this integration, utilizing this feature will delete ALL information on the asset, including any additional information that was manually input or pulled from another integration on the asset at a later date.
Using this function will delete ALL assets and integration data that may be pulled in from the integration; as well as stop any subsequent re-syncs from bringing these assets in again.
- If an asset was created inside of Hudu from this integration, utilizing this feature will delete ALL information on the asset, including any additional information that was manually input or pulled from another integration on the asset at a later date.
Native Integrations
PSA/RMM
To set up integrations with our supported PSA or RMM integrations, please refer to the guides below!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Productivity
To set up integrations with one of our supported productivity integrations, please refer to the guides below!
|
|
|
|
|
|
|
|
|
|
|
|
Monitoring
To set up integrations with one of our supported monitoring integrations, please refer to the guides below!
Partner-Built Integrations
These integrations are built and maintained by our partners. Some are set up from the Partner-built section of Admin → Integrations; the rest are set up in the partner's platform using a Hudu API key from Admin → API Keys. Refer to the guides below for setup steps!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Third-Party Tools
Authentication
To set up SAML SSO using common identity providers, please refer to their respective guides below!
Alerting
To set up WebHook alerts to common messaging providers, please refer to the guides below!