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 Event → Invited — Update Event
AI-generatedSummary
Updates an existing invited assessment event by sending a PUT request to /assessmentevents/invited/{docId} on the HackNotice extensions API, with the JSON Request Body as the payload.
Inputs
- Document ID (required) — ID of the invited assessment event to update. It is URL-encoded into the path. The node throws an error if it is empty.
- Request Body (required) — JSON object with the fields to update. It must be a non-empty object. An empty body, invalid JSON, or an array raises the error 'Request body is required for this operation'.
- Page Number — Shown in the UI but not used by this route, because the path has no page segment.
- Invite Code — Shown in the UI but not used by this route, because the path has no invite-code segment.
Output shape
One or more n8n items holding the JSON the API returns for the updated event. An array response becomes multiple items and an object becomes one item. A non-object response is wrapped as {value: ...}, and an empty response gives no items. Each item is paired to the input item.
The node uses the hackNoticeApi credential. Failures surface as a node error: validation problems as NodeOperationError, API or HTTP errors as NodeApiError. The fields the API accepts are not defined in the node source.
Examples
Example 1: Change the details of an invited assessment event after receiving its ID from an earlier step.
Resource: Assessment Event; Operation: Invited — Update Event; Document ID: {{$json.eventId}}; Request Body: {"note": "Reviewed"} (field names are illustrative)