HackNoticeInstall

Summary

Returns the number of HackNotice phrase or filename research alerts matching a saved phrase search, optional extra JSON filters, and an optional time window.

Inputs

• Phrase Saved Search Name or ID — Saved phrase search from the dropdown, or an expression. Its stored filters become the base request body. If the saved search's endpoint is 'filename', the filename count endpoint is used. Otherwise the term count endpoint is used. If left empty, the body starts empty.
• Limit by Time — None (default) leaves any dates in the saved search or filters untouched. Last Day sets hours_ago=24. Last Week and Last Month set startdate to that many days or months back, at local midnight. Custom uses the start and end dates. Any choice other than None first removes the saved search's existing time fields.
• Start Date (required) — Shown only when Limit by Time is Custom. Sent as a startdate date (YYYY-MM-DD).
• End Date (required) — Shown only when Limit by Time is Custom. Sent as an enddate date (YYYY-MM-DD). Both dates must be valid or the node errors.
• Additional Filters — JSON object merged into the request body. It overrides saved-search filters, but Limit by Time still overrides date fields. Invalid JSON or a non-object value raises an error.

Output shape

One item per input item, with the fields count, pageSize (fixed at 50) and pageCount (ceil(count/50)).

The request is a POST to /research8/count/term, or /research8/count/filename/term when the saved search endpoint is 'filename'. The node throws an error if the API response has no numeric count. Each output item is paired to its input item.

Examples

Example 1: Check how many phrase-search hits appeared in the last week before deciding whether to fetch them.

Select a Phrase Saved Search, set Limit by Time to Last Week, and leave Additional Filters as {}.

Example 2: Count alerts in a fixed reporting period.

Set Limit by Time to Custom, then fill in Start Date and End Date.

Links

• n8n community nodes installation guide