Actions120
- Alert Actions
- Backup Actions
- Custom Field Actions
- Device Actions
- Document Template Actions
- Group Actions
- Knowledge Base Article Actions
- Location Actions
- Organization Actions
- Organization Document Actions
- Query Actions
- Alerts
- Antivirus Status
- Antivirus Threats
- Backup Usage
- Computer Systems
- Custom Fields
- Custom Fields (Detailed)
- Device Health
- Disks
- Logged-On Users
- Network Interfaces
- Operating Systems
- OS Patch Installs
- OS Patches
- Policy Overrides
- Processors
- RAID Controllers
- RAID Drives
- Scoped Custom Fields
- Scoped Custom Fields (Detailed)
- Software
- Software Patch Installs
- Software Patches
- Volumes
- Windows Services
- Related Item Actions
- Software License Actions
- System Actions
- Get Activities
- Get Contacts
- Get Device Custom Fields
- Get Device Roles
- Get Devices (Detailed)
- Get End Users
- Get Jobs
- Get Locations
- Get Notification Channels
- Get Notification Channels (Enabled)
- Get Organizations (Detailed)
- Get Policies
- Get Scheduled Tasks
- Get Scripting Languages
- Get Scripts
- Get Software Products
- Get Technicians
- Get User Roles
- Ticketing Actions
- User Actions
- Webhook Actions
System → Get Activities
AI-generatedSummary
Fetches system activity records from NinjaOne’s /api/v2/activities endpoint. Use the filters to narrow the results; the operation makes one request and does not paginate automatically.
Inputs
- Authentication (required) — Choose OAuth2 (Authorization Code) or Client Credentials and configure the matching NinjaOne credentials.
- Filters — Optional activity filters: class, after and before Unix timestamps, language, olderThan, pageSize, seriesUid, sourceConfigUid, status, type, and user. Device filters can also narrow activities by approval status, device class, device ID, location ID, online status, organization ID, or role ID; IDs accept comma-separated values.
Output shape
A list of activity records, each returned as a separate n8n item; a non-list API response is returned as one item.
Filter values are sent as query parameters, except device filters, which are combined into NinjaOne’s
dfexpression. The request uses the supplied filters once; there is no automatic pagination.