10.20. Hudu IT Documentation Integration: Surface Client Docs, Assets, and Passwords

Your technicians already keep client documentation in Hudu: network diagrams, runbooks, asset inventories, and credentials. The Hudu integration brings that documentation into AlgaPSA so a technician working a ticket for a client can see that client's assets, knowledge-base articles, and passwords in context — instead of switching tools mid-task.

This guide walks through connecting Hudu, mapping your Hudu companies to AlgaPSA clients, deciding how Hudu asset layouts import into AlgaPSA, and using the documentation surfaces on a client record. The examples use a fictional MSP managing clients such as Northstar Accounting, GreenLeaf Dental Group, and Pioneer Law Group.

How the integration behaves: The Hudu integration is pull-only and read-safe. AlgaPSA reads from Hudu and never writes changes back, so Hudu remains your system of record for documentation. Your Hudu API key is stored securely and is never displayed again after you save it.

Before You Start

Connect Your Hudu Instance

1. Navigate to Settings → General → Integrations in AlgaPSA.
2. Select the IT Documentation tab.
3. In the Hudu card, enter your Base URL (your Hudu instance address) and paste your API key.
4. Click Test Connection to confirm AlgaPSA can reach Hudu with the supplied credentials.
5. Click Connect.

When the connection succeeds, the card shows a Connected status, the detected Hudu instance, and whether Password access is enabled for the key.

Figure 1: The IT Documentation tab in Settings, with Hudu connected and ready to map companies.

Note: The API key field always reads "Leave blank to keep the current API key." AlgaPSA never displays a stored key. To rotate a key, paste the new value and click Connect again; leave it blank to keep using the existing key while changing other settings.

Map Hudu Companies to AlgaPSA Clients

A mapping tells AlgaPSA which Hudu company holds the documentation for each AlgaPSA client. Until a client is mapped, its Hudu surfaces stay empty.

1. In the Company Mappings section, click Refresh Companies to pull the latest company list from Hudu.
2. For each Hudu company, select the matching AlgaPSA Client from the dropdown.
3. AlgaPSA auto-suggests a match when a Hudu company name closely matches an AlgaPSA client — review suggestions before accepting them.

The counters at the top of the section summarize progress: mapped, suggested, unmapped, and total.

Figure 2: Each Hudu company is mapped to its AlgaPSA client. The status column confirms the link.

Operational check: Re-run Refresh Companies after you add a new client in Hudu or onboard a new client in AlgaPSA, then map the new pairing so its documentation appears.

Decide How Asset Layouts Import

Hudu organizes assets into layouts (Computer Assets, Firewalls, Databases, Email, and so on). The Asset Layouts section controls how each Hudu layout maps to an AlgaPSA asset type when you import assets. Any layout left unconfigured imports as Unknown.

1. For each Hudu Layout, choose the AlgaPSA Asset Type it should import as (for example, Computer Assets → Workstation, Firewalls → Network Device).
2. To keep a layout out of AlgaPSA entirely, set it to Don't import.
3. If no existing AlgaPSA asset type fits a layout, click Create type from layout. AlgaPSA generates a custom asset type whose fields mirror the Hudu layout, then assigns the layout to it in one step.

Figure 3: Mapping Hudu asset layouts to AlgaPSA asset types, with the option to create a matching custom type.

Tip: "Create type from layout" is the fastest way to bring specialized documentation — like Cloud Accounts or Door Access Systems — into AlgaPSA with the right fields, rather than collapsing everything into a generic type.

Work with a Client's Documentation

Once a client is mapped, open the client record (Clients → [client name]) to find the Hudu surfaces.

The Hudu Tab: Assets

The Hudu tab lists the client's Hudu assets next to any matching AlgaPSA assets, with the counts of mapped, suggested, unmapped, and total assets.

• Import all unmatched brings every unmapped Hudu asset into AlgaPSA using your asset-layout mappings.
• Sync from Hudu pulls the latest values for assets that are already mapped, so renamed or updated Hudu records stay current in AlgaPSA.
• Each row shows the import or link status, and Open in Hudu jumps to the source record.

Figure 4: The Hudu tab on a client record, mapping Hudu assets to AlgaPSA assets with import and sync controls.

The Hudu Tab: Articles

Below the assets, the Articles section lists the client's Hudu knowledge-base articles — runbooks, onboarding checklists, and procedures. These are link-only: selecting an article opens it in Hudu, so your team always reads the current, authoritative version.

Figure 5: A client's Hudu articles, linked directly to the source documentation in Hudu.

Reveal Client Passwords Securely

When your Hudu API key has password access, mapped clients show a Passwords tab. Credentials are listed by name and username with the secret hidden by default.

1. Click Reveal on a password row to display its value.
2. Click Open in Hudu to manage the credential at the source.

Figure 6: Hudu passwords on a client record. Values stay hidden until a technician reveals them.

Security: Every reveal is recorded in AlgaPSA's audit log with the user and timestamp, so credential access is accountable. Passwords are fetched on demand from Hudu and are never stored in AlgaPSA. If the API key lacks password access, the Passwords tab does not appear.

Browse Documentation Across Clients

To search documentation without opening each client individually, navigate to Documents and select the Hudu tab. This cross-client view lists every Hudu article across your mapped clients, showing the AlgaPSA client and the source Hudu company side by side. Use the search box to find an article by title.

Figure 7: The cross-client Hudu articles view on the Documents page.

Keeping AlgaPSA and Hudu in Step

Your Hudu integration is now ready. Technicians can see each client's assets, articles, and credentials directly inside AlgaPSA, while Hudu remains the single source of truth your team maintains.