Actions9
Overview
This node interacts with the Huntress API to retrieve a specific Summary Report by its ID. It is useful when you want to fetch detailed summary information about security or operational reports managed within the Huntress platform. For example, a user might use this node to programmatically obtain a report summary for auditing, monitoring, or integration into other workflows.
Properties
| Name | Meaning |
|---|---|
| Summary Report ID | The unique numeric identifier of the summary report to retrieve. |
Output
The node outputs JSON data representing the requested Summary Report from the Huntress API. This JSON typically contains all details related to the specified summary report, such as report metadata, statistics, and any relevant summary fields provided by the API. There is no indication that binary data is returned.
Dependencies
- Requires an active connection to the Huntress API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for API requests is
https://api.huntress.io/v1. - Requests are made with JSON content type headers.
Troubleshooting
- Invalid or missing Summary Report ID: Ensure the ID is provided and is a valid number; otherwise, the API will return an error.
- Authentication errors: If the API key or token is invalid or expired, the node will fail to connect. Verify the API credentials in n8n.
- Network issues: Connectivity problems to the Huntress API endpoint can cause request failures.
- API rate limits: Excessive requests may be throttled by the Huntress API, resulting in errors.
- Common error messages include HTTP status codes like 401 (Unauthorized), 404 (Not Found if the report ID does not exist), or 500 (Server errors). Resolving these involves checking credentials, verifying the report ID, and retrying after some time.
Links and References
- Huntress API Documentation (for detailed API endpoints and data structures)
- n8n documentation on creating custom nodes