AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation allows users to create a new PII (Personally Identifiable Information) scan setting by sending a POST request. It is useful in scenarios where you want to configure or update scanning parameters for identifying sensitive data within your systems or datasets. For example, an organization might use this node to define rules and settings that control how their data scanning agents detect and handle PII across various file paths and data sources.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking the request context.
Additional Body Fields Optional JSON fields to customize the scan settings, including:
- scan_settings: Array of scan configuration objects.
- path_settings: Array defining which paths to include or exclude in scans.
- allowed_extension_types: Array of file extensions allowed for scanning.
- agent_ids: Array of identifiers for agents that will perform the scan.

The "Additional Body Fields" property accepts a JSON string representing these arrays, allowing flexible customization of the scan settings.

Output

The node outputs the response from the API call as JSON in the json output field. This typically includes details about the created PII scan setting such as its ID, status, and the applied configuration. There is no indication that binary data is returned by this operation.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard ConnectSecure service.
  • Needs the base URL of the API endpoint configured in the node credentials.
  • The node depends on the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled with the node for request building.

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 header is correctly set.
  • Malformed JSON in Additional Body Fields: The data field expects valid JSON. Invalid JSON syntax will cause the request to fail. Validate JSON formatting before execution.
  • API connectivity issues: Verify that the base URL and API credentials are correctly configured and that the API service is reachable.
  • Unexpected API errors: Check the API response message for details. Common issues may relate to invalid scan settings or agent IDs.

Links and References

Discussion