AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the AvantGuard ConnectSecure API to retrieve firewall group information. Specifically, the "Get Retrieve Firewall Groups" operation fetches a list of firewall groups based on optional query parameters and a required user ID header. This node is useful in scenarios where you need to programmatically access or audit firewall group configurations, filter groups by conditions, paginate results, or order them for display or further processing.

Practical examples include:

  • Retrieving all firewall groups associated with a specific user.
  • Filtering firewall groups by certain conditions (e.g., status or type).
  • Paginating through large sets of firewall groups using skip and limit parameters.
  • Ordering firewall groups by name or creation date.

Properties

Name Meaning
X USER ID User Id - a required string header identifying the user making the request.
Additional Query Parameters Optional query parameters to refine the retrieval:
- Condition: A query condition string to filter firewall groups.
- 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 firewall groups. The structure typically includes an array of firewall group objects, each containing details such as group identifiers, names, and other metadata as defined by the AvantGuard ConnectSecure API response schema.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard ConnectSecure API.
  • The base URL for the API must be configured in the node credentials.
  • The node depends on the @avantguardllc/n8n-openapi-node package and the OpenAPI specification (openapi.json) bundled within the node implementation.

Troubleshooting

  • Missing or invalid X USER ID: Since the user ID header is required, omitting it or providing an incorrect value will likely cause authentication or authorization errors. Ensure the correct user ID is provided.
  • Invalid query parameters: Providing unsupported or malformed query parameters may result in API errors or empty responses. Validate query parameter values before use.
  • API connectivity issues: Network problems or incorrect base URL configuration can prevent successful API calls. Verify network access and credential settings.
  • 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