NinjaOne Custom Fields
Overview
MSPs use NinjaOne custom fields to hold data the RMM does not collect itself: asset tags, warranty dates, backup product, contract tier, BitLocker escrow status, or the output of a scripted check. Fields live on two scopes, devices and organizations, and each scope has a read and a write tool.
Anti-triggers
- Ticket custom fields — ticket attributes are a separate model; use
ninjaone-tickets(ninjaone_tickets_attributes_list). - Device or organization core properties (name, policy, location) — use
ninjaone-devicesorninjaone-organizations.
MCP Tools
| Tool | Tier | Arguments | Purpose |
|---|---|---|---|
ninjaone_devices_get_custom_fields |
read | device_id |
All custom field values on a device |
ninjaone_devices_update_custom_fields |
write | device_id, fields |
Set one or more device custom fields |
ninjaone_organizations_get_custom_fields |
read | organization_id |
All custom field values on an organization |
ninjaone_organizations_update_custom_fields |
write | organization_id, fields |
Set one or more organization custom fields |
fields is an object of field-name/value pairs, for example { "assetTag": "ACME-0042", "warrantyExpiry": "2027-03-31" }. Keys are the field's API name as defined in NinjaOne's custom-field configuration, not its display label.
Workflows
Read before write
- Get the current values with the matching
get_custom_fieldstool. - Confirm the exact key spelling from that response; never guess a key.
- Show the user the old and new value for each field.
- After approval, call the matching
update_custom_fieldstool with only the fields that change.
Fleet audit
ninjaone_organizations_list, thenninjaone_organizations_devicesper organization.ninjaone_devices_get_custom_fieldsper device.- Report devices where a required field (asset tag, warranty date) is empty. This is read-only and safe to run unattended.
Gotchas
- Partial update, not replace. Only the keys you send change. Do not send a field with an empty value to "leave it alone"; omit it.
- Technician-editable versus script-written fields. Some fields are written by NinjaOne scripts on a schedule. Changing one by hand is overwritten on the next run; check with the user before editing a field a script maintains.
- Per-call write. Each update is one API call per device or organization; there is no bulk tool. A fleet-wide change is many write calls and should be approved as a batch first.
Related Skills
- Devices - Device lookup
- Organizations - Organization lookup
- Tickets - Ticket attributes