AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the "Attack Surface" resource to retrieve attack surface results. It is designed to fetch data related to security assessments or vulnerability scans, which can be useful for cybersecurity analysts or automated security workflows. Typical use cases include querying recent attack surface findings, filtering results based on conditions, and paginating through large datasets of security information.

For example, a user might want to retrieve all attack surface results for a specific user ID, limit the number of records returned, or order the results by date or severity.

Properties

Name Meaning
X USER ID The User Id header value required to identify the user context for the request.
Additional Query Parameters Optional parameters to refine the query:
- Condition: Filter condition as a 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 attack surface results. This typically includes an array of objects detailing individual attack surface entries matching the query criteria. Each entry may contain fields such as identifiers, timestamps, status, and other relevant metadata about the attack surface.

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

Dependencies

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

Troubleshooting

  • Missing or invalid X USER ID: Since the X USER ID header is required, omitting it or providing an incorrect value will likely cause authentication or authorization errors. Ensure this property is set correctly.
  • Invalid query parameters: Providing malformed or unsupported values in additional query parameters like condition, skip, limit, or order_by may result in API errors or empty responses. Validate these inputs carefully.
  • API connectivity issues: Network problems or incorrect base URL configuration can prevent successful requests. Verify API endpoint accessibility and credential correctness.
  • Rate limiting or permission errors: If the API enforces rate limits or user permissions, exceeding limits or lacking rights may cause errors. Check API documentation and user privileges.

Links and References

Discussion