Datto RMM Operations Bundle

Overview

In the Service Desk, common Datto RMM actions—creating ad‑hoc jobs, checking execution results, and pulling device health details—are frequent but often disruptive. Technicians end up context switching between tickets and the RMM console, hunting for GUIDs, waiting on execution, and manually assembling updates for clients or internal notes. Over time, this slows response, increases inconsistency in reporting, and adds avoidable friction for new technicians still learning the tooling.

To solve this problem, Pia has developed the Datto RMM Operations Bundle—a set of three automations that bring core RMM workflows into the chatbot experience. It enables engineers to create jobs quickly, track and report on job progress, and retrieve comprehensive device details and alerts without leaving the ticket. The result is faster triage, clearer updates, reduced context switching, and a more consistent, printable audit trail of work performed.

Flow

Create new QuickJob

1. The technician will run the package via the chatbot.
2. The technician will be able to select an RMM site to query if it has not been pre‑configured in the package configuration for the target client.
3. The technician will be presented with a form asking for:
   • The device to create the job on
   • The name of the new job (the name format can be automatically generated using relevant variables and a provided format in the package configuration against the target client, e.g. “New Job running component ABC against device XYZ”)
   • The component to be executed as part of the job
4. The package will then get the details of the component and generate the proposed name for the job if auto‑generation is enabled.
5. The technician will then review the proposed specifications of the job, then select between cancelling the request, modifying the selections, or proceeding to create the job.
6. The package will then make a request to Datto RMM with the details of the proposed job and return a report including the GUID of the job upon successful creation.
7. The package will then allow the user to periodically check automatically in the chatbot for the job’s completion, and upon completion of the job get a report with all of the job details including success state and outputs from the component executed.

Check Existing Job

1. The technician will run the package via the chatbot.
2. The technician will be able to select an RMM site to query if it has not been pre‑configured in the package configuration for the target client.
3. The technician will be presented with a form asking for:
   • The UUID of the job to query (this can be found in the audit notes of the ticket where the job was created with the Create New Job package)
   • An associated device of the job to get the outputs for
4. The package will query Datto RMM for the details of the job and the outputs from the device, then present a comprehensive, printable report to the technician.

Get Device Details and Alerts

1. The technician will run the package via the chatbot.
2. The technician will be able to select an RMM site to query if it has not been pre‑configured in the package configuration for the target client.
3. The technician will be asked which device to get the details of, and how many recently resolved alerts to gather (20 is the default).
4. The package will query Datto RMM and gather all the necessary details before providing a comprehensive, printable report of the details in the chatbot.