AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node integrates with the AvantGuard NinjaOne API to retrieve an installer package for a specified environment. It is useful in IT management scenarios where automated deployment or distribution of software agents is required across various operating systems and architectures. For example, an IT administrator can use this node to programmatically obtain the correct agent installer (e.g., Windows MSI, Mac DMG, Linux DEB) tailored to a specific organization or location, facilitating streamlined software rollout.

Properties

Name Meaning
Additional Body Fields Optional fields to customize the installer request:
- Organization Id Numeric identifier of the organization for which the installer is requested.
- Location Id Numeric identifier of the location within the organization.
- Installer Type The type of installer package to retrieve. Options include:
WINDOWS MSI, MAC DMG, MAC PKG, LINUX DEB, LINUX RPM, LINUX ARM 64 DEB, LINUX ARMV 7 A DEB,
LINUX ARM 64 RPM, LINUX ARMV 7 A RPM
- Usage Limit Numeric limit on how many times the installer can be used.
- Content JSON object specifying additional content details; by default includes "nodeRoleId": "auto".

Output

The node outputs JSON data representing the installer information retrieved from the API. This typically includes metadata about the installer package such as download URLs, version, and other relevant details needed to deploy the agent. There is no indication that binary data (such as the actual installer file) is output directly by the node.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard NinjaOne service.
  • The base URL for the API must be configured in the node credentials.
  • Uses the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled with the node for request construction.

Troubleshooting

  • Common issues:
    • Incorrect or missing API credentials will cause authentication failures.
    • Providing invalid or unsupported installer types may result in errors or empty responses.
    • Omitting required identifiers like organization or location IDs when they are necessary could lead to incomplete or failed requests.
  • Error messages:
    • Authentication errors typically indicate invalid API keys or misconfigured credentials.
    • Validation errors may occur if body fields do not conform to expected formats or values.
  • Resolution tips:
    • Verify API credentials and base URL configuration.
    • Ensure all required fields are correctly set according to the API documentation.
    • Use supported installer types exactly as listed in the options.

Links and References

Discussion