AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node integrates with the AvantGuard NinjaOne API to create a related item linked to a specified entity within the system. It is useful for scenarios where you want to programmatically associate additional data or files with existing entities such as organizations, documents, locations, nodes, checklists, or knowledge base documents. For example, you might use this node to attach a new document or file to an organization record or link a checklist to a specific location.

Properties

Name Meaning
Entity Type The type of entity to which the related item will be attached. Options: ORGANIZATION, DOCUMENT, LOCATION, NODE, CHECKLIST, KB DOCUMENT.
Entity Id The unique numeric identifier of the entity to which the related item will be linked.
Additional Body Fields Optional JSON fields to include in the request body, such as file metadata or content details. This allows adding complex nested data structures describing the related item’s file or other attributes.

Output

The node outputs JSON data representing the response from the AvantGuard NinjaOne API after creating the related item. This typically includes confirmation details about the newly created related item, such as its ID and any metadata returned by the API. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard NinjaOne API.
  • The node uses the base URL provided in the credentials to send requests.
  • Depends on the @avantguardllc/n8n-openapi-node package and the OpenAPI specification bundled as openapi.json for request construction.

Troubleshooting

  • Common issues:

    • Invalid or missing entity ID or entity type may cause the API to reject the request.
    • Improperly formatted JSON in the "Additional Body Fields" can lead to request failures.
    • Network or authentication errors if the API key or base URL is incorrect or expired.
  • Error messages:

    • Authentication errors usually indicate invalid API credentials; verify and update the API key.
    • Validation errors from the API often point to missing required fields like entityId or entityType.
    • JSON parsing errors suggest malformed input in the additional fields; ensure valid JSON syntax.

Links and References

Discussion