Actions159
- Related Items Actions
- Backup Actions
- Queries Actions
- Get Disk Drives
- Get Operating Systems
- Get RAID Controller Report
- Get Volumes
- Get Computer Systems
- Get Antivirus Status Report
- Get Device Health Report
- Get Custom Fields Report
- Get Installed Software Patches
- Get Custom Fields Detailed Report
- Get Installed OS Patches
- Get Pending Failed Rejected OS Patches
- Get RAID Drive Report
- Get Windows Services Report
- Get Antivirus Threats
- Get Device Usage
- Get Network Interfaces
- Get Processors
- Get Software
- Get Last Logged On Users Report
- Get Policy Overrides 1
- Get Scoped Custom Fields Report
- Get Pending Failed Rejected Software Patches
- Get Scoped Custom Fields Detailed Report
- System Actions
- Knowledge Base Articles Actions
- Get Knowledge Base Article Signed Urls
- Get Related Item Attachments Signed Urls
- Download Knowledge Base Article
- Get Knowledge Base Folder Path Content
- Upload Temp Attachments
- Get Knowledge Base Folder Content
- Get Client Knowledge Base Articles
- Upload Knowledge Base Articles
- Get Global Knowledge Base Articles
- Download Related Item Attachment
- Organization Documents Actions
- Document Templates Actions
- Checklist Templates Actions
- Organization Checklists Actions
- Location Actions
- Management Actions
- Get Custom Fields Policy Condition
- Delete Policy Condition
- Reset Alert
- Update Device
- Request Scripting Options
- Submit OS Patch Scan
- Get Installer For Location
- Get Windows Event Policy Conditions
- Create Organization
- Cancel Device Maintenance
- Reboot Devices
- Set Windows Service Configuration
- Create Location For Organization
- Update Node Role Policy Assignment For Organization
- Create Windows Event Policy Condition
- Node Approval Operation
- Control Windows Service
- Remove Device Owner
- Submit OS Patch Apply
- Get Installer
- Create Policy
- Get Windows Event Policy Condition
- Update Device Maintenance
- Reset Policy Overrides
- Set Device Owner
- Submit Software Patch Scan
- Update Location
- Reset Alert Set Activity Data
- Get Device Link
- Run Script On Device
- Submit Software Patch Apply
- Update Organization
- Create Custom Fields Policy Condition
- Get Custom Fields Policy Conditions
- Custom Fields Actions
- Ticketing Actions
- Organization Actions
- Devices Actions
- Get Device Active Jobs
- Get Device Installed Software Patches
- Get Device Processors
- Update Node Attribute Values
- Get Device Disk Drives
- Get Device Pending Failed Rejected OS Patches
- Get Device Volumes
- Get Device Alerts
- Get Device Network Interfaces
- Get Device Software
- Get Device Activities
- Get Device Last Logged On User
- Get Device Services
- Get Policy Overrides
- Get Device
- Get Device Installed OS Patches
- Get Device Pending Failed Rejected Software Patches
- Get Node Custom Fields
- Groups Actions
- Webhooks Actions
Overview
This node interacts with the AvantGuard NinjaOne API to retrieve information about devices managed within the system. Specifically, the "Get Device Last Logged On User" operation fetches details about the most recent user who logged onto a specified device. This can be useful in IT asset management scenarios where tracking user activity on devices is important for security audits, compliance, or troubleshooting.
Practical examples include:
- Identifying which user last accessed a particular workstation.
- Auditing device usage patterns by correlating devices and users.
- Supporting helpdesk operations by quickly finding the last user of a device when investigating issues.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the device for which to retrieve the last logged-on user. Must be provided as a number. |
Output
The node outputs JSON data containing details about the last user who logged onto the specified device. The exact structure depends on the API response but typically includes user identification fields such as username, user ID, login timestamp, and possibly additional metadata related to the login event.
If the node supports binary data output (not indicated here), it would represent any associated files or attachments related to the user or device login event.
Dependencies
- Requires an active connection to the AvantGuard NinjaOne API.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The base URL for the API must be set in the node's credential configuration.
Troubleshooting
- Missing or invalid device Id: Ensure that the "Id" property is provided and corresponds to a valid device in the system.
- Authentication errors: Verify that the API key or token is correctly configured and has sufficient permissions.
- Network or connectivity issues: Confirm that the base URL is reachable from the n8n environment.
- API rate limits or service downtime: Check the NinjaOne service status if requests fail repeatedly.
Common error messages might include unauthorized access, resource not found (if the device ID does not exist), or bad request due to malformed input.
Links and References
- AvantGuard NinjaOne API Documentation (general reference for API endpoints and authentication)
- n8n documentation on creating custom nodes