Actions9
Overview
This node interacts with the Huntress API to retrieve multiple billing reports based on specified filters. It is useful for users who want to programmatically access and analyze billing data such as payment statuses or refunds from their Huntress account. For example, a user could fetch all open billing reports to monitor outstanding invoices or retrieve failed payments to investigate issues.
Properties
| Name | Meaning |
|---|---|
| Filters | A collection of filter options to narrow down the billing reports returned by the query. The only available filter is: Status, which can be one of the following values: Failed, Full Refund, Open, Paid, or Partial Refund. This filter controls which billing reports are fetched based on their payment status. |
Output
The node outputs JSON data representing an array of billing report objects matching the applied filters. Each object contains details about individual billing reports such as their status and other relevant billing information. There is no indication that the node outputs binary data.
Dependencies
- Requires an API key credential for authenticating with the Huntress API.
- The node makes HTTP requests to the base URL
https://api.huntress.io/v1. - Proper configuration of the API key credential in n8n is necessary for successful operation.
Troubleshooting
Common Issues:
- Invalid or missing API key credential will cause authentication failures.
- Using unsupported filter values may result in empty responses or errors.
- Network connectivity problems can prevent the node from reaching the Huntress API.
Error Messages:
- Authentication errors typically indicate invalid credentials; verify and update the API key.
- HTTP status codes returned from the API (e.g., 400, 401, 500) should be checked for more details.
- If the node returns no data, confirm that the filter criteria match existing billing reports.
Links and References
- Huntress API Documentation (for detailed API endpoints and parameters)
- n8n documentation on API Credentials