HackNoticeInstall

Summary

Uploads a binary file from the incoming n8n item to HackNotice as an invited assessment data file, via a multipart POST to /assessmentdatafiles/invited.

Inputs

• Upload Assessment ID (required) — Assessment ID sent as multipart field assessment_id. The node throws an error if it is empty.
• Input Binary Field (required) — Name of the binary property on the input item that holds the file (default data). It is sent as multipart field data, using the binary's own file name and MIME type. If those are missing, the name falls back to upload.<ext> or upload.bin, and the type to application/octet-stream.
• Upload Filename — Optional filename form field. It is sent only when non-empty.
• Upload Note — Optional note form field. It is sent only when non-empty.

Output shape

One or more JSON items containing the API's response, each paired to the input item. An array response yields one item per element, an object yields one item, and a scalar is wrapped as { value }.

The file itself is not returned. The shared fields Document ID, Page Number, Invite Code and Request Body are shown in the UI but are not used for this operation. Missing binary data, a missing Assessment ID or an empty binary field name raises an error. API failures are raised as NodeApiError. Authentication uses the hackNoticeApi credential.

Examples

Example 1: Upload a file downloaded earlier in the workflow to an assessment you were invited to.

Place an HTTP Request or Read Binary File node first. Then set Upload Assessment ID to the assessment's ID and Input Binary Field to data.

Example 2: Attach evidence with a custom name and a comment.

Set Upload Assessment ID, set Upload Filename to evidence.pdf, and set Upload Note to Q3 scan results.

Links

• n8n community nodes installation guide