Actions159
- Related Items Actions
- Backup Actions
- Queries Actions
- Get Disk Drives
- Get Operating Systems
- Get RAID Controller Report
- Get Volumes
- Get Computer Systems
- Get Antivirus Status Report
- Get Device Health Report
- Get Custom Fields Report
- Get Installed Software Patches
- Get Custom Fields Detailed Report
- Get Installed OS Patches
- Get Pending Failed Rejected OS Patches
- Get RAID Drive Report
- Get Windows Services Report
- Get Antivirus Threats
- Get Device Usage
- Get Network Interfaces
- Get Processors
- Get Software
- Get Last Logged On Users Report
- Get Policy Overrides 1
- Get Scoped Custom Fields Report
- Get Pending Failed Rejected Software Patches
- Get Scoped Custom Fields Detailed Report
- System Actions
- Knowledge Base Articles Actions
- Get Knowledge Base Article Signed Urls
- Get Related Item Attachments Signed Urls
- Download Knowledge Base Article
- Get Knowledge Base Folder Path Content
- Upload Temp Attachments
- Get Knowledge Base Folder Content
- Get Client Knowledge Base Articles
- Upload Knowledge Base Articles
- Get Global Knowledge Base Articles
- Download Related Item Attachment
- Organization Documents Actions
- Document Templates Actions
- Checklist Templates Actions
- Organization Checklists Actions
- Location Actions
- Management Actions
- Get Custom Fields Policy Condition
- Delete Policy Condition
- Reset Alert
- Update Device
- Request Scripting Options
- Submit OS Patch Scan
- Get Installer For Location
- Get Windows Event Policy Conditions
- Create Organization
- Cancel Device Maintenance
- Reboot Devices
- Set Windows Service Configuration
- Create Location For Organization
- Update Node Role Policy Assignment For Organization
- Create Windows Event Policy Condition
- Node Approval Operation
- Control Windows Service
- Remove Device Owner
- Submit OS Patch Apply
- Get Installer
- Create Policy
- Get Windows Event Policy Condition
- Update Device Maintenance
- Reset Policy Overrides
- Set Device Owner
- Submit Software Patch Scan
- Update Location
- Reset Alert Set Activity Data
- Get Device Link
- Run Script On Device
- Submit Software Patch Apply
- Update Organization
- Create Custom Fields Policy Condition
- Get Custom Fields Policy Conditions
- Custom Fields Actions
- Ticketing Actions
- Organization Actions
- Devices Actions
- Get Device Active Jobs
- Get Device Installed Software Patches
- Get Device Processors
- Update Node Attribute Values
- Get Device Disk Drives
- Get Device Pending Failed Rejected OS Patches
- Get Device Volumes
- Get Device Alerts
- Get Device Network Interfaces
- Get Device Software
- Get Device Activities
- Get Device Last Logged On User
- Get Device Services
- Get Policy Overrides
- Get Device
- Get Device Installed OS Patches
- Get Device Pending Failed Rejected Software Patches
- Get Node Custom Fields
- Groups Actions
- Webhooks Actions
Overview
This node operation creates a new location within an organization in the Management resource. It is useful for scenarios where you need to programmatically add physical or logical locations associated with an organization, such as offices, warehouses, or service centers. For example, a company expanding its operations can use this node to register new office locations automatically in their management system.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the organization under which the location will be created. |
| Additional Body Fields | Optional fields to provide more details about the location: |
| - Name | The name of the location (e.g., "Headquarters", "Warehouse 1"). |
| - Address | The physical address of the location. |
| - Description | A textual description of the location. |
| - User Data | Custom attributes as JSON to store additional user-defined data related to the location. |
| - Tags | JSON array of tags to categorize or label the location. |
| - Fields | JSON object representing custom fields for further customization of the location data. |
Output
The node outputs JSON data representing the newly created location entity. This typically includes all the properties sent in the request along with any additional metadata or identifiers assigned by the backend service upon creation. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authentication to the AvantGuard NinjaOne API.
- The base URL for the API must be configured in the node credentials.
- The node uses the
@avantguardllc/n8n-openapi-nodepackage and an OpenAPI specification (openapi.json) bundled internally to build requests.
Troubleshooting
- Missing or invalid Id: Since the
Idproperty is required, omitting it or providing an invalid value will cause errors. Ensure the organization ID is correct and provided. - Invalid JSON in custom fields: The
userData,tags, andfieldsproperties expect valid JSON strings. Malformed JSON will cause parsing errors. - Authentication errors: If the API key or base URL is misconfigured, the node will fail to authenticate. Verify credentials and endpoint settings.
- API response errors: If the backend rejects the request due to invalid or missing fields, check the optional body fields for correctness and completeness.
Links and References
- AvantGuard NinjaOne API Documentation (example placeholder, replace with actual if available)
- n8n Documentation on Creating Custom Nodes