NinjaOne icon

NinjaOne

Consume NinjaOne API

Actions158

Organization Documents → Get Client Documents With Attribute Values

AI-generated

Overview

This node operation, Get Client Documents With Attribute Values under the Organization Documents resource, retrieves documents associated with client organizations from the NinjaOne API. It allows filtering and grouping of documents based on templates or organizations, enabling users to efficiently query and organize document data.

Common scenarios where this node is beneficial include:

  • Fetching all documents related to specific organizations for reporting or auditing.
  • Grouping documents by their template types to analyze usage patterns.
  • Searching documents by name or template attributes to locate specific files quickly.

For example, a user might want to get all documents grouped by their template for a set of organization IDs to generate a summary report of document types used across clients.

Properties

Name Meaning
Group By Determines how the results are grouped. Options: TEMPLATE (group by document template), ORGANIZATION (group by organization).
Organization Ids Comma-separated string of organization IDs to filter documents belonging to these organizations.
Template Ids Comma-separated string of template IDs to filter documents matching these templates.
Template Name Filter documents by the name of their template.
Document Name Filter documents by the document's name.

Output

The output is a JSON array where each item contains the response data from the NinjaOne API call corresponding to the requested documents. The structure depends on the API response but generally includes document metadata and attribute values grouped as specified.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API authentication token credential configured in n8n to authenticate requests against the NinjaOne API.
  • Uses the NinjaOne REST API endpoints to fetch organization document data.
  • No additional external dependencies beyond the NinjaOne API and n8n's HTTP request capabilities.

Troubleshooting

  • Empty or missing results: Ensure that the provided organization IDs, template IDs, or names are correct and exist in the NinjaOne system.
  • Authentication errors: Verify that the API key or OAuth2 credentials are valid and have sufficient permissions to access organization documents.
  • Invalid parameter format: Make sure that IDs are provided as comma-separated strings without extra spaces or invalid characters.
  • NodeOperationError about missing binary data: Not applicable here since this operation does not handle binary input.

Links and References

Discussion