AvantGuard - NinjaOne

Actions159

Overview

The node is designed to update an existing organization within a management system. It allows users to modify various attributes of an organization such as its name, description, approval mode for devices, tags, and custom fields. This node is useful in scenarios where organizational details need to be kept current or adjusted based on evolving business requirements. For example, if an organization's description changes or new tags need to be added for categorization, this node facilitates those updates programmatically.

Properties

Name	Meaning
Id	The unique identifier of the organization to update (required).
Additional Body Fields	Optional additional fields to update on the organization:
- Name	Full name of the organization.
- Description	A textual description of the organization.
- User Data	Custom attributes provided as JSON to store additional metadata about the organization.
- Node Approval Mode	Device approval mode with options: AUTOMATIC, MANUAL, REJECT.
- Tags	JSON array of tags associated with the organization.
- Fields	JSON object representing custom fields for the organization.

Output

The node outputs JSON data representing the updated organization object after the update operation completes successfully. This output typically includes all the organization's properties reflecting the latest state post-update. There is no indication that the node outputs binary data.

Dependencies

Requires an API key credential for authentication to the AvantGuard NinjaOne service.
The base URL for the API must be configured in the node credentials.
Uses the @avantguardllc/n8n-openapi-node package internally to build and execute requests against the NinjaOne API.

Troubleshooting

Common Issues:
- Providing an invalid or non-existent organization Id will likely result in an error from the API indicating the resource was not found.
- Malformed JSON in the "User Data", "Tags", or "Fields" properties can cause parsing errors.
- Missing required authentication credentials will prevent the node from connecting to the API.
Error Messages:
- Errors related to authorization usually indicate missing or incorrect API keys; verify credentials configuration.
- Validation errors from the API may occur if required fields are missing or contain invalid values; ensure the "Id" is set and optional fields conform to expected formats.
- JSON parsing errors suggest that the input JSON strings are not well-formed; validate JSON syntax before execution.

Links and References

AvantGuard NinjaOne API Documentation (general reference for API endpoints and data models)
n8n Documentation for guidance on using nodes and managing credentials