Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to create a mapping for an agent discovery setting. It is designed to send user-specific data to the API, enabling integration scenarios where automated configuration or synchronization of discovery settings is required. Typical use cases include automating network device discovery configurations or updating agent mappings in a secure environment based on dynamic input.

Properties

Name Meaning
X USER ID The User Id header value sent with the request; identifies the user making the request.
Data JSON object containing the body payload for creating the agent discovery setting mapping.

Output

The node outputs JSON data representing the response from the Connect Secure API after attempting to create the agent discovery setting mapping. This typically includes confirmation details of the created mapping or error information if the operation failed. There is no indication that binary data is output by this node.

Dependencies

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

Troubleshooting

  • Common issues:

    • Missing or invalid User Id header (X USER ID) can cause authentication or authorization failures.
    • Malformed JSON in the Data property may lead to request rejection.
    • Network connectivity problems or incorrect API credentials will prevent successful communication with the Connect Secure API.
  • Error messages:

    • Authentication errors typically indicate missing or incorrect API credentials or User Id.
    • Validation errors suggest issues with the structure or content of the JSON data sent.
    • Timeout or connection errors imply network issues or API endpoint unavailability.

To resolve these, ensure the User Id is correctly provided, the JSON data is valid, and the API credentials are properly configured in n8n.

Links and References

Discussion