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 → Update Assessment
AI-generatedSummary
Updates an existing HackNotice assessment by sending a PUT request to /assessments/:docId with a JSON body, and returns the API's response as output items.
Inputs
- Document ID (required) — ID of the assessment to update. It is trimmed, URL-encoded and placed in the path. The node throws an error if it is empty.
- Request Body (required) — JSON object with the fields to change. It must be a non-empty object, otherwise the node throws 'Request body is required'. Invalid JSON, or a JSON array, is treated as {} and so also triggers that error.
- 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.
Output shape
One output item per object returned by the API. An array response yields one item per element, a single object yields one item, and an empty response yields none. A primitive response is wrapped as {value}. Each item is paired to its input item.
Requests go to https://extensionapi.hacknotice.com using the hackNoticeApi credential. HTTP failures are raised as NodeApiError, and validation failures as NodeOperationError. The response shape is whatever the API returns, which the source does not define.
Examples
Example 1: Rename an assessment or change its fields from a previous node's output
Resource: Assessment; Operation: Update Assessment; Document ID: {{$json.id}}; Request Body: {"name":"Q4 Vendor Review"}