Vight

The Vight integration with Hudu brings your published Hudu knowledge base into Ask Vight, the AI assistant for MSPs. Once connected, your team can ask questions about runbooks, SOPs, onboarding, and client systems and get answers grounded in your Hudu documentation.

What You'll Need

Ability to add integrations in Vight.
Admin or Super Admin role in Hudu (required to create an API key).

Integration Features

Finds the matching Hudu company before searching client-specific documentation.
Searches central/global and company-specific published articles.
Reads a selected article to answer questions about runbooks, SOPs, onboarding, and client systems.
Uses read-only API calls; Vight does not create, change, or delete Hudu content.
Stores one organization-level API key, encrypted at rest.

What Vight needs from Hudu

API Key (read-only)

Before You Connect

The key is shared at the Vight organization level. Any Vight user who can use Ask Vight can search documentation for every company allowed by that key, and individual Hudu user permissions do not apply.

Hudu article content used to answer a question is sent to the configured Ask Vight model, and the resulting chat answer can be saved in conversation history.

Enabling the Vight Integration

The integration between Vight and Hudu was built by Vight via the API. The integration is enabled within the Vight platform.

Obtaining Hudu API Credentials

The integration is read-only and only calls the Companies and Articles endpoints of the Hudu API. Create a dedicated key with the least privilege possible.

Navigate to the Hudu admin area and click API Keys, then click + New API Key.
- Name: enter a name such as Vight.
- Limit scope to: select Full access.
- Company: optionally scope the key to a specific company Vight should be able to search. Leave blank for all companies.
- Allowed IP Addresses: optionally enter 52.2.110.170 (Vight's production egress IP), one per line. Leave blank for all.
- Key can perform the following actions: leave View passwords, Delete data, and Export data all unchecked. Vight is read-only and does not use any of these.

Click Create.
Copy the generated key.
- Be sure to copy the key and keep this in a secure location; this will be the last time you see this key.

Setting Up the Integration in Vight

In Hudu, create the dedicated API key described above.
In Vight, open Integrations.
Click Add Integration, then select Hudu under Knowledge.
Enter your Hudu tenant URL, such as https://example.huducloud.com. Enter the origin only, without /api/v1 or another API route.
Paste the API key and click Create Integration.
Open the integration and use Test Connection to confirm Vight can read published articles.

Vight validates article access before saving. Only one Hudu integration is allowed per Vight organization.

Using Hudu in Ask Vight

Once connected, ask questions naturally. For example:

"Find the VPN troubleshooting runbook for Acme in Hudu"
"What does Contoso's onboarding article say about firewall access?"
"Search our central Hudu articles for the laptop replacement process"

For client questions, Ask Vight resolves the Hudu company, searches within that company, and reads the selected article before answering. For central documentation, it filters out company-owned articles.

Troubleshooting

Use Test Connection after rotating or changing the key.
A 401 error usually means the key is invalid or revoked.
A 403 error means the key does not have access to the requested content.
Confirm the URL starts with https:// and is the same Hudu hostname you use in a browser.
Confirm the key allows article access and that any company or IP restrictions include the content and the Vight egress IP (52.2.110.170) you intend to use.
Search quality depends on Hudu's keyword search. Include a client name and a few distinctive terms in the question.

For more about Vight, visit vight.ai or contact Vight support at support@vight.ai.