Actions222
- Application Baseline Actions
- Attack Surface Actions
- Backup Software Actions
- EDR Actions
- Tags Actions
- PII Actions
- External Scan Actions
- Settings Actions
- Compliance Assessment Actions
- Reports Actions
- Compliance Actions
- Jobs Actions
- Active Directory Actions
- Retrieve Ad Roles
- Retrieve Ad User Licenses
- Retrieve Azure Licenses
- Retrieve Azure Ad Logs
- Retrieve Azure Secure Score
- Retrieve Ad Password Policies
- Retrieve Ad Groups View
- Retrieve Ad Ous View
- Retrieve Ad Gpos View
- Retrieve Ad Computers View
- Retrieve Ad Users View
- Retrieve Ad Domain Details
- Retrieve Ad Gpos Details
- Retrieve Get Ous Details
- Retrieve Get Groups Details
- Retrieve Ad Group Users
- Retrieve Ad Group Computers
- Retrieve Get User Details
- Retrieve Get Computer Details
- Retrieve Ad Roles Details
- Retrieve Ad Roles Member
- Retrieve Ad Basic Info
- Audit Log Actions
- Ad Audit Actions
- Asset Data Actions
- Retrieve Bios Info
- Retrieve Bio Info
- Retrieve Browser Extensions
- Retrieve Browser Extension
- Retrieve Ciphers View
- Retrieve Cipher View
- Retrieve Windows Protection Status
- Retrieve Window Protection Status
- Retrieve Asset Compliance Report Card
- Retrieve Asset Firewall Policy
- Retrieve Asset Installed Drivers
- Retrieve Asset Installed Driver
- Retrieve Asset Interface
- Retrieve Asset Msdt
- Retrieve Asset Ports
- Retrieve Asset Port
- Retrieve Asset Security Report Data
- Retrieve Asset Security Report Datum
- Retrieve Asset Shares
- Retrieve Asset Share
- Retrieve Asset Storages
- Retrieve Asset Storage
- Retrieve Asset Unqouted Services
- Retrieve Asset Unqouted Service
- Retrieve Asset User Shares
- Retrieve Asset User Share
- Retrieve Asset Video Info
- Retrieve Asset Windows Reboot Required
- Retrieve Asset Window Reboot Required
- Vulnerabilities Actions
- Firewall Actions
- Integration Actions
- Retrieve Integration Credentials
- Retrieve Integration Credential
- Create Integration Credential
- Update Integration Credential
- Delete Integration Credential
- Retrieve Integration Rules
- Retrieve Integration Rule
- Create Integration Rule
- Update Integration Rule
- Delete Integration Rule
- Retrieve Company Mappings
- Retrieve Company Mapping
- Create Company Mapping
- Update Company Mapping
- Delete Company Mapping
- Event Set Actions
- Ticket Template Actions
- Scheduler Actions
- Credentials Actions
- Asset Actions
- Retrieve Records
- Retrieve Assets
- Retrieve Asset
- Create Asset
- Update Asset
- Delete Asset
- Retrieve Asset Stats
- Retrieve Asset Stat
- Retrieve Asset View
- Retrieve Cron Jobs
- Retrieve Kernel Modules
- Retrieve Suid Permissions
- Retrieve Ufw Firewall Rules
- Retrieve Selinux Settings
- Retrieve Asset Iptables Rules
- Retrieve Asset Users
- Retrieve Asset Processes Running
- Retrieve Asset Services
- Retrieve Asset Patches Info
- Retrieve Asset Firewall Rules
- Retrieve Asset Registry Misconfiguration
- Retrieve Asset Open Ports
- Retrieve Notification Tickets View
- Retrieve System Events View
- Discovery Settings Actions
- Retrieve Discovery Settings
- Retrieve Discovery Setting
- Create Discovery Setting
- Update Discovery Setting
- Delete Discovery Setting
- Retrieve Agent Discoverysettings Mapping
- Retrieve Agent Discoverysetting Mapping
- Create Agent Discoverysetting Mapping
- Update Agent Discoverysetting Mapping
- Delete Agent Discoverysetting Mapping
- Auth Actions
- Company Actions
- Agent Actions
Overview
This node interacts with the Connect Secure API to update PII (Personally Identifiable Information) scan settings. It allows users to modify configurations related to scanning for sensitive data, such as which scan settings to apply, path settings, allowed file extensions, and associated agent IDs. This is useful in scenarios where organizations need to manage or customize their data privacy scans dynamically, ensuring compliance with data protection regulations.
Practical examples include:
- Updating scan parameters to include new file types or directories.
- Adjusting agent assignments responsible for scanning specific data sets.
- Modifying allowed extensions to control which files are scanned for PII.
Properties
| Name | Meaning |
|---|---|
| X USER ID | User identifier required for authentication or tracking of the request. |
| Data | JSON object containing the scan configuration details: scan_settings, path_settings, allowed_extension_types, and agent_ids. Each is expected to be an array encoded as a JSON string. |
| Id | Numeric identifier representing the specific PII scan setting record to update. |
Output
The node outputs JSON data reflecting the response from the Connect Secure API after updating the PII scan settings. The exact structure depends on the API's response but typically includes confirmation of the updated settings or error information if the update failed.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Connect Secure API.
- The node uses the Connect Secure API endpoint defined in its internal OpenAPI specification.
- Proper configuration of the API credentials within n8n is necessary for successful operation.
Troubleshooting
Common issues:
- Missing or invalid
X USER IDheader may cause authentication failures. - Malformed JSON in the
Dataproperty can lead to request errors. - Providing an incorrect or non-existent
Idmay result in "not found" or update failure responses.
- Missing or invalid
Error messages:
- Authentication errors typically indicate missing or invalid user identification or API credentials.
- Validation errors may arise if the JSON structure in
Datadoes not conform to expected schema. - API errors related to the
Idusually mean the specified scan setting does not exist.
To resolve these:
- Ensure the
X USER IDis correctly set and valid. - Validate the JSON format and content of the
Dataproperty before execution. - Confirm that the
Idcorresponds to an existing scan setting.
Links and References
- Connect Secure API documentation (refer to your organization's API docs for detailed endpoints and schemas).
- n8n documentation on using HTTP Request nodes and handling JSON data.