NinjaOne icon

NinjaOne

Consume NinjaOne API

Actions158

Checklist Templates → Get Checklist Templates

AI-generated

Overview

This node interacts with the NinjaOne API to retrieve checklist templates. Specifically, the "Get Checklist Templates" operation fetches checklist templates based on optional filtering criteria such as template IDs, template name, whether the template is required, and whether archived templates should be included.

Use cases include:

  • Automating retrieval of checklist templates for auditing or compliance workflows.
  • Integrating checklist templates into other systems or dashboards.
  • Filtering templates dynamically based on specific attributes like name or archival status.

For example, you might use this node to get all active (non-archived) required checklist templates whose names contain a certain keyword, then process or display them in your workflow.

Properties

Name Meaning
Checklist Template Ids Comma-separated string of checklist template IDs to filter the results by specific IDs.
Checklist Template Name String to filter checklist templates by their name.
Required Boolean flag to filter templates that are marked as required (true) or not (false).
Include Archived Boolean flag to include archived checklist templates (true) or exclude them (false).

Output

The node outputs an array of JSON objects, each representing a checklist template retrieved from the NinjaOne API. The exact structure depends on the API response but typically includes details such as template ID, name, required status, and archival status.

No binary data output is produced by this operation.

Dependencies

  • Requires an API authentication token credential configured in n8n to authenticate requests to the NinjaOne API.
  • The node uses the NinjaOne OAuth2 API credentials for authorization.
  • Network access to the NinjaOne API endpoint is necessary.

Troubleshooting

  • No Data Returned: If no checklist templates are returned, verify that the filter parameters (IDs, name, required, includeArchived) are correct and match existing templates.
  • Authentication Errors: Ensure the API key or OAuth2 credentials are valid and have sufficient permissions.
  • Invalid Property Values: Passing invalid or malformed values (e.g., non-string for IDs) may cause request failures.
  • Binary Data Errors: Not applicable here since this operation does not handle binary data.
  • API Rate Limits: If many requests are made in a short time, the API may throttle; consider adding delays or error handling for rate limits.

Links and References

Discussion