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
Groups → Get Group Device Ids
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve device IDs associated with a specific group. It is useful in scenarios where you need to manage or analyze devices grouped under certain categories within NinjaOne, such as inventory management, monitoring, or automation workflows that depend on group membership.
For example, you might use this node to:
- Fetch all device IDs belonging to a particular group to perform batch operations.
- Integrate with other systems by exporting group device lists.
- Automate alerts or reports based on devices in specific groups.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the group for which to retrieve device IDs. This is a required numeric input. |
Output
The node outputs an array of JSON objects, each representing the response from the NinjaOne API for the requested group. The main output field json contains the data returned by the API call to fetch device IDs for the specified group.
The exact structure of the JSON depends on the NinjaOne API response but typically includes a list or collection of device identifiers associated with the group.
No binary data output is produced by this operation.
Dependencies
- Requires an active NinjaOne API OAuth2 authentication credential configured in n8n.
- Depends on network access to the NinjaOne API endpoint.
- Uses the NinjaOne API version 2 endpoints internally.
Troubleshooting
- Missing or invalid Group Id: Ensure the "Id" property is set correctly and corresponds to an existing group in NinjaOne.
- Authentication errors: Verify that the NinjaOne API credentials are valid and have sufficient permissions.
- API request failures: Network issues or NinjaOne service outages can cause errors; check connectivity and NinjaOne status.
- Error messages: If the node throws errors related to missing binary data, it indicates misuse of properties intended for other operations (not relevant here). For API errors, review the error message for HTTP status codes or details.
Links and References
- NinjaOne API Documentation (for detailed API endpoint info)
- n8n Documentation - Creating Nodes