NinjaOne-Scripts

Using the NinjaOne REST API v2 for automation, integration, and data retrieval via HTTP requests. Use when scripts need to interact with NinjaOne programmatically, manage devices/organizations/tickets, perform bulk operations, create tag definitions, retrieve monitoring data, synchronize with external systems (PSA, ITSM), or build custom dashboards. Covers OAuth2 authentication, pagination, filtering (device filters like df, class, org, status), rate limiting, and error handling patterns.

Using the ninjarmm-cli executable and legacy PowerShell commands for custom field management via command-line interface. Use when scripts need to interact with NinjaOne custom fields from Batch/Shell scripts, handle documentation templates, work with dropdown GUIDs directly, manage fields in non-PowerShell environments, or use piped data for large content. Covers all field types including secure, WYSIWYG, and documentation fields with examples for Windows, Linux, and macOS.

HTML formatting, inline styling, Font Awesome 6 icons, Charts.css data visualization, and optional Bootstrap 5 grid for NinjaOne WYSIWYG custom fields. Use when creating visual reports, formatted documentation, status dashboards, data charts, or styled content in custom fields. Supports cards, tables, info cards, stat cards, buttons, tags, and responsive layouts with allowlist-based HTML/CSS security.

Use when code uses Get-NinjaProperty or Set-NinjaProperty with -Type parameter, references NinjaOne custom field types (Dropdown, MultiSelect, WYSIWYG, Secure, etc.), or user asks about reading/writing NinjaOne custom fields with type conversion.

Use when code references $env:NINJA_* variables (NINJA_ORGANIZATION_NAME, NINJA_AGENT_NODE_ID, NINJA_DATA_PATH, etc.), or user asks about NinjaOne agent environment variables or organization context.

Use when creating NinjaOne automation scripts that accept runtime parameters, converting string environment variables to typed values, or user asks about NinjaOne script variables, preset parameters, or variable type conversion.

Use when code uses Get-NinjaTag, Set-NinjaTag, Remove-NinjaTag, ninjarmm-cli tag-get/tag-set/tag-clear, or user asks about NinjaOne device tagging, tag-based automation, or tag management.