NinjaOneInstall

Overview

This node interacts with the NinjaOne API to retrieve alerts related to a specific device. It is designed to fetch device alert information by specifying the device identifier and optionally filtering or localizing the results using language and time zone parameters.

Common scenarios where this node is beneficial include:

• Monitoring device health and status by retrieving alerts generated for devices.
• Integrating device alert data into workflows for automated incident management or notification systems.
• Localizing alert information based on user language preferences and adjusting timestamps according to specified time zones.

For example, a user can configure the node to get all alerts for a device with ID 123, requesting the alerts in English and adjusted to the "America/New_York" time zone.

Properties

Output

The node outputs an array of JSON objects, each representing the response from the NinjaOne API containing device alert data. The structure of the json output field corresponds directly to the API's response for device alerts, typically including details such as alert type, severity, timestamp, message, and other relevant metadata.

No binary data output is produced by this operation.

Dependencies

• Requires an active connection to the NinjaOne API authenticated via an OAuth2 API key credential.
• The node depends on the NinjaOne API endpoint /v2/devices/{id}/alerts (inferred from the pattern in the code) to fetch device alerts.
• Proper configuration of the OAuth2 credentials within n8n is necessary for successful API requests.

Troubleshooting

• Missing or invalid device ID: Since the device ID is required, omitting it or providing an invalid number will cause the request to fail. Ensure the device ID is correct and exists in NinjaOne.
• Authentication errors: If the OAuth2 token is expired or misconfigured, the node will fail to authenticate. Refresh or reconfigure the API credentials.
• Invalid language or timezone values: Providing unsupported or incorrectly formatted language tags or time zone strings may result in unexpected API responses or errors.
• API rate limits or downtime: Temporary failures might occur due to NinjaOne API rate limiting or service outages. Implement retry logic or check NinjaOne service status if errors persist.
• Error messages: The node returns error messages from the API wrapped in the output JSON if "Continue On Fail" is enabled. Otherwise, it throws exceptions that halt execution.

Links and References

• NinjaOne API Documentation (general reference for endpoints and parameters)
• IANA Time Zone Database (for valid time zone strings)
• BCP 47 Language Tags (for valid language tag formats)