View as Markdown
NinjaOne icon

NinjaOne ACTION

Update Device

Update details for a specific device in NinjaOne. See the documentation
  • Action
  • Writes data
  • Destructive
  • OAuth
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's NinjaOne account once, then configure and run Update Device from your backend or agent.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "ninjaone-update-device",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    ninjaone: { authProvisionId: "apn_xxxxxxx" },
    deviceId: "Device ID",
    displayName: "Display Name",
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

Update Device inputs
Property Type Description
deviceId Device ID string
The ID of the device to update
Required Dynamic
displayName Display Name string
The name of the device
Optional
nodeRoleId Node Role Id string
The ID of the device role
Optional Dynamic
policyId Policy ID string
The ID of the policy override
Optional Dynamic
organizationId Organization ID string
The ID of the organization
Optional Dynamic
locationId Location ID string
The ID of the location to the ticket
Optional Dynamic

REFERENCE

Tool details

Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.

Registry key
ninjaone-update-device
Version
0.0.2
App
NinjaOne
Authentication
OAuth
Read-only
No
Destructive
Yes
Open world
Yes