Disconnected operational tools create duplicate work, inconsistent documentation, and fragmented workflows for MSP teams.

Liongard helps centralize operational workflows by connecting your PSA, documentation platform, and asset intelligence into a more unified system. Whether your team uses HaloPSA, Hudu, IT Glue, or a combination of platforms, the way those systems are connected directly impacts technician workflows, documentation quality, reporting visibility, and operational overhead.

This guide walks through several integration architectures MSPs commonly use with Liongard, including the tradeoffs, operational considerations, and best practices for each approach. By choosing the right integration strategy for your environment, your team can reduce operational silos, improve documentation consistency, streamline ticket workflows, and maintain cleaner system data across platforms.

Before you choose a setup, be clear on how your team actually works day to day.

Ask yourself these questions:

These answers determine how much data flows into your documentation tool, how complex your setup becomes, and how much ongoing maintenance your team takes on.

This is the recommended starting point. Liongard detects changes across your environments and sends alerts and asset data into HaloPSA. From there, your documentation tool pulls company and asset data from HaloPSA.

HaloPSA stays at the center of your workflow. Tickets are created there, and it remains your system of record for service delivery. Your documentation tool acts as the reference layer your team uses while working tickets.

You won’t get the full depth of Liongard inspection data in your documentation tool with this setup. It only reflects what flows through HaloPSA. The benefit is a simpler integration with fewer moving parts and a lower risk of duplicate or conflicting records.

In this setup, HaloPSA still handles ticketing and company data, but Liongard sends asset and configuration data directly to IT Glue through its native integration.

That means IT Glue receives full inspection data from Liongard instead of a filtered version from HaloPSA. This can make documentation more detailed and useful, especially for teams working directly in IT Glue.

The tradeoff is added complexity. You’re managing more connections, and if other integrations are in place, there’s a risk of duplicate configuration records that need to be managed.

With this approach, HaloPSA continues to handle ticketing and company data, while Hudu pulls asset and inspection data directly from Liongard using its API.

Because Hudu pulls directly from Liongard, it can access deeper inspection data than what flows through HaloPSA. This gives you more detailed visibility inside Hudu.

This setup introduces additional coordination. If Hudu is also syncing from HaloPSA, you may end up with overlapping or duplicate records that need to be managed.

Hudu can also be configured to pull data directly from Liongard without using HaloPSA for documentation. This configuration is handled entirely within Hudu.

Liongard connects to HaloPSA using a Client ID and Secret. You need to create a dedicated API user and application in HaloPSA before configuring anything in Liongard.

Customer environments in Liongard need to be linked to the corresponding company records in HaloPSA. This tells Liongard where to send tickets when alerts fire for a given customer.

Best practice: Choose one source for your client list

If HaloPSA is where you manage your client relationships, import companies from HaloPSA. If you’re also using IT Glue, stick with whichever platform you treat as your source of truth.

Pulling from more than one system can create mismatches, so it’s best to choose one and stay consistent.

This is the alerting engine. Liongard detects a change, fires an alert, and routes it to HaloPSA as a ticket. The flow works through three tabs in Liongard under Admin > Actionable Alerts.

Alerting Flow Reference

Rule fires > assigned to Template > Template has HaloPSA as destination > ticket created in HaloPSA for the linked customer environment.

From this point forward, Liongard is detecting changes across customer environments and routing actionable tickets directly into your HaloPSA service queue. No manual ticket creation. No missed changes. Your team works the alerts in the tool they already use.

The Hudu > HaloPSA integration is configured inside Hudu, not in HaloPSA. Hudu pulls company and asset data from HaloPSA and surfaces it inside your Hudu client spaces.

Note: Hudu KB Sync to HaloPSA

Hudu 2.40+ includes a KB sync feature that pushes Hudu knowledge base articles into HaloPSA as FAQ lists. If you plan to use this, update your HaloPSA API credentials in both platforms to include the proper KB scopes before enabling it. This is a bonus workflow, not required for the core asset documentation flow.

For partners using IT Glue as their documentation platform alongside HaloPSA, the integration architecture is slightly different.

HaloPSA handles company import and ticketing. IT Glue receives asset documentation directly from Liongard via Liongard's native integration, not through HaloPSA.

Complete Steps 1 through 4 from Path A above. HaloPSA is still your PSA, your company import source, and your ticketing destination for Liongard alerts. No changes to that setup.

IT Glue Enterprise is required for this integration.

Note: Company import source

If HaloPSA is already your source of truth, import and map your clients from HaloPSA first. Then use the Map tab in the IT Glue integration to link those same Liongard environments to the matching IT Glue organizations. There’s no need to re-import.

This is how Liongard pushes inspection data into IT Glue. Each inspector type maps to a Flexible Asset Type in IT Glue. All of Liongard's assets end in (auto) so they will not overwrite any existing documentation.

IT Glue Pro Sync is a newer, generally available feature that pushes Liongard inspector data directly into IT Glue’s Core Configurations instead of Flexible Assets. This allows you to manage Liongard data within IT Glue’s native asset management structure.

Note: Pro Sync and Flexible Assets can coexist.

Enabling Pro Sync does not remove or affect your existing Flexible Assets. They are two separate integrations that can run simultaneously. If existing IT Glue configuration records match an asset in Liongard by name, Pro Sync will update/overwrite the existing record.

Once both Flexible Assets and Pro Sync are enabled, your IT Glue instance is continuously updated by Liongard inspection data without any manual documentation effort. Configuration changes are tracked in Liongard and surfaced in IT Glue automatically.

This setup allows Hudu to pull asset and inspection data directly from Liongard using its API, rather than relying on HaloPSA.

Liongard still sends alerts and tickets to HaloPSA, so your service workflow stays the same. Documentation data, however, is handled inside Hudu through its direct integration with Liongard.

This integration is configured entirely within Hudu, not in Liongard. Because of that, setup and sync behavior are managed on the Hudu side.

If you also sync data from HaloPSA into Hudu, you are creating multiple data paths into the same system. That requires clear decisions around how assets are matched and which source is authoritative to avoid duplicate or overlapping records.

Once everything is connected, the next step is using the data the right way. These are the workflows MSPs use to keep data clean, reduce manual work, and get more out of Liongard.

Hudu’s native integration creates read-only integration cards that are separate from the asset’s own editable fields. Dynamic, frequently changing data (disk utilization, last logged-in user, certificate expirations, license counts) should not be relied on in Hudu as a live display surface. Cards reflect the last sync, not the current state.

The recommended approach is to split responsibility by data type:

What is Visual Insights?

Visual Insights is Liongard’s dashboard and reporting layer. It surfaces Liongard metric data in configurable, shareable dashboards — giving technicians and account managers a live view of customer environments without navigating individual inspector records. Use it for any data that changes frequently and needs to be monitored rather than documented.

When a technician needs to check disk health, confirm last login on a machine, or verify MFA is enforced across an M365 tenant, the answer is a Visual Insights dashboard - not a Hudu card. Hudu holds the stable knowledge layer; Visual Insights handles the dynamic operations layer.

This eliminates card clutter in Hudu and gives technicians a purpose-built display surface for dynamic data. Visual Insights dashboards can be scoped per customer, filtered by inspector type, and shared with stakeholders - more useful than surfacing the same data through read-only integration cards in a documentation tool.

If your RMM is not reliably bridging user-to-device relationships into HaloPSA, Liongard’s Windows Endpoint Inspector can fill that gap. It captures the last logged-in user for each inspected Windows endpoint.

Liongard’s M365 and Google Workspace inspectors count active licensed users per tenant. Use Liongard Reports or a Visual Insights dashboard to compare active user counts against recurring service quantities in HaloPSA during your billing review cycle. Any discrepancy between Liongard’s count and HaloPSA’s billed quantity is an upsell or reconciliation item.

For clients running Google Workspace — particularly in education environments where account sprawl is common — Liongard can identify and alert on inactive accounts automatically.

Note: Custom Metric Building

Custom metrics in Liongard use JPath/Base64 expressions to query inspector data. Reach out to your Liongard Solutions Engineer if you need help building a specific metric for any of these use cases.