Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve information about a specific firewall zone. It is designed to fetch details of a firewall zone by its unique identifier, which can be useful in network security management scenarios where you need to programmatically access firewall configurations or audit firewall zones.

Practical examples include:

  • Automating retrieval of firewall zone details for compliance reporting.
  • Integrating firewall zone data into broader network monitoring workflows.
  • Fetching firewall zone information as part of a security incident response process.

Properties

Name Meaning
X USER ID User Id header value required for authentication or identification in the API request.
Id Numeric identifier of the firewall zone to retrieve.

Output

The node outputs JSON data representing the retrieved firewall zone details. The structure typically includes all relevant properties of the firewall zone as returned by the Connect Secure API, such as zone name, description, associated rules, and other metadata.

If the API supports binary data (e.g., configuration files or logs), it would be included in the binary output field; however, based on the provided code and properties, this node primarily outputs JSON data.

Dependencies

  • Requires an active connection to the Connect Secure API.
  • Needs an API key or token credential configured in n8n for authentication.
  • The X USER ID header must be supplied as part of the input properties to identify the user making the request.
  • The node depends on the bundled OpenAPI specification (openapi.json) and uses an OpenAPI client library to perform the API call.

Troubleshooting

  • Missing or invalid X USER ID: The API may reject requests without a valid user ID header. Ensure this property is correctly set.
  • Invalid Id value: Providing a non-existent or incorrect firewall zone ID will result in errors or empty responses. Verify the ID before execution.
  • Authentication errors: If the API key or token is missing or expired, the node will fail to authenticate. Check credentials configuration.
  • Network issues: Connectivity problems to the Connect Secure API endpoint will cause request failures. Confirm network access and endpoint availability.

Common error messages might include unauthorized access, resource not found, or bad request due to missing parameters. Resolving these involves verifying input values, credentials, and network connectivity.

Links and References

Discussion