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 "Asset Data" resource to retrieve asset metadata (Msdt). It is designed to query an external API endpoint that provides detailed information about assets based on specified conditions and pagination parameters. This node is useful in scenarios where users need to fetch filtered lists of asset data, such as inventory management, asset tracking, or reporting systems.
For example, a user might want to retrieve all assets belonging to a specific category or location, skip a certain number of records for pagination, limit the number of results returned, or order the results by a particular field.
Properties
| Name | Meaning |
|---|---|
| X USER ID | User Id header required for authentication or identification purposes in the API call. |
| Condition | Query condition string to filter the asset data results based on specific criteria. |
| Skip | Number of records to skip, used for pagination to offset the starting point of results. |
| Limit | Maximum number of records to return in the response, controlling page size. |
| Order By | Field name(s) to order the results by, allowing sorting of the returned asset data. |
Output
The node outputs JSON data containing the retrieved asset metadata matching the query parameters. The structure typically includes an array of asset objects with their respective fields as provided by the external API. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating requests to the Connect Secure API.
- Depends on the external Connect Secure API service to fetch asset metadata.
- No additional environment variables or configurations are explicitly required beyond the API credential.
Troubleshooting
- Missing or invalid X USER ID: If the "X USER ID" header is not provided or incorrect, the API may reject the request. Ensure this property is set correctly.
- Invalid query conditions: Malformed or unsupported query strings in the "Condition" property can cause errors or empty results. Validate the query syntax according to the API documentation.
- Pagination issues: Setting "Skip" or "Limit" to inappropriate values (e.g., negative numbers) may lead to unexpected behavior or errors.
- Ordering errors: Using invalid field names in "Order By" could result in API errors or unsorted data.
- API connectivity: Network issues or invalid API credentials will prevent successful data retrieval. Verify credentials and network access.
Links and References
- Refer to the Connect Secure API documentation for details on query syntax, supported fields, and authentication requirements.
- n8n documentation on how to configure API credentials and use HTTP headers in nodes.