AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Asset → Patch Update Asset

AI-generated

Overview

This node performs a patch update on an Asset resource by sending partial data updates to an external API. It is useful when you want to modify specific fields of an existing asset without replacing the entire asset record. For example, you might update the status, add new patches information, or change firewall settings for an asset in your inventory system.

Properties

Name Meaning
X USER ID The user identifier required as a header for authentication or tracking purposes in the API request.
Additional Body Fields Optional fields to include in the request body:
- Data (JSON): A JSON object containing various asset attributes such as patches, SNMP info, status, etc.
- Id (number): The numeric identifier of the asset to be updated.

The "Data" field supports these keys with example default values:

  • os_patches: array of OS patches
  • snmp_info: array of SNMP information
  • is_firewall: boolean indicating if it is a firewall
  • unique_id: array of unique identifiers
  • status: boolean status of the asset
  • is_deprecated: boolean flag for deprecation
  • discovered_protocols: array of protocols discovered
  • scan_status: boolean scan status
  • install_required_patches: array of required patches to install

Output

The node outputs JSON data representing the response from the patch update API call. This typically includes the updated asset details or confirmation of the successful update. There is no indication that binary data is handled by this node.

Dependencies

  • Requires an API key credential for authenticating requests to the external asset management service.
  • The base URL and headers are configured via node credentials and parameters.
  • Uses an OpenAPI-based request builder internally to construct and send HTTP PATCH requests.

Troubleshooting

  • Missing or invalid X USER ID: The API requires the X USER ID header; ensure it is provided and valid.
  • Invalid JSON in Data field: The "Data" property expects valid JSON; malformed JSON will cause errors.
  • Asset ID not provided or incorrect: The asset id must be specified correctly to identify which asset to patch.
  • API connectivity issues: Verify network access and correct base URL configuration.
  • Permission errors: Ensure the API key has rights to update assets.

Links and References

  • Refer to the external asset management API documentation for detailed schema and supported patch operations.
  • n8n documentation on using HTTP Request nodes and custom API integrations.

Discussion