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
Webhooks → Configure Webhook
AI-generatedOverview
This node integrates with the NinjaOne API to configure webhooks for activity notifications. It allows users to set up a callback URL where NinjaOne will send event data based on specified activity filters. This is useful for automating workflows triggered by events in NinjaOne, such as device changes, alerts, or other monitored activities.
Typical use cases include:
- Automatically triggering downstream processes when specific activities occur in NinjaOne.
- Receiving real-time updates about monitored systems or policies.
- Customizing webhook payloads by expanding references or adding custom HTTP headers.
Properties
| Name | Meaning |
|---|---|
| Url | The callback (webhook) URL where activity notifications will be sent. |
| Activities | JSON object specifying which activities to filter and receive notifications for. |
| Expand | JSON array defining which references to expand in the webhook payloads for more detail. |
| Headers | JSON object containing custom HTTP headers (e.g., Authorization) to include in requests. |
Output
The node outputs an array of JSON objects representing the response from the NinjaOne API after configuring the webhook. Each output item contains a json field with the API response data confirming the webhook setup or providing details about the configured webhook.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token credential for NinjaOne (OAuth2 or similar).
- The node uses NinjaOne's REST API endpoints to configure webhooks.
- No additional environment variables are explicitly required beyond the API credentials.
Troubleshooting
- Missing or invalid URL: Ensure the "Url" property is a valid, reachable callback URL. Invalid URLs may cause webhook configuration failures.
- Malformed JSON in Activities, Expand, or Headers: These properties expect valid JSON strings. Syntax errors will cause parsing failures.
- Authentication errors: Verify that the provided API authentication token is valid and has sufficient permissions to configure webhooks.
- No binary data error: Not applicable here since this operation does not handle binary data.
- API request failures: Check network connectivity and NinjaOne API status if requests fail.
Links and References
- NinjaOne API Documentation (for detailed webhook configuration and activity filters)
- n8n Webhook Node Documentation (general webhook usage in n8n)