HuntressInstall

Summary

Isolates a Huntress agent for a reseller account by sending a POST request to /v1/accounts/{account_id}/agents/{id}/isolation. You can record a reason, enable strict isolation where supported, and customize the request body, headers, or query parameters.

Inputs

• Account Id (required) — The Huntress account ID.
• Id (required) — The agent ID to isolate.
• Reason — Optional reason recorded for the isolation.
• Strict Isolation — Whether to apply strict isolation; honored only on Windows (WFP) and Linux (eBPF).
• Custom Body — Optional JSON merged with the fields above; custom body values take priority.
• Custom Headers — Optional HTTP headers to add to the request.
• Query Filters — Optional query-string parameter names and values.
• Batching — Controls how input items are grouped and the delay between batches; the node makes one request per input item.
• Debug — When enabled, adds the request URL, query parameters, headers, and body to the output under a debug entry.
• Timeout (ms) — How long to wait for response headers before aborting; defaults to 300000 ms.

Output shape

A response from the isolation API for each input item.

The supplied source pack contains signatures only, so the exact response structure and whether debug details are included as a separate field cannot be confirmed. Pagination settings are declared but this operation is not a list operation.

Links

• n8n community nodes installation guide