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
Device → Approve / Reject
AI-generatedSummary
Approve or reject one or more NinjaOne devices by posting their IDs to the selected approval endpoint. Choose the mode and provide device IDs as a comma-separated list; the node parses them into numbers and returns the API response.
Inputs
- Authentication (required) — Select OAuth2 (default) or Client Credentials and configure the matching NinjaOne credentials.
- Mode — Choose Approve (default) or Reject.
- Device IDs (required) — Comma-separated device IDs to process, for example
123,456.
Output shape
One item containing the API response, or a success object if the response has no body.
The node sends a POST request with the parsed IDs in a
devicesarray. If continuing on failure is enabled, an error item is returned for the affected input item.