Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve mappings related to agent discovery settings. Specifically, it fetches the "Agent Discoverysettings Mapping" data, which can be used to understand or manage how agents are discovered and mapped within a secure environment.

Common scenarios for this node include:

  • Automating retrieval of agent discovery configurations for auditing or reporting.
  • Integrating discovery settings into workflows that require dynamic access to agent mappings.
  • Filtering and paginating discovery settings data based on specific conditions or ordering preferences.

For example, a user might want to retrieve all discovery settings where a certain condition applies, skip the first 10 records, limit the results to 50, and order them by a particular field.

Properties

Name Meaning
X USER ID User Id header required for authentication or identification in the API request.
Condition Query condition to filter the discovery settings data 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, allowing sorting of the returned data.

Output

The node outputs JSON data representing the retrieved agent discovery settings mapping from the Connect Secure API. The structure corresponds to the API's response format for these mappings, typically including details about each discovery setting entry.

If the API supports binary data, it is not indicated here; thus, the output is expected to be purely JSON.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the Connect Secure API being accessible and properly configured.
  • Uses the @devlikeapro/n8n-openapi-node package and OpenAPI specification (openapi.json) bundled with the node for request construction and parsing.

Troubleshooting

  • Missing or invalid X USER ID: Since the X USER ID header is required, omitting it or providing an incorrect value will likely cause authentication or authorization errors. Ensure the correct user ID is provided.
  • Invalid query parameters: Providing malformed or unsupported values in condition, skip, limit, or order_by may result in API errors or empty responses. Validate these inputs before execution.
  • API connectivity issues: Network problems or incorrect API credentials can cause failures. Verify network access and credential validity.
  • Pagination mishandling: Using skip and limit incorrectly might lead to unexpected subsets of data. Confirm pagination logic aligns with your use case.

Links and References

Discussion