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 Documents → Create Organization Documents
AI-generatedOverview
This node enables creating organization documents within the NinjaOne platform by sending a custom JSON body to the corresponding API endpoint. It is useful when you want to programmatically add or upload documents related to an organization, allowing automation of document management workflows such as adding policies, reports, or other organizational files.
Practical examples include:
- Automatically uploading compliance documents for an organization after generating them.
- Adding new policy documents to an organization's profile based on external triggers.
- Integrating with other systems to keep organizational documentation up-to-date without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Body | A JSON object representing the content and metadata of the organization document to be created. This JSON is sent as the request body to the API. Users must provide valid JSON that matches the expected schema for organization documents in NinjaOne. |
Output
The node outputs a JSON object containing the response from the NinjaOne API after attempting to create the organization document. This typically includes details about the newly created document such as its ID, status, and any metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the NinjaOne API using OAuth2 authentication.
- The node depends on the NinjaOne API being accessible and the user having appropriate permissions to create organization documents.
- Proper configuration of the OAuth2 credential in n8n is necessary for authentication.
Troubleshooting
- Invalid JSON in Body: If the JSON provided in the "Body" property is malformed or does not conform to the expected schema, the API may return an error. Ensure the JSON is valid and correctly structured.
- Authentication Errors: If the OAuth2 credentials are missing, expired, or invalid, the node will fail to authenticate. Reconfigure or refresh the credentials.
- API Permission Issues: Lack of sufficient permissions to create documents in the organization can cause errors. Verify user roles and permissions in NinjaOne.
- Network or API Downtime: Connectivity issues or NinjaOne API downtime will result in request failures. Check network connectivity and NinjaOne service status.
Common error messages might include:
- "Unauthorized" or "Authentication failed": Indicates issues with the OAuth2 token.
- "Bad Request": Usually due to invalid JSON or missing required fields.
- "Forbidden": Insufficient permissions.
- "Internal Server Error": Temporary server-side issues; retry later.
Links and References
- NinjaOne API Documentation (for detailed API schema and examples)
- n8n OAuth2 Credential Setup Guide