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 — Create Event
AI-generatedSummary
Creates an assessment event in the "invited" context by sending a POST request with a JSON body to HackNotice's /assessmentevents/invited endpoint.
Inputs
- Request Body (required) — JSON object describing the event to create. It must be a non-empty object. An empty, invalid or non-object value (including an array) throws "Request body is required for this operation". The event schema isn't defined in the node, so check the HackNotice API docs for the fields.
- Document ID — Shown in the UI but not used by this route, because the path has no :docId segment.
- 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 API's JSON response. An array response becomes one item per element, an object becomes a single item, and an empty response gives no items. Each item is paired to the input item that produced it.
The call authenticates with the hackNoticeApi credential against https://extensionapi.hacknotice.com. A primitive response is wrapped as {value: ...}. API errors are raised as NodeApiError, and body validation errors as NodeOperationError.
Examples
Example 1: Log an event against an assessment you were invited to, using fields built in an earlier node.
Resource: Assessment Event; Operation: Invited — Create Event; Request Body: an expression such as {{ JSON.stringify($json.eventPayload) }}, or a literal JSON object with the event fields.