Actions158
- System Actions
- Organization Actions
- Devices Actions
- Get Device
- Get Device Active Jobs
- Get Device Activities
- Get Device Alerts
- Get Device Disk Drives
- Get Device Installed OS Patches
- Get Device Installed Software Patches
- Get Device Last Logged On User
- Get Device Network Interfaces
- Get Device Pending Failed Rejected OS Patches
- Get Device Pending Failed Rejected Software Patches
- Get Device Processors
- Get Device Services
- Get Device Software
- Get Device Volumes
- Get Node Custom Fields
- Update Node Attribute Values
- Get Policy Overrides
- Groups Actions
- Queries Actions
- Get Antivirus Status Report
- Get Antivirus Threats
- Get Computer Systems
- Get Custom Fields Detailed Report
- Get Custom Fields Report
- Get Device Health Report
- Get Device Usage
- Get Disk Drives
- Get Installed OS Patches
- Get Installed Software Patches
- Get Last Logged On Users Report
- Get Network Interfaces
- Get Operating Systems
- Get Pending Failed Rejected OS Patches
- Get Pending Failed Rejected Software Patches
- Get Policy Overrides 1
- Get Processors
- Get RAID Controller Report
- Get RAID Drive Report
- Get Scoped Custom Fields Detailed Report
- Get Scoped Custom Fields Report
- Get Software
- Get Volumes
- Get Windows Services Report
- Management Actions
- Get Custom Fields Policy Conditions
- Create Custom Fields Policy Condition
- Get Windows Event Policy Conditions
- Create Windows Event Policy Condition
- Delete Policy Condition
- Get Custom Fields Policy Condition
- Get Windows Event Policy Condition
- Create Organization
- Node Approval Operation
- Reset Alert
- Reset Alert Set Activity Data
- Update Device Maintenance
- Cancel Device Maintenance
- Control Windows Service
- Update Device
- Get Device Link
- Reset Policy Overrides
- Reboot Devices
- Remove Device Owner
- Request Scripting Options
- Run Script On Device
- Set Device Owner
- Set Windows Service Configuration
- Submit OS Patch Apply
- Submit OS Patch Scan
- Submit Software Patch Apply
- Submit Software Patch Scan
- Create Location For Organization
- Get Installer
- Get Installer For Location
- Update Organization
- Update Location
- Update Node Role Policy Assignment For Organization
- Create Policy
- Ticketing Actions
- Webhooks Actions
- Related Items Actions
- Location Actions
- Backup Actions
- Knowledge Base Articles Actions
- Upload Temp Attachments
- Download Knowledge Base Article
- Get Client Knowledge Base Articles
- Get Global Knowledge Base Articles
- Get Knowledge Base Article Signed Urls
- Get Knowledge Base Folder Content
- Get Knowledge Base Folder Path Content
- Download Related Item Attachment
- Get Related Item Attachments Signed Urls
- Organization Documents Actions
- Document Templates Actions
- Checklist Templates Actions
- Custom Fields Actions
- Organization Checklists Actions
Queries → Get Last Logged On Users Report
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve various reports and data. Specifically, for the "Queries" resource with the "Get Last Logged On Users Report" operation, it fetches a report listing the most recent users logged onto devices managed by NinjaOne. This is useful for IT administrators who want to monitor user activity across their device fleet, audit access patterns, or troubleshoot login issues.
Practical examples include:
- Generating a list of last logged-on users per device to verify compliance.
- Tracking user logins over time for security audits.
- Integrating login data into dashboards or other reporting tools.
Properties
| Name | Meaning |
|---|---|
| Df | Device filter: a string used to filter the report by specific device criteria. |
| Cursor | Cursor name: a string used for pagination to continue fetching results from a previous call. |
| Page Size | Limit number of records per page: a number specifying how many records to return per request (default 1000). |
Output
The node outputs JSON data representing the last logged on users report retrieved from the NinjaOne API. The structure corresponds directly to the API response and typically includes details such as user names, device identifiers, timestamps of last login, and possibly additional metadata about the login events.
No binary data output is produced by this operation.
Dependencies
- Requires an active NinjaOne API OAuth2 credential configured in n8n for authentication.
- Depends on the NinjaOne API being accessible and the user having appropriate permissions to query reports.
- Uses the built-in HTTP request helper with authentication to communicate with the NinjaOne API.
Troubleshooting
Common Issues:
- Invalid or expired API credentials will cause authentication failures.
- Incorrect or unsupported filter values may result in empty responses or errors.
- Pagination cursors that are outdated or invalid can cause errors or no further data returned.
Error Messages:
- Errors from the NinjaOne API will be propagated; typical messages might include authorization errors, invalid parameters, or rate limiting notices.
- If binary data is expected but missing (not applicable here), the node throws an error indicating missing binary data.
Resolutions:
- Verify and refresh API credentials if authentication fails.
- Check filter and cursor values for correctness.
- Handle pagination carefully by using the cursor returned from previous calls.
Links and References
- NinjaOne API Documentation (general reference for endpoints and data structures)
- n8n Documentation on HTTP Request Node (for understanding request handling and authentication)