Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Firewall Groups, is designed to fetch a list of firewall groups from the Connect Secure API. It allows users to query and filter firewall group data based on various parameters such as conditions, pagination controls (skip and limit), and sorting order. This operation is useful in scenarios where network administrators or security engineers want to programmatically access and manage firewall group configurations, audit existing groups, or integrate firewall group data into broader automation workflows.

Practical examples:

  • Automatically retrieving all firewall groups that match certain criteria for compliance reporting.
  • Paginating through large sets of firewall groups to synchronize with an external system.
  • Sorting firewall groups by creation date or name to display in a custom dashboard.

Properties

Name Meaning
X USER ID User Id header required for authentication or identification purposes in the API call.
Condition Query condition string to filter firewall groups based on specific criteria.
Skip Number of records to skip, used for pagination.
Limit Maximum number of records to return, used for pagination.
Order By Field(s) to order the results by, e.g., name, creation date, etc.

Output

The node outputs JSON data representing the retrieved firewall groups. Each item in the output corresponds to a firewall group object returned by the API, containing details such as group identifiers, names, and other metadata as provided by the Connect Secure API.

If the API supports binary data related to firewall groups (e.g., configuration files or exports), this node would handle it accordingly, but based on the static code and properties, the output is primarily structured JSON data.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the Connect Secure API being accessible and properly configured.
  • No additional environment variables are explicitly required beyond the API credential.
  • Uses the @devlikeapro/n8n-openapi-node package and lodash internally for OpenAPI parsing and utility functions.

Troubleshooting

  • Common issues:

    • Missing or invalid "X USER ID" header will likely cause authentication or authorization errors.
    • Incorrect query conditions may result in empty responses or API errors.
    • Pagination parameters (skip and limit) set incorrectly might lead to unexpected subsets of data.
    • Network connectivity issues or incorrect API credentials will prevent successful data retrieval.

  • Error messages:

    • Authentication failures typically indicate missing or wrong user ID or API key; verify credentials.
    • Validation errors on query parameters suggest malformed or unsupported filter conditions.
    • Rate limiting or quota exceeded errors require checking API usage limits and possibly adjusting request frequency.

Links and References

Discussion