AvantGuard - ConnectSecureInstall

Overview

This node is designed to create a new agent discovery setting mapping within the "Discovery Settings" resource. It sends a POST request to an external API endpoint to register or configure discovery settings related to agents. This can be useful in scenarios where you need to programmatically manage or automate the configuration of agent discovery mappings, such as integrating with network management systems or security platforms that require dynamic updates to discovery settings.

Practical examples include:

• Automating the onboarding of new agents by creating their discovery settings automatically.
• Integrating with a larger workflow that manages network devices or security agents.
• Updating discovery configurations based on changes in your infrastructure or environment.

Properties

The X USER ID is passed as a header named X-USER-ID.
The Additional Body Fields allow adding custom JSON data to the request body, enabling flexibility for extra parameters supported by the API.

Output

The node outputs the JSON response returned from the API after creating the agent discovery setting mapping. The structure of this JSON depends on the external API's response but typically includes confirmation details about the created mapping, such as IDs, status, or any metadata returned by the service.

No binary data output is indicated in the source code.

Dependencies

• Requires an API key credential (referred generically) to authenticate requests to the external AvantGuard ConnectSecure API.
• The base URL for the API is configured via credentials.
• The node uses the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled with the node to build its properties and handle requests.

Troubleshooting

• Missing or invalid X USER ID header: The API may reject requests if the X-USER-ID header is missing or incorrect. Ensure this value is provided and valid.
• Invalid JSON in Additional Body Fields: If the JSON provided in the "Data" field is malformed, the request will fail. Validate JSON syntax before execution.
• Authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
• API endpoint errors: Network issues or incorrect base URL configuration can cause failures. Confirm the base URL and network connectivity.
• Unexpected API responses: Check the API documentation for required fields and expected response formats to ensure compatibility.

Links and References

• AvantGuard ConnectSecure API Documentation (hypothetical link)
• n8n HTTP Request Node Documentation (for understanding how headers and body are sent)
• JSON validation tools like JSONLint for verifying additional body fields input.