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
Location → Update Node Attribute Values 2
AI-generatedOverview
This node integrates with the NinjaOne API to perform various operations on different resources. Specifically, for the Location resource and the Update Node Attribute Values 2 operation, it updates attributes of a node identified by given IDs. This is useful in IT management scenarios where you need to programmatically update location-related node attributes within NinjaOne, such as updating configuration or metadata tied to specific locations.
Practical examples include:
- Updating the attributes of a device or asset located at a particular site.
- Automating changes to location-specific settings across multiple nodes in an IT environment.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the node to update. Must be a number. |
| Location Id | The unique identifier of the location associated with the node. Must be a number. |
Output
The node outputs JSON data representing the response from the NinjaOne API after attempting to update the node attribute values. The structure depends on the API's response but generally includes confirmation of the update or details about the updated node attributes.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the NinjaOne API using OAuth2 authentication.
- The node expects the user to configure an API key credential (OAuth2) for authenticating requests.
- No additional external dependencies are required beyond the NinjaOne API access.
Troubleshooting
Common issues:
- Missing or invalid
IdorLocation Idparameters will cause the API request to fail. - Authentication errors if the OAuth2 credentials are not set up correctly.
- Network or API downtime can result in request failures.
- Missing or invalid
Error messages:
"No binary data exists on item!"or"No binary data property ... does not exist on item!"— These do not apply to this operation but appear in other operations; ignore for this context.- API error responses will be returned in the JSON output under an
errorfield if "Continue On Fail" is enabled.
Resolution:
- Ensure all required numeric IDs are provided and valid.
- Verify that the NinjaOne OAuth2 credentials are properly configured and authorized.
- Check network connectivity and NinjaOne service status.
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n documentation on Creating Custom Nodes