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
User → Delete
AI-generatedSummary
Delete a NinjaOne user by ID by sending a DELETE request to /api/v2/user/{userId}. Select OAuth2 or Client Credentials authentication and provide the required User ID.
Inputs
- Authentication — Authentication method: OAuth2 (Authorization Code, default) or Client Credentials. Configure the matching NinjaOne credentials.
- User ID (required) — Numeric ID of the user to delete.
Output shape
One n8n item for each input item, containing the API response as JSON.
If the API returns no response body, the node emits
{"success":true}. API errors are thrown unless Continue On Fail is enabled; then an item with anerrorfield is emitted.