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 Suid permissions related to assets. It is designed to fetch permission data for a specific user, filtered and sorted according to various query parameters. This node is useful in scenarios where you need to programmatically access or audit user permissions on assets within an enterprise system, such as generating reports on user access rights or integrating permission checks into automated workflows.
Practical examples include:
- Retrieving all Suid permissions for a given user to verify their access levels.
- Filtering permissions based on specific conditions (e.g., asset type or status).
- Paginating results by skipping a number of records and limiting the output size.
- Ordering the retrieved permissions by specified fields.
Properties
| Name | Meaning |
|---|---|
| X USER ID | The User Id for whom Suid permissions are being retrieved. This is sent as a request header. |
| Condition | A query string condition to filter the Suid permissions returned by the API. |
| Skip | Number of records to skip in the result set, used for pagination. |
| Limit | Maximum number of records to return, used to limit the size of the response. |
| Order By | Field(s) by which to order the returned Suid permissions. |
Output
The node outputs JSON data representing the Suid permissions retrieved from the Connect Secure API. Each item in the output corresponds to a permission record associated with the specified user and filtered according to the input properties.
If binary data were involved, it would typically represent files or attachments related to permissions, but this node focuses solely on JSON permission data.
Dependencies
- Requires an API key credential for authenticating with the Connect Secure API.
- The node depends on the external Connect Secure API service being accessible.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
- Missing or invalid X USER ID: The node requires a valid user ID header; ensure this is provided and correctly formatted.
- API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Invalid query parameters: Conditions, skip, limit, and order_by must conform to the API's expected formats; incorrect values may cause errors or empty responses.
- Network issues: Connectivity problems to the Connect Secure API will prevent data retrieval; check network settings and API endpoint availability.
Common error messages might include unauthorized access, bad request due to malformed query parameters, or timeout errors. Resolving these involves checking credentials, validating input parameters, and ensuring stable network connectivity.
Links and References
- Connect Secure API documentation (refer to your organization's API docs for detailed usage)
- n8n documentation on HTTP Request nodes and API integrations for general guidance