Actions30
- Device Actions
- Ticket Actions
- Organization Actions
- Document Actions
Overview
The "Get Many" operation for the Ticket resource in this node allows users to retrieve multiple tickets from the NinjaOne platform. This operation is useful when you want to list tickets based on certain criteria such as creation date or pagination parameters like limit and offset.
Common scenarios include:
- Fetching a batch of recent tickets for reporting or monitoring.
- Retrieving tickets created within a specific date range for audit or analysis.
- Paginating through large sets of tickets to process them in chunks.
For example, you might use this operation to get the last 50 tickets created after January 1, 2024, to analyze recent support issues.
Properties
| Name | Meaning |
|---|---|
| Limit | Max number of results to return (minimum 1). |
| Offset | Offset to start retrieving results from (minimum 0). |
| Start Date | Return tickets created at or after this date (ISO 8601 datetime). |
| End Date | Return tickets created up to this date (ISO 8601 datetime). |
Output
The output contains a JSON array of ticket objects retrieved from the NinjaOne API. Each ticket object includes details such as ticket ID, subject, status, type, priority, creation date, and other relevant metadata depending on the API response.
No binary data output is associated with this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to access the NinjaOne API.
- The base URL for the API defaults to
https://api.ninjaone.combut can be overridden by credentials configuration.
Troubleshooting
- Empty results: If no tickets are returned, verify that the
Start DateandEnd Datefilters are correct and that tickets exist in that range. - Invalid limit or offset: Ensure that
Limitis at least 1 andOffsetis 0 or greater; otherwise, the API may reject the request. - Authentication errors: Confirm that the API key or OAuth2 credentials are valid and have sufficient permissions to read tickets.
- Date format issues: Use ISO 8601 format for
Start DateandEnd Dateto avoid parsing errors.
Links and References
- NinjaOne API Documentation (for detailed ticket schema and query parameters)
- n8n Documentation - Creating Custom Nodes