Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve a specific mapping related to agent discovery settings. It is designed to fetch detailed configuration or mapping information for an agent's discovery setting by its unique identifier. This can be useful in scenarios where you need to programmatically access or audit discovery configurations within a secure environment, such as automated compliance checks, integration with other systems, or dynamic configuration management.

For example, you might use this node to:

  • Retrieve the discovery setting mapping of a particular agent before performing further automated actions.
  • Integrate discovery setting data into dashboards or reporting tools.
  • Validate or synchronize discovery settings across multiple environments.

Properties

Name Meaning
X USER ID User Id header value required for authentication or identification in the API request.
Id Numeric identifier of the specific agent discovery setting mapping to retrieve.

Output

The node outputs JSON data representing the retrieved agent discovery setting mapping. The structure of this JSON corresponds to the API response for the requested discovery setting identified by the provided Id. This typically includes all relevant fields and metadata describing the mapping configuration.

If the API supports binary data (not indicated here), it would be summarized accordingly, but based on the code and properties, the output is purely JSON.

Dependencies

  • Requires an active connection to the Connect Secure API.
  • Requires an API authentication token or credential configured in n8n (referred generically as "an API key credential").
  • The user must provide a valid X USER ID header value for the API call.
  • The node depends on the bundled OpenAPI specification (openapi.json) and uses an OpenAPI client library to perform the request.

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 an incorrect or non-existent discovery setting ID will likely result in an error or empty response.
  • Authentication errors: If the API credentials are missing or invalid, the node will fail to authenticate.
  • Network issues: Connectivity problems to the Connect Secure API endpoint will cause execution failures.
  • API changes: If the Connect Secure API changes its schema or endpoints, the node may require updates to the OpenAPI spec or implementation.

Links and References

Discussion