Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation updates the mapping settings for an agent's discovery configuration within a "Discovery Settings" resource. It is useful when you need to programmatically modify how an agent discovers or maps certain data or configurations in an automated workflow. For example, you might use this node to update user-specific discovery parameters or adjust the data mappings that an agent uses during its discovery process.

Properties

Name Meaning
X USER ID The user identifier header value sent with the request, representing the acting user.
Data JSON object containing the new discovery setting mapping data to be updated.
Id Numeric identifier of the specific discovery setting mapping to update.

Output

The node outputs JSON data representing the response from the API after attempting to update the agent discovery setting mapping. This typically includes confirmation of the update, any updated fields, or error information if the update 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 API service to perform the update operation.
  • The node uses the OpenAPI specification bundled internally to define and validate the operation.

Troubleshooting

  • Missing or invalid X USER ID: If the user ID header is not provided or incorrect, the API may reject the request. Ensure the "X USER ID" property is set correctly.
  • Invalid JSON in Data property: The "Data" field must be valid JSON. Malformed JSON will cause parsing errors before sending the request.
  • Incorrect Id value: The "Id" must correspond to an existing discovery setting mapping. Using an invalid or non-existent Id will result in an error from the API.
  • Authentication errors: Ensure the API key credential is configured properly; otherwise, the API will deny access.
  • API connectivity issues: Network problems or API downtime can cause failures; verify connectivity and API status.

Links and References

Discussion