Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with a firewall system to retrieve license information. It is designed to query the firewall's license data based on various filtering and pagination parameters. This can be useful in scenarios where you need to monitor or audit firewall licenses, automate compliance checks, or integrate license data into broader IT management workflows.

For example, you might use this node to:

  • Fetch all active firewall licenses with specific conditions.
  • Retrieve a subset of licenses for reporting purposes by limiting and skipping records.
  • Order license data by certain fields to analyze usage trends.

Properties

Name Meaning
X USER ID User identifier required for authentication or API access headers.
Condition Query condition string to filter the license records returned by the API.
Skip Number of records to skip, used for pagination.
Limit Maximum number of records to return, used for pagination.
Order By Field(s) by which to order the returned license records.

Output

The node outputs JSON data representing the retrieved firewall license information. The structure of the JSON output corresponds to the license records returned by the firewall API, filtered and ordered according to the input properties.

If the API supports binary data (e.g., license files), it would typically be included as binary output, but based on the provided code and properties, this node primarily returns JSON data about licenses.

Dependencies

  • Requires an API key or token credential for authenticating with the firewall system.
  • Depends on the firewall API endpoint that supports querying license information with headers and query parameters.
  • No additional external libraries beyond standard n8n dependencies and the bundled OpenAPI client are explicitly required.

Troubleshooting

  • Missing or invalid X USER ID: The API requires a valid user ID header; ensure this property is set correctly.
  • Invalid query conditions: If the Condition parameter is malformed, the API may return errors or no results.
  • Pagination issues: Setting Skip or Limit incorrectly could result in empty responses or incomplete data.
  • Ordering errors: Using unsupported fields in Order By may cause the API to reject the request.
  • Authentication failures: Ensure the API key or token credential is configured properly in n8n.

Links and References

  • Refer to your firewall vendor’s API documentation for details on license retrieval endpoints, supported query parameters, and authentication methods.
  • n8n documentation on HTTP Request node for understanding how headers and query parameters are sent.
  • General best practices for API pagination and filtering.

Discussion