Skip to main content

Connect Huntress to Lexful

Connect Huntress to collect organizations, agents and security information.

Connect Huntress to collect organizations, protected agents and security information in Lexful.

Early access: This integration supports syncing, but is still being tested and data may be incomplete. Saving credentials alone does not enable syncing; opt in when you are ready.

Create Huntress API credentials

  1. In Huntress, sign in as an administrator and open API Credentials from the menu.

  2. Under User API Credentials, choose Add. Select the user and give the credential a descriptive name, such as Lexful.

  3. Copy the API Key and Secret into secure storage. Use a user with read access to the organizations and security data you need.

User-based keys inherit that user’s permissions. Huntress has deprecated account-based keys, which may return incomplete data. See Generating API Keys.

Connect in Lexful

  1. As a Lexful administrator, open Platform → Integrations → Sources, find Huntress, and choose Connect. Open the existing connection if you have already added it.

  2. Enter the credentials in API Key and API Secret.

  3. Choose Test Connection and resolve any errors. Select Enable early-access syncing when available if you want to start collecting data, then choose Save credentials. If you save without opting in, use Start syncing on the connection when ready.

What syncs

  • Organizations and agents.

  • Signals and incident reports.

  • Remediation information associated with incidents.

  • Managed identities.

Lexful reads this information; this connection does not execute remediation, isolate devices or change Huntress settings. Source security datasets do not each become a separate documentation asset.

Check the first sync

Open the connection’s Activity and check the relevant source tables. A successful connection test checks a limited API request; it does not confirm a complete sync.

Collected source data does not automatically become a document or asset for every source object. Review the available mappings, customer selection and filters before syncing supported records into your organizations. See Map integration categories and clients and Choose what to import.

If data is missing

The connection test reads organizations only. If that succeeds but another source table fails, check the API user’s access to that data and whether you are using a deprecated account key. Check Sync activity before changing customer mappings.

If an error remains, use Support in Lexful or contact us. Include the provider, failed source table and visible error. Do not send API keys, secrets or passwords.

Did this answer your question?