AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node operation allows users to create new checklist templates. Checklist templates are structured sets of tasks or items that can be reused for consistent workflows, inspections, or processes. This operation is useful in scenarios where standardized procedures need to be enforced or repeated, such as quality assurance, onboarding checklists, maintenance routines, or project task lists.

For example, a user might create a checklist template for equipment inspection with predefined tasks and descriptions, which can then be applied repeatedly across different assets or projects.

Properties

Name Meaning
Additional Body Fields Optional JSON fields to include in the request body when creating the checklist template. The default structure includes a description and an array of tasks, each with its own description. Users can customize this JSON to add more details or modify the checklist content.

The "Additional Body Fields" property expects a JSON object representing the checklist template's details, such as description and tasks. It allows flexible customization of the checklist template being created.

Output

The node outputs JSON data representing the response from the checklist template creation API. This typically includes details of the newly created checklist template, such as its unique identifier, description, tasks, and any metadata returned by the service.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authentication with the external service.
  • The node uses a base URL configured via credentials to send requests.
  • Depends on the external API endpoint for checklist template creation provided by the connected service.

Troubleshooting

  • Invalid JSON in Additional Body Fields: If the JSON provided in the "Additional Body Fields" 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 or token is correctly set up in the node credentials.
  • API Endpoint Issues: Network errors or incorrect base URL configuration can prevent successful requests. Confirm the base URL and network connectivity.
  • Missing Required Fields: If the checklist template requires mandatory fields not included in the additional body JSON, the API may reject the request. Review the API documentation to ensure all required fields are present.

Links and References

  • Refer to the external service’s API documentation for checklist templates to understand required fields and response structure.
  • JSON formatting guides to help construct valid JSON for the "Additional Body Fields".

Discussion