AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node operation allows users to create organization checklists within the AvantGuard NinjaOne platform. It is useful for automating the creation of structured checklists that can include descriptions and tasks, helping teams standardize processes or audits across an organization. For example, a user might create a checklist for onboarding new employees or for routine IT maintenance tasks.

Properties

Name Meaning
Additional Body Fields Optional JSON fields to customize the checklist creation request body. This includes properties like description (text describing the checklist) and tasks (an array of task objects each with their own description). The JSON structure must be valid and follows the format:
json { "description": {}, "tasks": [ { "description": {} } ] }

Output

The node outputs JSON data representing the newly created organization checklist as returned by the API. This typically includes details such as the checklist ID, description, tasks, and any metadata provided by the service. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard NinjaOne platform.
  • The base URL for the API is configured via credentials.
  • The node uses the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled internally to build requests.

Troubleshooting

  • Invalid JSON in Additional Body Fields: If the JSON provided in the "Additional Body Fields" property is malformed, the node will likely throw a parsing error. Ensure the JSON syntax is correct before execution.
  • Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Verify that the API key and base URL are correctly set in the node credentials.
  • API Request Failures: Network issues or invalid request bodies may result in errors from the API. Check the structure of the JSON body and ensure required fields are included.
  • Empty or Missing Required Fields: Since the body is customizable, omitting necessary fields expected by the API could cause errors. Refer to the API documentation for mandatory fields when creating checklists.

Links and References

Discussion