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
Devices → Get Device Last Logged On User
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve information about devices and their associated data. Specifically, the "Get Device Last Logged On User" operation fetches details about the last user who logged onto a specified device. This is useful in IT management scenarios where administrators need to track device usage or audit user activity on endpoints.
Practical examples include:
- Identifying which user last accessed a particular workstation.
- Auditing device usage for security compliance.
- Integrating device-user data into broader asset management workflows.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the device for which to retrieve the last logged-on user. |
Output
The node outputs JSON data representing the last logged-on user information for the specified device. The exact structure depends on the NinjaOne API response but typically includes user details such as username, user ID, login timestamp, and possibly other metadata related to the login session.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the NinjaOne API.
- Needs an API authentication token configured via OAuth2 credentials within n8n.
- The node uses the NinjaOne OAuth2 credential type (configured externally) to authenticate requests.
Troubleshooting
Common issues:
- Invalid or missing device Id parameter will cause the API call to fail.
- Authentication errors if the OAuth2 token is expired or misconfigured.
- Network connectivity problems preventing access to the NinjaOne API endpoint.
Error messages:
"No binary data exists on item!"or similar are not relevant here since this operation does not handle binary data.- API error responses will be returned in the
json.errorfield if "Continue On Fail" is enabled.
Resolutions:
- Ensure the device Id is correctly provided and corresponds to an existing device.
- Verify that the NinjaOne OAuth2 credentials are valid and have necessary permissions.
- Check network settings and firewall rules to allow outbound API calls.
Links and References
- NinjaOne API Documentation (for detailed API endpoints and response formats)
- n8n OAuth2 Credential Setup (for configuring OAuth2 credentials in n8n)