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 group. It is designed to fetch details of a firewall group by its unique identifier, which can be useful in scenarios where you need to audit, monitor, or manage firewall configurations programmatically within an automation workflow.

Practical examples include:

  • Automatically retrieving firewall group details before applying changes.
  • Integrating firewall group data into reporting dashboards.
  • Validating firewall group existence and properties as part of security compliance checks.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes in the API request.
Id The unique numeric identifier of the firewall group to retrieve.

Output

The node outputs JSON data representing the retrieved firewall group details. This typically includes all relevant attributes of the firewall group as returned by the Connect Secure API, such as group name, rules, associated devices, and other metadata.

If the API supports binary data (e.g., configuration files or logs), the node would handle it accordingly, but based on the provided code and properties, the output focuses on JSON structured data.

Dependencies

  • Requires an active connection to the Connect Secure API.
  • Needs an API authentication token or key configured in n8n credentials (referred generically as "an API key credential").
  • The X USER ID header must be supplied to identify the user making the request.
  • The node depends on the bundled OpenAPI client library for Connect Secure 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 or non-existent firewall group Id: If the specified Id does not exist, the API will likely return an error or empty response. Verify the Id before running the node.
  • Authentication errors: Check that the API key credential is properly configured and has sufficient permissions.
  • Network issues: Ensure that the n8n instance can reach the Connect Secure API endpoint.
  • Unexpected API responses: Review the API documentation for any changes or additional required parameters.

Links and References

Discussion