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 → Update File Metadata
AI-generatedSummary
Updates the metadata of an assessment data file in HackNotice by sending a PUT request to /assessmentdatafiles/:docId with a JSON body. It doesn't change the file contents.
Inputs
- Document ID (required) — ID of the assessment data file to update. It is URL-encoded into the path. The operation errors if it is empty.
- Request Body (required) — JSON object with the metadata fields to update, sent as the PUT body. It must be a non-empty JSON object. An empty, invalid or non-object value raises 'Request body is required'. The node doesn't document which fields the API accepts.
- Page Number — Shown in the UI but not used by this route.
- Invite Code — Shown in the UI but not used by this route.
Output shape
One or more n8n items holding the JSON response from the API, normally the updated file record. An array response becomes one item per element. Each item is paired to its input item.
The response shape comes from the HackNotice API and isn't defined in the node. An empty response gives no items. A non-object response is wrapped as {value}. HTTP errors are thrown as NodeApiError. It is authenticated with the hackNoticeApi credential against https://extensionapi.hacknotice.com.
Examples
Example 1: Add a note or rename a data file after review
Document ID = {{$json.fileId}}; Request Body = {"note":"Reviewed","filename":"findings.csv"}. The field names are illustrative and need to match what the API accepts.