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 integrates with the AvantGuard NinjaOne API to retrieve reports about user login activity. Specifically, the "Get Last Logged On Users Report" operation fetches data on the most recent users who have logged into devices managed by NinjaOne. This is useful for IT administrators and security teams to monitor user access patterns, detect unusual login behavior, or generate audit logs.
Practical examples include:
- Generating a report of all users who logged in within a certain timeframe.
- Filtering login records by device type or other criteria.
- Paginating through large sets of login data for detailed analysis.
Properties
| Name | Meaning |
|---|---|
| Additional Query Parameters | Optional parameters to customize the query: - Df: Device filter (string) - Cursor: Cursor name for pagination (string) - Page Size: Limit number of records per page (number, default 1000) |
These parameters allow fine-tuning of the API request, such as filtering results by device, controlling pagination via cursor tokens, and limiting the number of returned records per call.
Output
The node outputs JSON data representing the last logged-on users report retrieved from the NinjaOne API. The structure typically includes user details, login timestamps, associated devices, and possibly metadata for pagination (like cursors).
If the API supports binary data (e.g., file exports), the node would handle it accordingly, but based on the provided code and operation, the output is primarily JSON-formatted report data.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard NinjaOne service.
- The base URL for the API must be configured in the node credentials.
- Depends on the
@avantguardllc/n8n-openapi-nodepackage for OpenAPI integration. - Uses the NinjaOne OpenAPI specification (
openapi.json) bundled with the node.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect or unsupported query parameters may result in API errors.
- Large datasets might require handling pagination properly using the cursor and page size parameters.
- Error messages:
- Authentication errors usually indicate invalid API keys or misconfigured credentials.
- API rate limits or timeouts can occur if too many requests are made in a short period; consider adding delays or reducing page size.
- If the response is empty or incomplete, verify that filters like device filter (
df) are correctly specified.
Links and References
- AvantGuard NinjaOne API Documentation (general reference for API endpoints and parameters)
- n8n OpenAPI Node Integration Guide (for understanding how OpenAPI-based nodes work)