Actions11
Overview
This node integrates with the Huntress API to retrieve multiple summary reports based on specified filters. It is designed to fetch aggregated data summaries such as monthly, quarterly, or yearly reports for an organization. This functionality is useful for users who want to analyze security or operational metrics over different time periods.
Typical use cases include:
- Generating periodic security summary reports for an organization.
- Automating retrieval of historical summary data for further processing or visualization.
- Filtering reports by organization and report type to focus on relevant data.
Properties
| Name | Meaning |
|---|---|
| Filters | A collection of filters to narrow down the summary reports retrieved. Includes: |
| - Organization ID: Numeric identifier of the organization to filter reports for. | |
| - Type: The type of summary report to retrieve. Options are: Monthly, Quarterly, Yearly. |
Output
The node outputs JSON data representing the summary reports fetched from the Huntress API. Each item in the output corresponds to a summary report matching the provided filters. The structure typically includes fields related to the report's timeframe, metrics, and organizational context.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Huntress API.
- The node communicates with the Huntress API endpoint at
https://api.huntress.io/v1. - Pagination support is included via internal helper functions to handle large result sets.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing invalid filter values (e.g., non-numeric organization ID) may result in request errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors typically indicate incorrect or expired API keys; verify and update credentials.
- HTTP status codes returned from the API (e.g., 400 Bad Request) suggest malformed requests; check filter parameters.
- Timeout or network errors require checking internet connection and API availability.
Links and References
- Huntress API Documentation (for detailed API endpoints and data formats)
- n8n documentation on creating custom nodes