Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node updates an existing Asset by sending new data to the Connect Secure API. It is useful in scenarios where asset information needs to be modified or refreshed, such as updating patch statuses, firewall flags, or discovered protocols for a given asset. For example, you might use this node to mark an asset as deprecated, update its scan status, or change its unique identifiers.

Properties

Name Meaning
X USER ID User Id header value required for authentication or identification purposes in the API request.
Data JSON object containing the asset fields to update. Fields include os_patches, snmp_info, is_firewall, unique_id, status, is_deprecated, discovered_protocols, scan_status, and install_required_patches. Example default structure:
json { "os_patches": "[]", "snmp_info": "[]", "is_firewall": false, "unique_id": "[]", "status": true, "is_deprecated": false, "discovered_protocols": "[]", "scan_status": true, "install_required_patches": "[]" }
Id Numeric identifier of the asset to update.

Output

The node outputs the response from the API call in the json field of the output item. This typically contains the updated asset data or confirmation of the update operation. The exact structure depends on the API response but generally reflects the current state of the asset after the update.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node expects the user to provide a valid X USER ID header value.
  • The node uses the Connect Secure API endpoint defined in the bundled OpenAPI specification (not fully shown here).
  • Proper network access to the Connect Secure API service is necessary.

Troubleshooting

  • Missing or invalid X USER ID: The API may reject requests without a valid user ID header. Ensure this property is set correctly.
  • Invalid asset Id: If the asset ID does not exist or is incorrect, the API will likely return an error indicating the asset was not found.
  • Malformed JSON in Data: The Data property must be valid JSON. Errors parsing this input will cause the request to fail.
  • API authentication errors: Make sure the API key credential is configured properly in n8n.
  • Network issues: Verify connectivity to the API endpoint.

Common error messages will relate to authorization failures, resource not found, or validation errors on the payload. Checking the API response message usually helps identify the root cause.

Links and References

Discussion