HackNoticeInstall

Summary

Counts invited assessment data files by sending a POST to HackNotice's /assessmentdatafiles/invited/count endpoint with a required JSON filter body, and returns the API's count response.

Inputs

• Request Body (required) — JSON object sent as the POST body (filter criteria for the count). The route requires a non-empty object; an empty {}, invalid JSON, or a non-object value throws 'Request body is required for this operation'. The accepted filter fields are not defined in the node.
• Document ID — Shown in the UI but not used by this route (the path has no document ID segment).
• Page Number — Shown in the UI but not used by this route (the path has no page segment).
• Invite Code — Shown in the UI but not used by this route (the path has no invite code segment).

Output shape

One output item per API result, paired to the input item. The response is normalized: an array becomes one item per element, an object becomes a single item, null becomes none, and a scalar (such as a bare number) becomes { value: <scalar> }.

The response is not reshaped into a count field, unlike the alert count operations. The exact shape depends on what the HackNotice API returns. Requests are authenticated with the hackNoticeApi credential against https://extensionapi.hacknotice.com. HTTP errors surface as NodeApiError.

Examples

Example 1: Count the invited data files attached to a specific assessment.

Resource: Assessment Data File (Invited); Operation: Count Files (Invited); Request Body: a JSON filter object such as {"assessment_id": ""}. The field name is illustrative and not defined by the node.

Links

• n8n community nodes installation guide