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 retrieve custom profile data from an external scanning service. Specifically, the "Retrieve Custom Profile" operation fetches user profile information based on various query parameters such as user ID, filtering conditions, pagination controls, and sorting preferences.
Typical use cases include:
- Fetching detailed user profiles for security or compliance audits.
- Integrating user profile data into workflows that require enriched user context.
- Querying large datasets with filtering, skipping, limiting, and ordering capabilities to manage data volume efficiently.
For example, a security analyst might use this node to retrieve profiles of users who meet certain risk criteria, skip already processed records, limit the number of results per request, and order them by last login time.
Properties
| Name | Meaning |
|---|---|
| X USER ID | The User ID header value used to identify the user whose custom profile is being retrieved. This is required. |
| Condition | A query string to filter the profiles based on specific conditions (e.g., status, attributes). |
| Skip | Number of records to skip in the result set, useful for pagination. |
| Limit | Maximum number of records to return, controlling the size of the response. |
| Order By | Field name(s) to order the results by, allowing sorted output (e.g., "createdAt DESC"). |
Output
The node outputs JSON data representing the retrieved custom profiles matching the specified query parameters. Each item in the output corresponds to a user profile object returned by the external scan service.
If the API supports binary data (not indicated here), it would typically represent attachments or files related to the profiles, but this node focuses on JSON profile data only.
Dependencies
- Requires an API key credential for authenticating with the Connect Secure API.
- Depends on the external Connect Secure service being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
- Missing or invalid X USER ID: Since the user ID header is required, omitting it or providing an incorrect value will likely cause authentication or authorization errors. Ensure the correct user ID is provided.
- Invalid query parameters: Incorrectly formatted
condition,skip,limit, ororder_byvalues may lead to API errors or empty responses. Validate these inputs before execution. - API connectivity issues: Network problems or misconfigured credentials can cause failures. Verify API endpoint accessibility and credential validity.
- Pagination mishandling: Using
skipandlimitincorrectly might result in missing or duplicated data across multiple requests. Use consistent pagination logic.
Links and References
- Connect Secure API Documentation (replace with actual URL)
- n8n documentation on HTTP Request Node for understanding routing and headers usage.
- General best practices for API pagination and filtering.
Note: The summary is based solely on static analysis of the provided source code and property definitions.