Actions159
- Related Items Actions
- Backup Actions
- Queries Actions
- Get Disk Drives
- Get Operating Systems
- Get RAID Controller Report
- Get Volumes
- Get Computer Systems
- Get Antivirus Status Report
- Get Device Health Report
- Get Custom Fields Report
- Get Installed Software Patches
- Get Custom Fields Detailed Report
- Get Installed OS Patches
- Get Pending Failed Rejected OS Patches
- Get RAID Drive Report
- Get Windows Services Report
- Get Antivirus Threats
- Get Device Usage
- Get Network Interfaces
- Get Processors
- Get Software
- Get Last Logged On Users Report
- Get Policy Overrides 1
- Get Scoped Custom Fields Report
- Get Pending Failed Rejected Software Patches
- Get Scoped Custom Fields Detailed Report
- System Actions
- Knowledge Base Articles Actions
- Get Knowledge Base Article Signed Urls
- Get Related Item Attachments Signed Urls
- Download Knowledge Base Article
- Get Knowledge Base Folder Path Content
- Upload Temp Attachments
- Get Knowledge Base Folder Content
- Get Client Knowledge Base Articles
- Upload Knowledge Base Articles
- Get Global Knowledge Base Articles
- Download Related Item Attachment
- Organization Documents Actions
- Document Templates Actions
- Checklist Templates Actions
- Organization Checklists Actions
- Location Actions
- Management Actions
- Get Custom Fields Policy Condition
- Delete Policy Condition
- Reset Alert
- Update Device
- Request Scripting Options
- Submit OS Patch Scan
- Get Installer For Location
- Get Windows Event Policy Conditions
- Create Organization
- Cancel Device Maintenance
- Reboot Devices
- Set Windows Service Configuration
- Create Location For Organization
- Update Node Role Policy Assignment For Organization
- Create Windows Event Policy Condition
- Node Approval Operation
- Control Windows Service
- Remove Device Owner
- Submit OS Patch Apply
- Get Installer
- Create Policy
- Get Windows Event Policy Condition
- Update Device Maintenance
- Reset Policy Overrides
- Set Device Owner
- Submit Software Patch Scan
- Update Location
- Reset Alert Set Activity Data
- Get Device Link
- Run Script On Device
- Submit Software Patch Apply
- Update Organization
- Create Custom Fields Policy Condition
- Get Custom Fields Policy Conditions
- Custom Fields Actions
- Ticketing Actions
- Organization Actions
- Devices Actions
- Get Device Active Jobs
- Get Device Installed Software Patches
- Get Device Processors
- Update Node Attribute Values
- Get Device Disk Drives
- Get Device Pending Failed Rejected OS Patches
- Get Device Volumes
- Get Device Alerts
- Get Device Network Interfaces
- Get Device Software
- Get Device Activities
- Get Device Last Logged On User
- Get Device Services
- Get Policy Overrides
- Get Device
- Get Device Installed OS Patches
- Get Device Pending Failed Rejected Software Patches
- Get Node Custom Fields
- Groups Actions
- Webhooks Actions
Overview
This node integrates with the AvantGuard NinjaOne system to retrieve alert information. Specifically, the "Get Alerts" operation under the "System" resource fetches alerts generated by the system, which can be useful for monitoring device or system health, security events, or other important notifications.
Typical use cases include:
- Automatically fetching and processing system alerts to trigger workflows based on specific alert types.
- Filtering alerts by source type, device, language, or time zone to tailor alert handling.
- Integrating alert data into dashboards or notification systems for real-time monitoring.
For example, a user might configure this node to pull all security-related alerts from a particular device and then send an email notification if any critical alerts are found.
Properties
| Name | Meaning |
|---|---|
| Additional Query Parameters | Optional filters and settings for the alert query. Includes: - Source Type: Filter alerts by their source. - Df: Filter alerts by device. - Lang: Specify language tag for alert messages. - Tz: Set the time zone context for alert timestamps. |
Output
The node outputs JSON data representing the alerts retrieved from the system. The structure typically includes details about each alert such as its source, associated device, timestamp (adjusted for the specified time zone), language, and other relevant metadata.
If the system supports binary data in alerts (e.g., attached logs or screenshots), the node would handle that accordingly, but based on the provided code and properties, the output is primarily JSON-formatted alert data.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard NinjaOne API.
- Needs the base URL of the NinjaOne API configured in the credentials.
- Depends on the
@avantguardllc/n8n-openapi-nodepackage for OpenAPI integration. - The node uses standard HTTP headers (
Accept: application/json,Content-Type: application/json) for requests.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Invalid filter values in additional query parameters may result in empty responses or errors.
- Network connectivity issues to the NinjaOne API endpoint can prevent data retrieval.
Error Messages:
- Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
- HTTP 400 errors may suggest malformed query parameters; check the spelling and format of filters.
- Timeout or connection errors require checking network access and API availability.
Links and References
- AvantGuard NinjaOne API Documentation (generic link, replace with actual if available)
- n8n OpenAPI Node Integration Guide