Huntress

Huntress is a managed endpoint detection and response (EDR) platform built for MSPs. Connecting Huntress to Hudu pulls your Huntress agents and identities into Hudu automatically, so what Huntress protects is documented alongside the rest of each company's assets. This article walks through generating Huntress API credentials, connecting Huntress to Hudu, matching Huntress organizations to Hudu companies, and choosing where synced data lands.

Visit Understanding Integrations for additional information on how integrations work in Hudu.

What you'll need

Access to a Huntress account that can create API credentials.
- The integration connects with a single API key and secret, so there is no per-organization setup on the Huntress side.
Admin role within Hudu.

Integration features

The Huntress integration syncs the following into Hudu:

Organizations — Huntress organizations are matched to Hudu companies. Only matched organizations are imported.
Agents — endpoints running the Huntress agent, created as assets on the layout you choose.
Identities — identities Huntress tracks for each organization, created as assets on the layout you choose.

Each synced agent gets a Huntress integration card showing details such as hostname, platform, operating system, serial number, IP and MAC address, and EDR version. Agents also populate connected fields on their asset, and re-syncing updates existing assets rather than creating duplicates.

Obtaining the Huntress information

To generate your Huntress API credentials:

Sign in to the Huntress portal.
Open Account Settings and select API Credentials.
Generate a new API key.
Copy both the API key and the secret key and store them somewhere safe.

Huntress only displays the secret key once. Copy it before leaving the page. If it is lost, generate a new set of credentials.

Treat your Huntress API key and secret like a password. Consider storing them in a Hudu password record so your team can find them later.

Enabling the integration

Integrations can be enabled at any point during your Hudu environment testing and/or during production. Integrations can be merged into your existing documentation based on set rules, so you can start with integration setup or easily connect them at a later date. To enable the Huntress integration:

Navigate to the Hudu admin area → Integrations.
Select Huntress from the list. You can find it under the Monitoring category.

Setting up the integration in Hudu

Step 1. Connect to Huntress

Enter your Huntress API Key and API Secret Key.
Select Save Credentials.
Once saved, the secret is hidden. To replace it later, select the edit icon in the API Secret Key field.

Step 2. Test the connection

Select Test Connection at the top of the page. A successful test shows Connection successful.
If the credentials are rejected, double-check that you copied the full key and secret with no extra spaces.

Step 3. Activate and sync

Select Activate and Sync. Sync time varies depending on data size.
- You can navigate away while the sync runs.
Check the Logs tab during sync for status updates.

Step 4. Configure options

Customize what to sync and what Hudu updates.

Optional settings:
- Auto-update names of assets — automatically syncs asset names from Huntress to keep them current.
- Do not update basic company details — prevents Huntress from overwriting company details already in Hudu.
Optional exclusions: skip the following:
- Agents
- Identities
Select Save Options to move to the next step.

Step 5. Match companies

Match at least one company before syncing.

Huntress organizations must be matched to:
- Existing companies in Hudu, or
- New companies you create
Use the Unmatched and Matched tabs to review organizations. On the Unmatched tab, filter by All match types, Suggested matches, or No suggested matches.
Recommended: match one organization first for testing.
Use bulk actions to accept or delete matches.
Use the menu to:
- Accept Match
- Change Match
- Match New Company
- Delete Match
Unmatched organizations will not be imported.
Select Sync Now any time you make changes to matches.

Step 6. Choose where data will fill

Default asset layouts

Select a default layout for each category:
- Huntress agents
- Huntress identities
Synced data is created as assets on these layouts, only within matched companies.
Select Save Asset Layouts, then select Sync Now to run the initial sync.

Layout changes only apply to new data that has not already been synced into Hudu. Choose your layouts before the initial sync.

Visit Asset Layouts for additional information on creating layouts.

Tools

Managing the integration

The top of the Huntress settings page shows the integration status, the number of matched and unmatched companies, the number of synced cards, and the next scheduled sync. From here you can:

Select Test Connection to recheck your credentials.
Select Sync Now to run a sync outside the schedule.
Select Pause Integration to stop syncing without removing your setup.

Use the Cards, Settings, Logs, and Deletion Options tabs to review synced cards, update setup, check sync activity, and manage what happens to synced data.

Connected fields

Huntress agents can populate the following connected fields on your asset layout:

Device hostname
Serial number
OS name
OS version
IP address
MAC address

Set a field on your agents layout to one of these data points, then re-sync to fill it with the matching value from Huntress.

Visit the Connected Fields article for additional information on mapping integration data to asset fields.

FAQ

Do I need separate API credentials for each Huntress organization?

No. The integration connects with one API key and secret and pulls in all of your Huntress organizations, which you then match to Hudu companies.

Why aren't my Huntress agents or identities showing up in a company?

Data only syncs for Huntress organizations that are matched to a Hudu company. Open the Huntress integration, confirm the organization is on the Matched tab and a layout is selected for agents and identities, then select Sync Now.

Will a second sync create duplicate assets?

No. Re-syncing updates the existing assets and fields rather than creating duplicates.

Can I stop the sync temporarily?

Yes. Select Pause Integration at the top of the Huntress settings page. Your credentials, matches, and layouts stay in place.

Troubleshooting

The connection test fails with an authentication error

Confirm you entered both the complete API key and secret key with no extra spaces. If it continues to fail, generate new credentials in Huntress (Account Settings → API Credentials), update them in Hudu, and select Test Connection again.

Agents or identities aren't syncing at all

Check the Skip the following options in the Huntress integration settings. If Agents or Identities is selected, that data is left out of the sync. Also confirm a default layout is selected for both Huntress agents and Huntress identities.

Assets landed on the wrong layout

Data is created on the layouts selected in the Asset Layouts section. Changing a layout only applies to data that has not already been synced, so existing assets stay on their original layout. Update the layout selection for future syncs.

Connected fields are empty after syncing

Confirm the fields on your agents layout are set to Huntress connected-field data points, then re-sync. Fields set after the last sync will not fill until the next one runs.