IntelupInstall

Summary

Updates an existing operational security risk in Intelup by sending a JSON body to the Intelup API for the given risk ID (a PUT request, inferred from the operation key putPublicOperationalSecurityRisk­ById).

Inputs

• Version (required) — Intelup API version snapshot to use: 3.42.3 (default), 3.41.6, or 3.41.5. Selects which operation definition is called.
• Id (required) — Identifier of the operational security risk to update. It is URL-encoded and substituted into the request path.
• Body (JSON) (required) — JSON payload with the risk fields to update. The default template, generated from the Swagger spec, shows code, description, created_at and updated_at with placeholder values. Replace these with real values. Invalid JSON raises a 'Body must be valid JSON' error.

Output shape

One output item per input item, each with the Intelup API's JSON response as its json payload.

The request is sent once per input item using the credential's base URL, token, code and unit-code headers. With Continue On Fail enabled, a failed item returns {error: message} instead of stopping the run. The response schema is not defined in the node, so the returned fields depend on the API.

Examples

Example 1: Rename or re-describe an existing operational security risk from an earlier node's output.

Version 3.42.3; Id set to an expression like {{$json.id}}; Body (JSON) set to {"code":"OPS-12","description":"Updated risk description"}.

Links

• n8n community nodes installation guide