Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Firewall Interfaces, is designed to fetch information about firewall interfaces from a Connect Secure API. It allows users to query and retrieve details about the network interfaces configured on a firewall device. This can be useful for network administrators or security engineers who want to automate monitoring, auditing, or managing firewall interface configurations within their workflows.

Practical examples include:

  • Automatically retrieving a list of firewall interfaces to verify configuration compliance.
  • Integrating firewall interface data into a broader network inventory system.
  • Triggering alerts or reports based on changes or specific conditions in firewall interfaces.

Properties

Name Meaning
X USER ID User Id required for authentication or identification in the API request header.
Condition Query condition string to filter the firewall interfaces returned by the API.
Skip Number of records to skip in the result set (used for pagination).
Limit Maximum number of records to return (used for pagination).
Order By Field name(s) to order the results by (e.g., interface name, creation date).

Output

The output of this operation is JSON data representing the retrieved firewall interfaces. Each item in the output array corresponds to a firewall interface with its associated properties as returned by the Connect Secure API.

If the API supports binary data for any interface-related content (e.g., configuration files or logs), it would be included in the binary output field, but based on the provided code and properties, the primary output is structured JSON data describing firewall interfaces.

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 X USER ID header must be supplied to identify the user making the request.
  • The node depends on the external Connect Secure API service being available and responsive.

Troubleshooting

  • Missing or invalid X USER ID: The API may reject requests without a valid user ID header. Ensure the "X USER ID" property is correctly set.
  • Invalid query parameters: Incorrect values in "Condition", "Skip", "Limit", or "Order By" may cause errors or unexpected results. Validate these inputs before execution.
  • API connectivity issues: Network problems or incorrect credentials will prevent successful retrieval. Verify API endpoint accessibility and credential validity.
  • Empty results: If no interfaces match the query condition, the output will be empty. Adjust the "Condition" or pagination parameters accordingly.

Links and References

Discussion