Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve firewall rules. It is designed to fetch a list of firewall rules based on user-defined query parameters such as filtering conditions, pagination controls (skip and limit), and sorting order. This node is useful in scenarios where you need to programmatically access and manage firewall configurations, audit security policies, or integrate firewall rule data into automated workflows.

Practical examples include:

  • Retrieving all firewall rules that match a specific condition for compliance reporting.
  • Paginating through large sets of firewall rules to display them in a dashboard.
  • Sorting firewall rules by creation date or priority to analyze recent changes.

Properties

Name Meaning
X USER ID User Id header required for authentication or identification in the API request.
Condition Query condition string to filter firewall rules based on specified criteria.
Skip Number of records to skip, used for pagination to offset the starting point of results.
Limit Maximum number of firewall rules to retrieve in one request.
Order By Field name(s) to sort the retrieved firewall rules by, e.g., "created_at" or "priority".

Output

The node outputs JSON data representing the retrieved firewall rules. Each item in the output corresponds to a firewall rule object returned by the Connect Secure API, containing details such as rule identifiers, conditions, actions, and metadata.

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

Dependencies

  • Requires an active connection to the Connect Secure API.
  • Needs an API key credential or equivalent authentication token configured in n8n to authorize requests.
  • The node depends on the @devlikeapro/n8n-openapi-node package and the OpenAPI specification (openapi.json) bundled within the node for request construction and response parsing.

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 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 credentials can lead to failed requests. Verify network access and credential validity.
  • Pagination mishandling: Setting skip and limit incorrectly might cause unexpected subsets of data or missing entries. Use these parameters carefully to navigate through paged results.

Links and References

Discussion