AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the AvantGuard ConnectSecure API to retrieve discovery settings mappings related to agents. Specifically, the "Get Retrieve Agent Discoverysettings Mapping" operation fetches configuration or mapping data that defines how agent discovery settings are structured or applied.

Typical use cases include:

  • Automating retrieval of agent discovery configurations for auditing or synchronization.
  • Integrating discovery settings into workflows that manage network or security agents.
  • Fetching filtered or paginated discovery settings data based on query parameters.

For example, a user might want to get all discovery settings mappings for a specific user ID, optionally filtering or ordering the results.

Properties

Name Meaning
X USER ID The User ID header value required by the API to identify the user making the request.
Additional Query Parameters Optional parameters to refine the query:
- Condition: Filter condition string.
- Skip: Number of records to skip (for pagination).
- Limit: Maximum number of records to return.
- Order By: Field(s) to order the results by.

Output

The node outputs JSON data representing the retrieved agent discovery settings mappings. The structure corresponds to the API response and typically includes details about each discovery setting mapping such as identifiers, configuration fields, and metadata.

No binary data output is indicated in the source code or properties.

Dependencies

  • Requires an API key credential for AvantGuard ConnectSecure to authenticate requests.
  • Needs the base URL of the AvantGuard ConnectSecure API configured in credentials.
  • Uses the @avantguardllc/n8n-openapi-node package internally to build and execute API requests.

Troubleshooting

  • Missing or invalid X USER ID: The API requires the X-USER-ID header; ensure it is provided and correct.
  • API authentication errors: Verify that the API key credential is valid and has necessary permissions.
  • Query parameter issues: Invalid values for condition, skip, limit, or order_by may cause errors or empty results.
  • Network or connectivity problems: Ensure the base URL is reachable from the n8n instance.

Common error messages will likely relate to HTTP status codes such as 401 Unauthorized (authentication failure), 400 Bad Request (invalid query parameters), or 404 Not Found (resource not found).

Links and References

  • AvantGuard ConnectSecure API documentation (refer to official AvantGuard resources).
  • n8n documentation on creating and using API key credentials.
  • OpenAPI specification used internally (not directly exposed but useful for advanced users).

Discussion