Skip to main content
An agent with this tool answers an NCM alert or a “the internet is down” ticket from the client’s NetCloud Manager data: is the router online, which WAN link it uses, when it failed over and whether it came back, and how strong and fast its links are. It can reboot a router, run a speed test and change one setting, with the approvals you set.
Automatically enabled when you configure Cradlepoint permissions in your agent workflow. No manual toggle needed.

What It Does

  • Find the client’s NCM accounts from the Organization Mapping
  • Read routers with their state and since when, and each WAN and LAN link’s connection state, carrier, signal and address
  • Read failovers, with when each started and ended and which link carried the site
  • Read router alerts and logs, interface health, signal, usage and throughput samples
  • Reboot a router, run and read a speed test, and change a router’s configuration, group or name
  • Manage alert rules, push destinations, apps and subaccounts
  • With the API v3 token: subscriptions and licensing, Starlink dishes, LAN clients, modem upgrades and eSIM, Remote Connect, NetCloud Exchange, private cellular, users and roles, and Wi-Fi passwords
The agent calls NCM through the Vendor API tool, with cradlepoint as the vendor id. Sandbox scripts can call it too, under the same permissions; a script never reads Wi-Fi passwords.

Permission Groups

Access Profiles

Every group Read Only, and Wi-Fi Passwords off.
Devices, Reboots & Speed Tests and Configuration & Groups can change, each change after a technician approves it. Every other group is Read Only, and Wi-Fi Passwords off.
Every group can change. Users & Access, Remote Connect, NetCloud Exchange and Subscriptions & Licensing ask a technician first.
Every change runs on its own, except the ones that always ask.
These always ask a technician: unregistering a router, deleting an account, an organization migration, any change to a user or a role, and any change that sends a password, a Wi-Fi key or a secret.

On a ticket

On a ticket, every call names one of the NCM accounts mapped to the ticket’s company, and Neo checks that each router or record the call names is in that account before it sends it. Lists of every account’s routers, users, locations, alert rules and every API v3 call are not sent. With no ticket company (a chat, or a scheduled agent with no ticket), the agent reads every account.