AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the "Discovery Settings" resource of the AvantGuard ConnectSecure API, specifically to retrieve a single discovery setting by its unique identifier. It is useful in scenarios where you need to fetch detailed configuration or status information about a particular discovery setting within your security or network environment managed by AvantGuard.

For example, you might use this node to:

  • Retrieve the current configuration of a specific discovery setting for auditing or monitoring.
  • Fetch details before updating or deleting a discovery setting.
  • Integrate discovery setting data into workflows that automate security compliance checks.

Properties

Name Meaning
X USER ID The user identifier required as a header to authenticate or specify the user context.
Id The numeric identifier of the discovery setting to retrieve.

Output

The node outputs JSON data representing the retrieved discovery setting object. This JSON typically includes all properties and metadata associated with the specified discovery setting as returned by the AvantGuard ConnectSecure API.

No binary data output is indicated or expected from this operation.

Dependencies

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

Troubleshooting

  • Missing or invalid X USER ID header: Ensure the "X USER ID" property is set correctly; it is required and sent as a header.
  • Invalid or non-existent Id: The "Id" must be a valid number corresponding to an existing discovery setting; otherwise, the API will return an error.
  • Authentication errors: Verify that the API key credential is properly configured and has sufficient permissions.
  • Network or connectivity issues: Confirm that the base URL is reachable and correct.
  • Unexpected API response: Check if the API version or endpoint has changed; update the node or OpenAPI spec accordingly.

Links and References

Discussion