33 docs tagged with "API"

Counts devices carrying a named application per organization, publishes the device detail table to an organization Knowledge Base article, and optionally publishes a tenant-wide summary table to a global Knowledge Base article.

An API-driven reporting solution for NinjaOne that counts devices carrying a named application across every organization and publishes the results as organization-level and tenant-wide Knowledge Base articles.

Custom RPA bot that attaches a device to an existing CW RMM service ticket, covering the gap where a workflow cannot associate a device. Accepts a ticket ID or ticket number, preserves existing device associations, and is safe to re-run.

Custom form that collects a ticket and a device in order to attach that device to an existing CW RMM service ticket. Accepts either a ticket ID or a ticket number, and preserves any devices already associated with the ticket.

This script will uninstall and disable the Windows Copilot application as well as its functionality in the Edge browser. It has the revert option available too.

This monitor disables the copilot and uninstall it from the detected agents

This dataview contains the detail of action taken on the agent by the script at Copilot

This monitor revert the copilot changes and ensures to enable and install the copilot on the agents where the script has disabled and uninstalled it

Client ID of the client-credentials API application used by reporting automations to call the NinjaOne Public API. Populate once during setup; read by scripts at runtime.

Client Secret of the client-credentials API application used by reporting automations to call the NinjaOne Public API. Populate once during setup; read by scripts at runtime.

Custom RPA bot that creates a CW RMM service ticket from form input and attaches the selected device as its primary asset in the same API call. Service board, priority, team and source names are resolved to platform IDs at runtime.

Custom form that collects the company, site, device and ticket details required to create a CW RMM service ticket with a device attached as its primary asset. Service board, priority and team are entered by name and resolved to platform IDs by the paired bot.

This document details a script designed to uninstall CW Control and utilize the Offboarding - CW Control RMM+ API - EndSession Command to terminate the session from the CW Control web portal, saving approximately 10 minutes through automation.

Automates ConnectWise ticket lifecycle management directly from CW RMM monitors via webhook. Receives JSON payloads to Create, Close, or Comment on tickets, eliminating the need for separate RMM ticketing tasks and ensuring clean, duplicate-free alerting.

Automates ConnectWise ticket creation, device association, closure, and commenting based on webhook payloads from CW RMM monitors. This workflow handles device lookups, ticket state checks, and status updates to streamline alert management without requiring native RMM ticketing tasks.

Retrieves Lenovo device warranty information using Lenovo's public API. This script is designed for Lenovo workstations running Windows 10 or Windows 11 and returns the warranty start date, end date, and days remaining on the warranty.

Reports the MFA methods registered by every account in a Microsoft 365 tenant and flags the accounts whose only authentication method is SMS or a voice call.

Reports the MFA methods registered by every account in a Microsoft 365 tenant and flags the accounts whose only authentication method is SMS or a voice call.

This document provides a step-by-step guide to setting up StickySync, including generating an API key, installing the plugin, and mapping clients to ITGlue organizations.

Lists every device that has not contacted NinjaOne for each supplied number of days, publishes a per-organization table to an organization Knowledge Base article and a tenant-wide table to a global Knowledge Base article, and removes organization articles that no longer list any device.

An API-driven reporting solution for NinjaOne that lists every device that has not checked in for one or more day thresholds and publishes the results as organization-level and tenant-wide Knowledge Base articles.

The ProSync Client is a ConnectWise Automate plugin designed to connect to a centrally managed Automate instance via REST API calls. The plugin will download and synchronize content from the central instance to the installed instance.

The ProSync Server application (named "ProSync" in the ConnectWise Automate Plugin Manager) is a plugin designed to manage and distribute content across multiple instances of ConnectWise Automate from a central location.

Sync Passwords from ConnectWise Automate to ITGlue

This document outlines a script that retrieves API keys from the client password tab to enable learning mode for ThreatLocker. It includes details on dependencies, variables, parameters, and instructions for use, ensuring secure handling of API keys.

This document outlines the process of setting ThreatLocker to learning mode using an API, including auditing details such as duration, status, and user information. It provides implementation steps, associated scripts, and FAQs for effective usage.

Webhook URL for the ConnectWise workflow that manages ticket creation and closure.

This document outlines the update process for internal monitors in the ProSync plugin.

This document outlines the process to set the custom field value for "xPVAL Org Name" on machines based on the Parent Organization Name using the VSAAPI module. It details the requirements, process, parameters, and output for the script.

This document outlines the process for updating machine custom fields with the organization custom field patching schedule, including requirements, process steps, and parameters for the API call.

This document provides a method to purge Kaseya agents that are older than a specified number of days using the API. It outlines the necessary parameters including user authentication, the URL of the VSA, and any exceptions to the deletion rule.

This document provides a guide on how to update OS build custom fields for Windows 10 using a web check via API. It covers the necessary parameters such as URL, username, and authentication method required for the process.

This document provides a detailed guide on how to use the API to put the system organization name into a custom field within Kaseya VSA. It outlines the necessary parameters, including user authentication and the URL for VSA access.