Actions85
- Assessment Actions
- Assessment Data File Actions
- Assessment Data File (Invited) Actions
- Assessment Event Actions
- Assessment Invite Actions
- Assessment Preference Actions
- Assessment Template Actions
- Chatter Actions
- End User Actions
- End User Watchlist Actions
- First Party Alert Actions
- First Party Watchlist Actions
- Leak File Search Actions
- Research Actions
- Third Party Alert Actions
- Third Party Watchlist Actions
Assessment Data File → Count Files
AI-generatedSummary
Counts assessment data files by sending a POST to HackNotice's /assessmentdatafiles/count endpoint, with an optional JSON filter body.
Inputs
- Request Body — JSON object sent as the POST body, used as the count filter. Empty, invalid, or non-object JSON is treated as {}. The API's accepted filter fields aren't defined in the node.
- Document ID — Shown in the UI but not used by this route, because the path has no document ID.
- Page Number — Shown in the UI but not used, because the count path has no page segment.
- Invite Code — Shown in the UI but not used by this route.
Output shape
One output item per input item. The item's JSON is the API response, normalized: an object becomes one item, an array becomes one item per element, and a scalar becomes {value: ...}. Each item is paired to its input item.
The node doesn't reshape the response into a {count} object for this operation. The exact fields depend on what the API returns. Authentication uses the hackNoticeApi credential. API errors are raised as NodeApiError.
Examples
Example 1: Get the total number of assessment data files.
Resource: Assessment Data File; Operation: Count Files; Request Body: {}
Example 2: Count only the files that match a filter.
Resource: Assessment Data File; Operation: Count Files; Request Body: JSON filter object, for example one with an assessment ID field. Check the HackNotice API docs for valid field names.