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 → Delete File
AI-generatedSummary
Deletes a single HackNotice assessment data file by sending an authenticated DELETE to /assessmentdatafiles/:docId, using the supplied Document ID.
Inputs
- Document ID (required) — ID of the assessment data file to delete. It is trimmed and URL-encoded into the path. If it is empty, the node throws 'Document ID is required for this operation.'
- Page Number — Shown in the UI but not used by this operation, because the path has no page segment.
- Invite Code — Shown in the UI but not used by this operation.
- Request Body — Shown in the UI but ignored. DELETE requests are sent without a body.
Output shape
One or more JSON items containing the API's response, each paired to the input item. A null or empty response gives no items. A non-object response is wrapped as { value: ... }.
The response body is not documented in the source, so its exact fields are unknown. API errors are raised as NodeApiError, and a missing Document ID as NodeOperationError. This deletes the file's data and cannot be undone from the node. To delete invited-flow files, use the separate 'Assessment Data File (Invited)' resource.
Examples
Example 1: Remove a file that is no longer needed after an assessment closes.
Resource: Assessment Data File; Operation: Delete File; Document ID: {{ $json._id }}
Example 2: Clean up files returned by a List Files (Page) step, one item per file.
Document ID set to the expression {{ $json.id }} so the node runs once per input item.