Understanding Integrations

Hudu integrates with the services you already use and love; allowing you to turn Hudu into your teams' personal information hub!
 
Our integrations allow you to seamlessly connect your Hudu environment to 3rd-party applications, providing a "communication channel" between Hudu and your other software; overall creating a more robust and powerful experience while using our product!
 
There are three main types of integrations:
  • Native Integrations that we’ve created, and/or have been created by the integration vendor;
  • 3rd party tools, that push data from one application into another; alerting integrations; and authentication methods.
  • Integrations created by 3rd party applications. This means that we did not create this integration ourselves. To use this option, you’ll need to use your Hudu API information

    Native integrations automatically re-sync every three hours; but integrations can be re-synced manually, both at an integration level (via the re-sync button) or at an individual card level.

 

Guides

Enabling Integrations

Integrations can be enabled at any point during your Hudu environment testing and/or during production. Integrations can be merged into your existing documentation based on set rules; providing the ability to start with integration setup, or easily connect them at a later date. As a general rule, to enable integrations:
 
  • Navigate to your Hudu admin area >> Integrations.
  • Select the integration that you'd like to enable.
    • For native integrations, follow the guide specific to the integration you're attempting to set up.
  • Enter the required API connection information. This will depend on the integration chosen.
  • Test the Integration.
  • Run the integration by clicking Start Sync.
  • Once it has been completed, click on Match Companies.
  • Match companies to existing Hudu companies or create new ones.
  • Re-run the integration.

 

Matching Companies

Before your companies (and their corresponding data) from any integration can be brought into Hudu, they must first be matched to companies that either already exist within your Hudu environment; OR to companies that you create now.
  • The first time your integration connection runs successfully, it will attempt to bring in companies from the integration; these are then added to the Matched Companies List of that integration.
    • Navigate to your Hudu admin area >> Integrations, and look for your integration. Click into it.
    • It should now have a button that says Match Companies.
    • Go through the list of companies and either bulk create/match all OR decide to:
      • Match the company to an existing (already created) client in Hudu;
      • Create a matched client within Hudu from an integration company;
      • Leave unmatched; client (and corresponding data) will not be created/brought into Hudu.
  • Once you have matched your companies, you must re-run the integration import to fill in all the data for the newly matched/created companies.

Match_Companies.png

Primary Sync Location

Primary sync location(s) serve as your "junk drawer" asset layout(s); storing the information that is being pulled in, but not otherwise told where to be placed.
 
Depending on the integration being set up, your primary sync location(s) may be different. Typically, integrations require a primary sync location for contacts and/or assets (configurations, devices, locations, etc.).
 

1.png

 

Sort Rules

Sort rules allow you to select which data types (from the integration) will be mapped into which asset layouts (within Hudu). They allow you to specify certain "rules" for asset types as to where they get placed; any asset types that are brought in, but are not told where to be placed via sort rules, will be placed into the corresponding primary sync location.
 
The asset layouts that you're choosing to sort into can be created beforehand (Hudu admin area >> Asset Layouts; ensure that they're marked active) OR you can create new asset layouts here.
 

Connect_Autotask_-_OrganizedCo.png

  • Save your settings and stop/start your integration sync again to reflect your changes.

 

The "Card"

How Hudu Stores Integration Information

When Hudu pulls in data from external platforms, it uses a concept called a card to allow you to easily store and move this information; "stacking" information from multiple sources under a single, readable asset. These are then stored within customizable asset layouts (categories), inside each of your client spaces.
 
Cards can contain data from numerous different sources; including manual input, import from .csv, or from external sources (API & integrations). But, a single card can only contain data from a single source (manually entered information and imported information are both treated as "custom").
 
Multiple cards, that match based on the company they belong to as well as by asset name, will again be "stacked" under a single asset. If perhaps, a mismatch occurs, however, you can always re-match an integration card to another asset.
 

    Visit The "Card" to learn more!

 

Deletion Functionality

   The Danger Zone: actions taken below can cause permanent data loss. Be careful!

Delete All Agreements/Contracts

    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.

Delete Configuration Types

    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.

Delete All Cards from Integration

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.
Delete All Integration Assets

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.
Delete Integration

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.

 

Guide Links

Native Integrations

PSA/RMM

To set up integrations with our supported PSA or RMM integrations, please refer to the guides below!

halologo.png

HaloPSA

syncrologo.png

SyncroMSP

ninjalogo.png

NinjaOne

CWlogo.png

CW Manage

Autotasklogo.png

Autotask

dattormmlogo.png

DattoRMM

ateralogo.png

Atera

kaseyaBMSlogo.png

Kaseya BMS

repairshopr_logo.png

RepairShopr

pulsewaylogo.png

Pulseway

 

 

n-able_n-sight.png

N-Able N-Sight

 

 

 

PRODUCTIVITY

To set up integrations with one of our supported productivity integrations, please refer to the guides below!

365logo.png

Microsoft 365

quickpasslogo.png

QuickPass

cloudradiallogo.png

CloudRadial

mapboxlogo.png

MapBox

 

dattobackuplogo.png

Datto Backup

unifi_icon.png

Ubiquiti UniFi

 

 

 

MONITORING

To set up integrations with one of our supported monitoring integrations, please refer to the guides below!

domotzlogo.png

Domotz

liongardlogo.png

Liongard

auviklogo.png

Auvik

watchmanlogo.png

Watchman

 

Third-Party Tools

AUTHENTICATION

To set up SAML SSO using common identity providers, please refer to their respective guides below!

googleadminlogo.png

Google Admin Console

azureadlogo.png

AzureAD

jumpcloudlogo.png

JumpCloud

oktalogo.png

Okta

passlylogo.png

AuthAnvil (Passly)

oneloginlogo.png

OneLogin

 

ALERTING

To set up WebHook alerts to common messaging providers, please refer to the guides below!

slacklogo.png

Slack

teamslogo.png

Microsoft Teams

discordlogo.png

Discord

genericwebhook.png

Generic Provider

zapierlogo.png

Zapier

 

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