AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node is designed to retrieve firewall policy data related to assets from the AvantGuard ConnectSecure API. It is useful in scenarios where users need to programmatically access detailed firewall policies associated with specific assets, for example, to audit security configurations, integrate firewall policy data into monitoring dashboards, or automate compliance checks.

A practical example would be a security operations team automating the retrieval of asset firewall policies to verify that all assets comply with organizational security standards without manually logging into the firewall management console.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes in the API request.
Additional Query Parameters Optional parameters to refine the query:
- Condition: Filter condition string.
- Skip: Number of records to skip.
- 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 asset firewall policy information. This typically includes details about firewall rules, conditions, and metadata associated with the asset's firewall configuration.

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

Dependencies

  • Requires an API key credential for AvantGuard ConnectSecure (configured in n8n credentials).
  • Depends on the AvantGuard ConnectSecure API endpoint URL provided via credentials.
  • Uses the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled with the node for request building and execution.

Troubleshooting

  • Missing or invalid X USER ID: Since this header is required, omitting it or providing an incorrect value will likely cause authentication or authorization errors. Ensure the correct user ID is supplied.
  • API connection issues: Verify that the base URL and API credentials are correctly configured in n8n.
  • Invalid query parameters: Using unsupported or malformed query parameters in "Additional Query Parameters" may result in API errors or empty responses.
  • Rate limiting or permission errors: If the API enforces rate limits or permissions, ensure the API key has sufficient rights and usage limits are respected.

Links and References

Discussion