Liongard

What You'll Need

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

Integration Features

• Systems
  • Bring in your inspector types directly from Liongard; choose to create new asset layouts per inspector OR seamlessly merge them into your existing documentation.

What Hudu needs from Liongard

• Liongard Domain.
• Access Key ID.
• Access Key Secret.

Obtaining the Liongard Information

• Navigate to your Liongard instance >> click your name >> Account Settings.

• From here, you can obtain both of the required keys (access key ID and access key secret).
• Click Access Tokens on the left-hand menu. Click Generate New Token >> select Liongard API token from the list.
• Optionally select an expiration for the token and click Generate.

• Copy the Access Key ID and Access Key secret and paste them into Hudu exactly, in the Liongard integration setup settings.
• To obtain your Liongard domain URL; navigate to the My Liongard Instance tab >> URL.
  • This should be in the format: xxx.app.liongard.com

Enabling the Liongard 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 Liongard integration:

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

  • Select Liongard from the list.

Setting up the Integration in Hudu

Step 1. Connect to Liongard

• Enter the following information:
  • Liongard Domain
  • Access Key ID
  • Access Key Secret
• Select any additional options:
  • Auto-update names of Assets - If name is changed in Liongard, 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 Liongard

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 Liongard environments.

Step 3. Match Liongard Environments

• Before Environments from Liongard 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 Liongard are imported

  • They appear in the Matched Companies List for the integration

• Navigate to Hudu Admin → Integrations → Liongard

• 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 Liongard company

  • 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

Step 4. Choose where Liongard data will fill to

• Select Default Asset Layout

  • Choose an asset layout (must be active asset layout) from the list to designate as the default asset layout.

  • This asset layout will store information that is pulled in but not explicitly mapped to another asset layout.

• The Liongard integration requires one default asset layouts for:

  • Systems

• Add Sort Rules

  • Sort Rules determine how data types from Liongard 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.

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

FAQ