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 operation, Retrieve Notification Tickets View under the Asset resource, is designed to fetch a filtered and paginated list of notification tickets from an external service's API. It allows users to specify query conditions, pagination controls (skip and limit), and sorting order to tailor the data retrieval according to their needs.
Typical use cases include:
- Monitoring or auditing notification tickets related to assets in an IT or asset management system.
- Integrating ticket views into workflows for automated processing or reporting.
- Fetching specific subsets of tickets based on dynamic conditions for further analysis or alerting.
For example, a user might retrieve all open notification tickets assigned to a particular user, skipping the first 10 records and limiting the output to 20 tickets, ordered by creation date.
Properties
| Name | Meaning |
|---|---|
| X USER ID | User identifier required for authentication or scoping the request. |
| Condition | Query condition string to filter the notification tickets (e.g., status='open'). |
| Skip | Number of records to skip for pagination purposes. |
| Limit | Maximum number of records to return. |
| Order By | Field(s) to order the results by (e.g., "created_at desc"). |
Output
The node outputs JSON data representing the retrieved notification tickets view. The structure typically includes an array of ticket objects with their respective fields as returned by the API. Each item corresponds to a notification ticket matching the query parameters.
If the API supports binary data for this operation, it would be included accordingly; however, based on the provided code and properties, the output is primarily JSON data containing ticket details.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to access the external Connect Secure API.
- Depends on the external Connect Secure API endpoint that provides the notification tickets view.
- The node uses HTTP headers and query parameters to communicate with the API, including passing the
X-USER-IDheader.
Troubleshooting
- Missing or invalid X USER ID: The API may reject requests without a valid user ID header. Ensure the
X USER IDproperty is correctly set. - Invalid query conditions: Malformed or unsupported query strings in the
Conditionproperty can cause errors or empty results. Validate the syntax according to the API documentation. - Pagination issues: Setting
SkiporLimitto inappropriate values (e.g., negative numbers) may lead to unexpected behavior or errors. - Order By errors: Using invalid field names in
Order Bycan result in API errors. Confirm supported fields for ordering. - Authentication failures: Ensure the API key or authentication credentials are properly configured in n8n.
Links and References
- Refer to the official Connect Secure API documentation for detailed information on query syntax, available fields, and authentication methods.
- n8n documentation on HTTP Request node for understanding how headers and query parameters are used.
- General best practices for pagination and filtering in REST APIs.