Actions158
- System Actions
- Organization Actions
- Devices Actions
- Get Device
- Get Device Active Jobs
- Get Device Activities
- Get Device Alerts
- Get Device Disk Drives
- Get Device Installed OS Patches
- Get Device Installed Software Patches
- Get Device Last Logged On User
- Get Device Network Interfaces
- Get Device Pending Failed Rejected OS Patches
- Get Device Pending Failed Rejected Software Patches
- Get Device Processors
- Get Device Services
- Get Device Software
- Get Device Volumes
- Get Node Custom Fields
- Update Node Attribute Values
- Get Policy Overrides
- Groups Actions
- Queries Actions
- Get Antivirus Status Report
- Get Antivirus Threats
- Get Computer Systems
- Get Custom Fields Detailed Report
- Get Custom Fields Report
- Get Device Health Report
- Get Device Usage
- Get Disk Drives
- Get Installed OS Patches
- Get Installed Software Patches
- Get Last Logged On Users Report
- Get Network Interfaces
- Get Operating Systems
- Get Pending Failed Rejected OS Patches
- Get Pending Failed Rejected Software Patches
- Get Policy Overrides 1
- Get Processors
- Get RAID Controller Report
- Get RAID Drive Report
- Get Scoped Custom Fields Detailed Report
- Get Scoped Custom Fields Report
- Get Software
- Get Volumes
- Get Windows Services Report
- Management Actions
- Get Custom Fields Policy Conditions
- Create Custom Fields Policy Condition
- Get Windows Event Policy Conditions
- Create Windows Event Policy Condition
- Delete Policy Condition
- Get Custom Fields Policy Condition
- Get Windows Event Policy Condition
- Create Organization
- Node Approval Operation
- Reset Alert
- Reset Alert Set Activity Data
- Update Device Maintenance
- Cancel Device Maintenance
- Control Windows Service
- Update Device
- Get Device Link
- Reset Policy Overrides
- Reboot Devices
- Remove Device Owner
- Request Scripting Options
- Run Script On Device
- Set Device Owner
- Set Windows Service Configuration
- Submit OS Patch Apply
- Submit OS Patch Scan
- Submit Software Patch Apply
- Submit Software Patch Scan
- Create Location For Organization
- Get Installer
- Get Installer For Location
- Update Organization
- Update Location
- Update Node Role Policy Assignment For Organization
- Create Policy
- Ticketing Actions
- Webhooks Actions
- Related Items Actions
- Location Actions
- Backup Actions
- Knowledge Base Articles Actions
- Upload Temp Attachments
- Download Knowledge Base Article
- Get Client Knowledge Base Articles
- Get Global Knowledge Base Articles
- Get Knowledge Base Article Signed Urls
- Get Knowledge Base Folder Content
- Get Knowledge Base Folder Path Content
- Download Related Item Attachment
- Get Related Item Attachments Signed Urls
- Organization Documents Actions
- Document Templates Actions
- Checklist Templates Actions
- Custom Fields Actions
- Organization Checklists Actions
System → Get Alerts
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve system alerts based on specified filters. It is useful for monitoring and managing alerts generated by various sources within an IT environment managed by NinjaOne. For example, you can use this node to fetch alerts filtered by their source type, device, language, or time zone, enabling automated workflows that respond to specific alert conditions.
Properties
| Name | Meaning |
|---|---|
| Source Type | Filter alerts by their originating source type (e.g., hardware, software). |
| Df | Filter alerts by a specific device identifier. |
| Lang | Specify the language tag to localize alert information. |
| Tz | Define the time zone context for alert timestamps. |
Output
The node outputs an array of JSON objects, each representing an alert retrieved from the NinjaOne system. Each alert object contains details as provided by the NinjaOne API, such as alert metadata, source, device info, timestamps, and localized messages depending on the input parameters.
No binary data output is produced by this operation.
Dependencies
- Requires an active NinjaOne API OAuth2 authentication credential configured in n8n.
- The node uses NinjaOne's REST API endpoints to fetch alert data.
- No additional external dependencies are required beyond the NinjaOne API access.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing incorrect filter values (e.g., invalid device ID or unsupported source type) may result in empty responses or errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors returned from the NinjaOne API will be surfaced in the node’s output if "Continue On Fail" is enabled.
- Typical error messages include authentication errors, resource not found, or invalid query parameters.
Resolutions:
- Verify that the NinjaOne API credentials are correctly set up and have sufficient permissions.
- Double-check filter parameter values for correctness.
- Ensure network access to the NinjaOne API endpoint is available.
Links and References
- NinjaOne API Documentation (for detailed API usage and parameters)
- n8n Documentation (for general node usage and credential setup)