Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Firewall Zones, is designed to fetch information about firewall zones from a Connect Secure API. It allows users to query and retrieve a list of firewall zones with optional filtering, pagination, and sorting capabilities. This can be useful in scenarios where network administrators or security teams want to automate the retrieval of firewall zone configurations for auditing, monitoring, or integration with other systems.

Practical examples include:

  • Automatically fetching firewall zones to sync with a centralized security dashboard.
  • Retrieving specific firewall zones based on conditions to analyze or report on network segmentation.
  • Paginating through large sets of firewall zones when managing extensive network environments.

Properties

Name Meaning
X USER ID User Id required for authentication, sent as a header named X-USER-ID.
Condition Query condition to filter the firewall zones returned by the API.
Skip Number of records to skip (for pagination).
Limit Maximum number of records to return (for pagination).
Order By Field(s) to order the results by (sorting criteria).

Output

The output of this operation is JSON data representing the retrieved firewall zones. Each item in the output corresponds to a firewall zone object as returned by the Connect Secure API. The exact structure depends on the API response but typically includes details such as zone identifiers, names, and associated properties.

If the node supports binary data output, it would represent any file or raw data related to firewall zones, but based on the provided code and properties, the output is purely JSON.

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.

Troubleshooting

  • Missing or invalid X USER ID: Since the X USER ID header is mandatory, omitting it or providing an incorrect value will likely cause authentication errors. Ensure the user ID is correct and included.
  • Invalid query parameters: Providing malformed or unsupported values in condition, skip, limit, or order_by may result in API errors or empty responses. Validate these inputs before execution.
  • API connectivity issues: Network problems or incorrect API endpoint configuration can cause failures. Verify network access and API URL settings.
  • Empty results: If no firewall zones match the given condition or if pagination skips all available records, the output may be empty. Adjust query parameters accordingly.

Links and References

Discussion