AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation retrieves PII (Personally Identifiable Information) scan settings from an external service. It is useful in scenarios where you need to programmatically fetch configuration or metadata related to how PII data scanning is set up, for example, to audit or review scan parameters, or to dynamically adjust workflows based on current scan settings.

Practical examples include:

  • Fetching the current PII scan configurations before running a data compliance check.
  • Integrating with a dashboard that displays PII scan settings for monitoring purposes.
  • Automating alerts or reports based on specific scan conditions or limits.

Properties

Name Meaning
X USER ID User Id - a required string header used to identify the user making the request.
Additional Query Parameters Optional query parameters to refine the retrieval:
- Condition: Query condition string to filter results.
- Skip: Number of records to skip (pagination).
- Limit: Maximum number of records to return.
- Order By: Field(s) to order the results by.

Output

The output will be JSON data representing the retrieved PII scan settings according to the specified query parameters and user context. The structure typically includes details about scan configurations such as filters, limits, ordering, and other metadata relevant to PII scans.

If the node supports binary data output, it would represent any associated files or attachments related to the scan settings, but this is not indicated in the provided code or properties.

Dependencies

  • Requires an API key or authentication token configured in n8n credentials to authorize requests to the external PII scan settings service.
  • The base URL for the API must be set 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 building request properties.

Troubleshooting

  • Missing or invalid X USER ID: Since the user ID header is required, omitting it or providing an incorrect value will likely cause authorization errors or empty responses.
  • Invalid query parameters: Providing unsupported or malformed query parameters may result in API errors or unexpected results.
  • Authentication failures: Ensure the API key or authentication token is correctly configured in n8n credentials.
  • Network issues: Connectivity problems to the external API endpoint can cause timeouts or failed requests.
  • Empty or unexpected response: Verify that the user ID has access rights and that the query parameters are correct.

Links and References

  • No direct links were found in the source code. For more information, consult the documentation of the external PII scanning service or the API reference corresponding to the OpenAPI spec used by this node.

Discussion