AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

The "Update Device" operation within the "Management" resource allows users to modify details of an existing device in their system. This node is useful for updating device metadata such as display name, user-defined data, assigned roles, policies, organizational context, location, and warranty information. Practical applications include maintaining accurate device inventories, assigning or changing device policies, updating organizational or locational assignments, and managing warranty details.

Properties

Name Meaning
Id Device identifier (number) - specifies which device to update.
Additional Body Fields Optional fields to update on the device:
- Display Name: User-assigned display name (string).
- User Data: Custom attributes in JSON format.
- Node Role Id: Identifier for the device's role (number).
- Policy Id: Assigned policy ID; overrides organization policy mapping or reverts if null (number).
- Organization Id: Identifier for the organization the device belongs to (number).
- Location Id: Identifier for the device's location (number).
- Warranty: Warranty information in JSON format.

Output

The node outputs JSON data representing the updated device object as returned by the API after the update operation. This typically includes all device properties reflecting the changes made. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authentication with the AvantGuard NinjaOne service.
  • The base URL for the API must be configured in the node credentials.
  • Uses the @avantguardllc/n8n-openapi-node package and a bundled OpenAPI specification (openapi.json) to define request structure and defaults.

Troubleshooting

  • Common Issues:
    • Providing an invalid or non-existent device Id will likely result in an error from the API indicating the device was not found.
    • Malformed JSON in the "User Data" or "Warranty" fields can cause parsing errors.
    • Omitting required authentication credentials or misconfiguring the base URL will prevent successful API calls.
  • Error Messages:
    • Errors related to missing or invalid device Id should prompt verification of the device identifier.
    • JSON parsing errors suggest checking the syntax of custom JSON fields.
    • Authentication errors indicate issues with API key setup or permissions.

Links and References

Discussion