AvantGuard - NinjaOne

Actions159

Overview

The node implements the "Create Organization" operation under the "Management" resource for the AvantGuard NinjaOne API. It allows users to create a new organization within the system, optionally copying settings from an existing template organization. This is useful in scenarios where organizations need to be programmatically added with specific configurations, such as in IT management platforms or multi-tenant environments.

Practical examples include:

Automating onboarding of new client organizations with predefined settings.
Creating organizations with custom approval modes and policies.
Adding metadata like tags, locations, and custom fields during creation.

Properties

Name	Meaning
Additional Query Parameters	Optional query parameters that can be added to the request URL. Currently supports: • Template Organization Id: ID of a model/template organization to copy settings from.
Additional Body Fields	Optional body fields to customize the organization creation payload. Includes: • Name: Full name of the organization. • Description: Description of the organization. • User Data: Custom attributes as JSON. • Node Approval Mode: Device approval mode with options AUTOMATIC, MANUAL, REJECT. • Tags: List of tags as JSON. • Fields: Custom fields as JSON. • Locations: List of locations as JSON. • Policies: Node role policy assignments as JSON.

Name

Meaning

Additional Query Parameters

Optional query parameters that can be added to the request URL. Currently supports:
• Template Organization Id: ID of a model/template organization to copy settings from.

Additional Body Fields

Optional body fields to customize the organization creation payload. Includes:
• Name: Full name of the organization.
• Description: Description of the organization.
• User Data: Custom attributes as JSON.
• Node Approval Mode: Device approval mode with options AUTOMATIC, MANUAL, REJECT.
• Tags: List of tags as JSON.
• Fields: Custom fields as JSON.
• Locations: List of locations as JSON.
• Policies: Node role policy assignments as JSON.

Output

The node outputs JSON data representing the response from the API after creating the organization. This typically includes details about the newly created organization such as its ID, name, description, and any other metadata returned by the service.

There is no indication that the node outputs binary data.

Dependencies

Requires an API key credential for authenticating with the AvantGuard NinjaOne API.
The base URL for the API must be configured in the node credentials.
Uses standard HTTP headers for JSON content type and acceptance.

Troubleshooting

Common issues:
- Missing or invalid API authentication token will cause authorization errors.
- Providing malformed JSON in fields like userData, tags, fields, locations, or policies may result in parsing errors.
- Using an invalid templateOrganizationId could lead to failure in copying settings.
Error messages:
- Authorization errors typically indicate missing or incorrect API credentials.
- Validation errors may occur if required fields like name are empty or improperly formatted.
- JSON parsing errors suggest invalid JSON syntax in input properties; ensure proper formatting.

Links and References

AvantGuard NinjaOne API Documentation (generic link, replace with actual if available)
n8n documentation on HTTP Request node for understanding API calls
JSON formatting guides for preparing complex input fields