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
Organization → Get Node Custom Fields 1
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve custom fields associated with an Organization. Specifically, the "Get Node Custom Fields 1" operation fetches custom field data for a given organization by its identifier. This is useful in scenarios where you need to dynamically access or display additional metadata or custom attributes defined on organizations within NinjaOne.
Practical examples include:
- Automating workflows that require fetching organization-specific custom data for reporting or integration.
- Enriching organizational records in other systems by pulling custom fields from NinjaOne.
- Triggering conditional logic based on custom field values of organizations.
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric identifier of the Organization whose custom fields you want to retrieve. This is a required input. |
Output
The node outputs JSON data representing the custom fields of the specified Organization as returned by the NinjaOne API. The exact structure depends on the API response but generally includes key-value pairs or objects describing each custom field and its value.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the NinjaOne API using OAuth2 authentication.
- The node expects the NinjaOne API credentials to be configured in n8n.
- Network connectivity to the NinjaOne service endpoint is necessary.
Troubleshooting
- Missing or invalid Organization Id: Ensure the "Id" property is set correctly and corresponds to an existing organization in NinjaOne.
- Authentication errors: Verify that the NinjaOne API credentials are valid and have sufficient permissions to read organization custom fields.
- API request failures: Check network connectivity and NinjaOne API status. Review error messages returned by the API for details.
- No custom fields returned: It may indicate that no custom fields are defined for the specified organization.
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n OAuth2 Credential Setup (for configuring NinjaOne API credentials)