HuntressInstall

Summary

Isolates a Huntress agent by sending a POST request to /v1/agents/{id}/isolation. You can include a recorded reason, request strict isolation, and configure custom request options.

Inputs

• Id (required) — Numeric ID of the agent to isolate.
• Reason — Optional reason recorded for the isolation.
• Strict Isolation — Whether to request strict isolation; honored only on Windows (WFP) and Linux (eBPF).
• Custom Body — Optional JSON body deep-merged with the fields above; custom body values take priority.
• Custom Headers — Optional HTTP headers to send with the request.
• Query Filters — Optional query-string parameter names and values.
• Batching — Optional batch size and interval for processing input items; the UI states one request is made per item, with pauses between batches.
• Debug — When enabled, adds the request URL, query parameters, headers, and body to the output under a debug entry.
• Timeout (ms) — Request timeout in milliseconds; defaults to 300000.

Output shape

A single API response per input item.

The operation does not expose the pagination settings in its operation-specific request path. The response fields depend on the Huntress API response; debug details are included only when enabled.

Examples

Example 1: Basic isolation

Provide the agent ID and optionally a reason or strict isolation setting.

Example 2: Troubleshoot a request

Enable Debug to include the outgoing request details in the output.

Links

• n8n community nodes installation guide