AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node is designed to update the agent discovery setting mapping within a system called "Discovery Settings." Specifically, it performs a PATCH operation to modify existing mappings related to agent discovery configurations. This can be useful in scenarios where you need to adjust or correct how agents are discovered or mapped dynamically without recreating the entire configuration.

Practical examples include:

  • Updating an agent's discovery parameters after changes in network topology.
  • Correcting or adding additional metadata fields to an existing discovery mapping.
  • Automating updates to discovery settings as part of a larger workflow managing infrastructure or security agents.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes in the request header.
Additional Body Fields Optional additional fields to include in the PATCH request body. Includes:
- Data: JSON object with arbitrary data to update.
- Id: Numeric identifier of the discovery setting mapping to update.

Output

The node outputs JSON data representing the response from the PATCH update operation on the agent discovery setting mapping. This typically includes confirmation of the updated resource, any changed fields, and status information returned by the API.

No binary data output is indicated or expected.

Dependencies

  • Requires an API key credential for authenticating requests to the AvantGuard ConnectSecure service.
  • Depends on the base URL configured in the credentials to target the correct API endpoint.
  • Uses the @avantguardllc/n8n-openapi-node package internally to build and send requests based on OpenAPI specifications.

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 this field is correctly set.
  • Invalid JSON in Additional Body Fields (Data): The data field expects valid JSON. Malformed JSON will cause parsing errors before sending the request.
  • Incorrect Id value: Providing an invalid or non-existent id may result in a "not found" or similar error from the API.
  • API connectivity issues: Verify that the base URL and API credentials are correctly configured and that the API service is reachable.
  • Permission errors: Ensure the authenticated user has rights to update discovery settings.

Links and References

Discussion