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
Management → Get Device Link
AI-generatedOverview
This node integrates with the NinjaOne API to retrieve a direct link related to a specific device managed within the NinjaOne platform. The "Get Device Link" operation under the "Management" resource fetches a URL or redirect response that can be used to access or reference the device externally.
Typical use cases include:
- Automating workflows where you need to obtain a device-specific link for reporting, notifications, or further processing.
- Integrating NinjaOne device management into broader IT automation pipelines.
- Quickly retrieving device URLs to embed in dashboards or alerts.
For example, you might use this node to get a direct link to a device's management page and send it via email or chat to a technician.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the device for which the link is requested (number). |
| Redirect | Boolean flag indicating whether the response should return a redirect URL or not. |
- Id: Required. Specifies the device by its numeric ID.
- Redirect: Optional. If true, the API returns a redirect response; if false, it may return the link data directly.
Output
The node outputs an array of items, each containing a json object with the response from the NinjaOne API for the device link request.
- The
jsonfield typically contains the device link information or redirect details as returned by the API. - No binary data output is indicated for this operation.
Example output structure (simplified):
[
{
"json": {
"link": "https://ninjaone.example.com/device/12345",
"redirect": true
}
}
]
Dependencies
- Requires an active NinjaOne API OAuth2 credential configured in n8n for authentication.
- The node uses NinjaOne's REST API endpoints.
- Network connectivity to NinjaOne API endpoints is necessary.
Troubleshooting
- Missing or invalid device Id: Ensure the "Id" property is set correctly and corresponds to an existing device in NinjaOne.
- Authentication errors: Verify that the NinjaOne API credentials are valid and have sufficient permissions.
- API rate limits or downtime: Temporary failures may occur if NinjaOne API is unavailable or rate-limited.
- Binary data errors: Not applicable here since this operation does not handle binary data.
- Redirect handling: If the "Redirect" property is set incorrectly, the response may not be as expected. Adjust accordingly.
Common error messages will generally come from the NinjaOne API and should be handled by checking the error message included in the output when "Continue On Fail" is enabled.
Links and References
- NinjaOne API Documentation (general reference)
- n8n documentation on creating custom nodes