Morning device check
Dan Fletcher, service desk lead at an MSP, asked which devices at BigCo were offline. Memtro listed each with its class, last contact and any active alerts, and flagged two in maintenance.
NinjaOne + Memtro
Which devices are offline, and which alerts are still open?
NinjaOne manages your clients' devices, and Memtro reads it so technicians get answers fast. It reads organisations, devices with online and maintenance state, active alerts, the activity log, pending patches, and tickets with their history. When asked and granted, it can create, update and comment on tickets, reset alerts and schedule maintenance. It can also reboot devices, run scripts, patch, control Windows services, and create, move, approve or decommission devices. NinjaOne can tell Memtro when a condition triggers or a script runs, and a job can start on it. Only a system administrator can create the client app.
In Memtro
What you can do with NinjaOne in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right NinjaOne tool, reads what it needs, and answers with the source cited.
What it does
- 01Reads client organisations and devices with class, online state, last contact, approval and maintenance state.
- 02Reads active alerts, the activity log, and pending, failed or rejected operating system patches.
- 03Reads tickets by board, and one ticket's history with its comments and changes.
- 04When asked and granted, creates, updates or comments on a ticket. A public comment may be emailed to the requester.
- 05When asked and granted, resets alerts, schedules maintenance, reboots devices, runs scripts, patches and controls Windows services. These change the machine and can interrupt its user.
- 06With events on, a monitoring condition triggering, a script running or an end user asking for help can start a job.
Acts when asked
When you ask it to
These tools change something in NinjaOne. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
- 01Create a ticket
- 02Update a ticket's subject, status, priority, severity, type, assignee or tags
- 03Comment on a ticket (a public comment may email the requester)
- 04Reset an alert
- 05Schedule a maintenance window on a device
- 06Cancel a device's maintenance window
- 07Reboot a device
- 08Run a script or built-in action on a device
- 09Scan a device for operating system or software patches
- 10Install a device's approved operating system or software patches
- 11Start, stop, pause or restart a Windows service on a device
- 12Create a client organisation
- 13Rename a device or move it to another organisation, location, role or policy
- 14Approve or reject devices waiting for approval
- 15Decommission a device
Events
When it happens
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with NinjaOne for you. Each event can start a job, with the event as its input. NinjaOne sends a secret with every delivery, and one without it is refused.
Events and webhooks- 01A monitoring condition triggered or reset
- 02A condition's automated action ran
- 03A condition's action set ran
- 04An action ran on a device
- 05An action set ran on a device
- 06A script ran on a device
- 07A scheduled task ran
- 08Operating system patching activity
- 09Third-party software patching activity
- 10Antivirus activity (threats, scans)
- 11Security activity
- 12Monitor activity
- 13System activity (devices, organisations, users created or changed)
- 14A comment was added
- 15An end user asked for help
- 16PSA integration activity
- 17Mobile device management activity
- 18NinjaOne Backup activity
- 19CloudBerry backup activity
- 20Virtualisation (hypervisor) activity
- 21Network discovery activity
- 22Remote tools activity
- 23NinjaOne Remote session activity
- 24Remote desktop activity
- 25Splashtop session activity
In practice
Ask it like you would a colleague
Once NinjaOne is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
NinjaOne + MemtroWhich devices at Acme Ltd are offline right now?
What alerts are active on the file server?
Which critical patches are still pending?
What happened on ticket 4821 since yesterday?
Reboot the reception PC at Northwind.
A help request arrives
When NinjaOne told Memtro an end user had asked for help, a job started. It read the device's alerts and recent activity, and, as granted, created an internal ticket for Priya Sharma's team with what it found.
Teams
Where it fits
The teams that lean on NinjaOne most, a question each of them asks, and what they connect beside it.
- EngineeringKeep decisions from evaporatingEngineer, Tech lead, On call, New joiner“Who owns the billing migration, and what did we decide about retries?”Used alongside GitHub, Linear, Jira, Confluence, Slack and 5 more.
- ProductHear what customers actually ask forProduct manager, Researcher, Designer, Head of product“Which customers asked for SSO this quarter, and what is their combined ARR?”Used alongside Help Scout, HubSpot, Linear, Jira, Slack and 6 more.
- Agent buildersMemory and tools for the agents you buildSolo builder, Platform team, Automation engineer, Whoever signs it off“Search memtro for what we know about Acme before drafting the proposal”Used alongside GitHub, Linear and Slack.
Better together
Works with
A record in NinjaOne is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
- Work managementNinjaOne with JiraJQL search, issue details and projects from Jira Cloud.
- Work managementNinjaOne with Clio ManageAsk the matter: its client, its fee earner, the time on it and what is still unbilled.
- Work managementNinjaOne with LinearIssues, projects and teams, synced hourly into memory.
- SupportNinjaOne with Help ScoutAI that reads your support conversations and cross-references the customer everywhere else.
- SupportNinjaOne with ZendeskEvery ticket, reply and internal note, ready to be asked about.
- SupportNinjaOne with IntercomCustomer conversations and the people behind them, in your company memory.
- Documents and wikisNinjaOne with NotionSearch pages and query databases, and write to them when you ask.
- Documents and wikisNinjaOne with Google DriveSearch Drive and read Docs, Sheets and Slides as text, and write a Doc when you ask.
- Documents and wikisNinjaOne with ConfluenceSearch and read wiki pages, and write them when you ask.
Also in Engineering and operations
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
- GitHub
- AWS CloudWatch
- Sentry
- ServiceNow
- Okta
- Twilio
- AWS CloudTrail
- GitLab
- Bitbucket
- Vercel
- PagerDuty
- Datadog
- Grafana
- incident.io
- Azure DevOps
- CircleCI
- Cloudflare
- LaunchDarkly
- New Relic
- Rollbar
- Snyk
- Better Stack
- Buildkite
- DigitalOcean
- Heroku
- Netlify
- SonarQube Cloud
- Statuspage
UptimeRobot- Axiom
- BugSnag
- Checkly
- Hetzner Cloud
Honeycomb- Pingdom
- Render
- Statsig
- Sumo Logic
- Supabase
- HCP Terraform
- Vultr
- Airbrake
- Codecov
Cronitor- Dynatrace
FireHydrant- Fly.io
- Honeybadger
- Akamai Linode
- Octopus Deploy
- Pulumi
- Rootly
- Semgrep
- Splunk
StatusCake- Tailscale
- Argo CD
- authentik
- Coolify
- Gitea
GlitchTip
GLPI- Jenkins
Langfuse
LibreNMS- n8n
NetBox- Portainer
- Prefect
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone- OpenAI (usage and cost)
- Anthropic (usage and cost)
- Algolia
- Flagsmith
- Unleash
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert- KnowBe4
JumpCloud
ConfigCat- Railway
- Fastly
- Postman
- Make
- Braintrust
- OpenRouter
- ElevenLabs
Split- Scaleway
Aikido Security- AssemblyAI
Astronomer- Bamboo
- Baseten
- Bitrise
- Bitwarden
- BrowserStack
- bunny.net
- Cachet
- Checkmk
- Civo
- Cloudsmith
- Codacy
- Codemagic
Comet Opik- Coralogix
CrowdStrike Falcon- Dagster+
- DeepSource
Detectify- Docker Hub
Domotz- Grafana OnCall
- Harness
- Hugging Face
- Instatus
- Koyeb
- Lambda Cloud
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary- Mezmo
- Nomad
Northflank- Oh Dear
- OVHcloud
Portkey- Probely (Snyk API & Web)
PromptLayer- Proxmox VE
PRTG Network Monitor- Qase
Raygun
Retell AI- Retool
Runpod- SecurityScorecard
- Semaphore CI
Shodan- SigNoz
- Socket
Spike.sh
Squadcast- SwaggerHub
- TeamCity
Tenable- Together AI
- Travis CI
UpGuard
Uptime.com
Vanta- Vapi
- Windmill
Zenduty- OpsLevel
Cortex- Auth0
- Clerk
WorkOS
Kandji
Automox
Huntress- HackerOne
SimpleMDM- AppSignal
Healthchecks.io
Rapid7 InsightVM- 1Password Events
- JFrog Artifactory
- Sauce Labs
Zenhub- Deepgram
- Replicate
Setup
How to connect
Connect withInstance, Client ID and Client secret
- 1
In NinjaOne, a system administrator opens Administration, then Apps, then API, and adds an API Services client app. Tick the Monitoring and Management scopes and the Client Credentials grant.
- 2
In Memtro, open Connections → NinjaOne and enter the Instance host, such as eu.ninjarmm.com, then the Client ID and Client secret.
- 3
An administrator grants the ticket, device and script actions by name only to the technicians who may use them. Events are turned on from the connection's Events tab.
- 4
Ask which devices are offline and which alerts are open.
Also works from
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The NinjaOne tools are the same everywhere.
FAQ
Questions
Can Memtro change anything in NinjaOne?+
Only when you ask, and only what it has been granted: create a ticket; update a ticket's subject, status, priority, severity, type, assignee or tags; comment on a ticket (a public comment may email the requester); reset an alert; schedule a maintenance window on a device; cancel a device's maintenance window; reboot a device; run a script or built-in action on a device; scan a device for operating system or software patches; install a device's approved operating system or software patches; start, stop, pause or restart a Windows service on a device; create a client organisation; rename a device or move it to another organisation, location, role or policy; approve or reject devices waiting for approval; decommission a device. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
Who can use a NinjaOne connection?+
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Does Memtro store my NinjaOne data?+
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
How do I connect NinjaOne?+
Instance, Client ID and Client secret. In NinjaOne, a system administrator opens Administration, then Apps, then API, and adds an API Services client app. Tick the Monitoring and Management scopes and the Client Credentials grant.
Can NinjaOne start a job?+
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with NinjaOne for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Connect NinjaOne in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.