AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the AvantGuard ConnectSecure API to retrieve the window protection status of a specific asset. It is useful in scenarios where users need to monitor or audit the security status of physical assets, particularly focusing on whether their windows are protected or not. For example, security teams can use this node to programmatically check if certain assets have active window protection enabled, helping maintain compliance and respond quickly to vulnerabilities.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes in the API request.
Id The numeric identifier of the asset whose window protection status is being retrieved.

Output

The node outputs JSON data representing the window protection status of the specified asset. This typically includes details such as whether the window protection is active, timestamps, and possibly related metadata about the asset's security state. No binary data output is indicated.

Dependencies

  • Requires an API key credential for AvantGuard ConnectSecure to authenticate requests.
  • Needs the base URL of the AvantGuard ConnectSecure API configured in the node credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package and the bundled OpenAPI specification (openapi.json) for request construction.

Troubleshooting

  • Missing or invalid X USER ID: Ensure that the "X USER ID" property is provided and correctly set; otherwise, the API may reject the request.
  • Invalid asset Id: Providing an incorrect or non-existent asset Id will result in errors or empty responses.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Network issues: Check connectivity to the AvantGuard API endpoint and confirm the base URL is correct.
  • Unexpected response format: If the API changes, the node might fail to parse the response properly; updating the OpenAPI spec or node code may be necessary.

Links and References

Discussion