Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Pii Scan Settings, is designed to fetch configuration settings related to Personally Identifiable Information (PII) scanning from an external service. It allows users to query and retrieve details about how PII scans are configured, filtered, ordered, and paginated.

Common scenarios where this node would be beneficial include:

  • Auditing or reviewing current PII scan configurations in an organization.
  • Integrating PII scan settings retrieval into automated workflows for compliance reporting.
  • Dynamically adjusting or monitoring PII scan parameters based on retrieved settings.

For example, a user might want to retrieve all PII scan settings that match a certain condition (e.g., scans enabled for a specific department), skip the first 10 records, limit the results to 20, and order them by creation date.

Properties

Name Meaning
X USER ID User identifier required for authentication or context of the request.
Condition Query condition to filter the PII scan settings (e.g., filter expressions).
Skip Number of records to skip in the result set (used for pagination).
Limit Maximum number of records to return (used for pagination).
Order By Field(s) by which to order the returned PII scan settings.

Output

The output of this node consists of JSON data representing the retrieved PII scan settings. Each item in the output corresponds to a PII scan setting record matching the query parameters provided.

  • The json output field contains an array of objects with detailed information about each PII scan setting.
  • There is no indication that binary data is returned by this operation.

Dependencies

  • Requires an API key credential or similar authentication token to access the external Connect Secure API.
  • The node depends on the external Connect Secure API endpoint that provides PII scan settings.
  • Proper configuration of the API credentials within n8n is necessary for successful execution.

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 errors or failed requests.
  • Invalid query parameters: Providing malformed or unsupported values in condition, skip, limit, or order_by may result in errors or empty responses.
  • API connectivity issues: Network problems or incorrect API credentials can lead to request failures.
  • Empty results: If the query conditions do not match any records, the output will be empty; verify the correctness of the condition parameter.

To resolve these issues:

  • Ensure the X USER ID is correctly set and valid.
  • Validate query parameters against the API documentation.
  • Check network connectivity and API credential validity.
  • Adjust query filters to match existing data.

Links and References

Discussion