Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve firewall policy data related to assets. Specifically, the "Retrieve Asset Firewall Policy" operation fetches firewall policies applied to assets based on user-defined query parameters such as conditions, pagination, and sorting. This node is useful in scenarios where you need to programmatically access or audit firewall policies for assets within a secure environment, enabling automation of security compliance checks or integration with other asset management workflows.

Practical examples include:

  • Fetching all firewall policies for a specific user or asset group.
  • Retrieving a limited set of firewall policies sorted by creation date.
  • Querying firewall policies that meet certain conditions (e.g., policies active within a date range).

Properties

Name Meaning
X USER ID User Id header value to identify the user making the request.
Condition Query condition string to filter the firewall policies returned by the API.
Skip Number of records to skip for pagination purposes.
Limit Maximum number of records to return.
Order By Field(s) by which to order the returned firewall policies.

Output

The node outputs JSON data representing the retrieved asset firewall policies. The structure typically includes an array of firewall policy objects matching the query parameters. Each object contains details about a specific firewall policy applied to an asset.

If binary data were involved (not indicated here), it would represent file contents or attachments related to the firewall policies, but this node focuses on JSON data output only.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the Connect Secure API being accessible and properly configured.
  • No additional external services are required beyond the Connect Secure API.

Troubleshooting

  • Common issues:

    • Missing or invalid user ID header (X USER ID) may cause authentication or authorization failures.
    • Incorrect query conditions can result in empty responses or errors from the API.
    • Pagination parameters (skip and limit) must be non-negative integers; invalid values might cause errors.
    • Network connectivity issues to the Connect Secure API endpoint.
  • Error messages:

    • Authentication errors indicating missing or invalid credentials: Ensure the API key credential is correctly set up.
    • Validation errors for query parameters: Verify that condition, skip, limit, and order_by values conform to expected formats.
    • API rate limiting or server errors: Retry after some time or check API usage limits.

Links and References

  • Connect Secure API documentation (refer to your organization's internal API docs or vendor-provided resources).
  • n8n documentation on creating and using HTTP Request nodes and custom API integrations.

Discussion