Actions32
- Device Actions
- Control Windows Service
- Get
- Get Activities
- Get Alerts
- Get Custom Fields
- Get Dashboard URL
- Get Disks
- Get Jobs
- Get Last Logged On User
- Get Many
- Get Network Interfaces
- Get OS Patch Installs
- Get OS Patches
- Get Policy Overrides
- Get Processors
- Get Software
- Get Software Patch Installs
- Get Software Patches
- Get Volumes
- Get Windows Services
- Reboot Device
- Run Script
- Update Custom Fields
- Ticket Actions
- Organization Actions
Ticket → Get Many
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve multiple tickets based on specified criteria. It is useful for scenarios where users need to fetch a list of tickets, such as for reporting, monitoring, or further processing in automation workflows. For example, a user might want to get all tickets created within a certain date range or limit the number of tickets retrieved for performance reasons.
Use Case Examples
- Retrieve up to 50 tickets created after a specific start date.
- Fetch tickets with pagination using offset and limit parameters.
Properties
| Name | Meaning |
|---|---|
| Limit | Maximum number of ticket results to return. Helps control the volume of data fetched in one request. |
| Offset | Starting point offset for fetching tickets. Useful for pagination to skip a number of tickets. |
| Start Date | Filter to return tickets created at or after this date. Used to narrow down results by creation time. |
| End Date | Filter to return tickets created up to this date. Used to limit results by creation time. |
| Request Options | Additional request settings such as batching, SSL certificate validation, proxy configuration, and timeout settings to customize the API request behavior. |
Output
JSON
id- Unique identifier of the ticket.title- Title or summary of the ticket.status- Current status of the ticket.createdAt- Timestamp when the ticket was created.updatedAt- Timestamp when the ticket was last updated.assignedTo- User or team assigned to the ticket.priority- Priority level of the ticket.
Dependencies
- NinjaOne API access with OAuth2 credentials
Troubleshooting
- Ensure the OAuth2 API credentials are correctly configured and have the necessary permissions to access ticket data.
- Check that the base URL for the NinjaOne API is correct and accessible from the environment where the node runs.
- If using batching, verify batch size and interval settings to avoid rate limiting or timeouts.
- If SSL issues occur, consider enabling the option to ignore SSL certificate validation, but be aware of security implications.
Links
- NinjaOne API Documentation - Official API documentation for NinjaOne, useful for understanding available endpoints and parameters.