Skip to main content
Connect Hudu and every client agent works from your existing IT documentation (companies, assets, articles, procedures, Central KB, and passwords) the same way a senior technician would. Every internal note the agent posts on a ticket links back to the exact Hudu record behind each claim.
Hudu is configured in MSP Settings → Integrations.

​
What it’s for

Hudu is where most MSPs keep their per-client documentation — asset records, network diagrams, service accounts, “how we do X for client Y.” Connect it and the whole library is on hand for every ticket, scoped to the client the ticket belongs to.

​
How to connect

Hudu uses API key authentication.
1

Generate a Hudu API key

Sign in to Hudu as an admin and go to Admin → API Keys. Click + Add new API Key, give it a recognizable name (e.g. Rallied Integration), and copy the key. It’s shown only once.
2

Open MSP Integrations

In Rallied, go to MSP Settings → Integrations.
3

Connect Hudu

Find the Hudu card and click Connect. A credentials form appears.
4

Enter your credentials

Fill in:
  • API Key — the key you generated above.
  • Hudu URL — your Hudu hostname (e.g. yourdomain.huducloud.com for Hudu Cloud, or hudu.yourmsp.com for self-hosted). You can paste the full URL with https://; Rallied handles the rest.
Self-hosted Hudu must be reachable from the public internet over HTTPS with a valid, publicly-trusted TLS certificate.
5

Save and confirm

Click Save. Rallied validates the key against your Hudu instance and imports your companies as candidate client mappings. The card shows Connected when it’s ready.

​
Mapping companies to clients

Hudu stores documentation per company. On each Rallied client’s detail page, pick the matching Hudu company. From then on, every Hudu lookup the agent does for that client stays scoped to that company, so there’s no risk of pulling another client’s runbook into a response. If a client isn’t mapped to a Hudu company, the agent will not use Hudu for that client’s tickets.
The Internal company in Hudu (the one representing the MSP itself) is excluded from client mapping. Central KB articles and shared procedures are still available to every client agent as MSP-wide knowledge.

​
What your technicians see

Every internal note the agent posts on a ticket includes clickable links back to the exact Hudu record it used: the specific article, procedure, or asset. Technicians open the note, see the plan, and click straight through to the source. Outdated runbooks get spotted (and fixed) as a byproduct of working tickets.

​
What the agent reads

PDF attachments on Hudu articles are used the same as the article text, so vendor guides and RFPs your team keeps attached are searchable too.

​
Passwords and approval

Passwords retrieved from Hudu are sensitive. The hudu-get-password tool reveals the value, so the agent records in its notes why a credential was accessed. For especially sensitive operations, you can tighten this further:
  • Require identity verification before the agent uses any retrieved credential.
  • Change the tool’s setting from Auto-approve to Needs approval on MSP Settings → Integrations → Hudu.
Passwords are searchable by name only, never by value, so the agent can identify that a credential exists without seeing it until it explicitly retrieves it.

​
Managing your Hudu documentation

Open MSP Settings → Integrations → Hudu to see:
  • How much of your Hudu content is available to the agent
  • How often the agent has cited a Hudu record in the last 30 days
  • When Hudu was last refreshed
  • A Sync now button to pull in the latest edits immediately
See Documentation for the full picture of how the agent uses all your connected documentation together.

​
Approval settings

Read actions default to Auto-approve so the agent can consult your documentation freely during diagnosis. Write actions — like creating a new knowledge base article — default to Needs approval. Fine-tune from MSP Settings → Integrations → Hudu. Per-client overrides live on the client’s detail page.

​
See also