Datto RMM Integration

Estimated reading: 8 minutes

Deepser presents a dedicated module to easily integrate with Datto RMM. Integration by additional configuration of a flow allows the following functionality:

Download all Sites
Download all Devices
Download all Alerts
Create or Update a Site
Create or Update a Device Warranty (Device Warranty)
Create or Update user-defined Device fields (Device Udf)
Create or Update an Alert to Resolved

The following is a rundown of the available flow-side actions regarding integration:

Enable Datto Integration in Deepser

To enable the integrations module, go to the Deepser menu at System > Configurations > Integrations – Configurations, select and enable Datto RMM, then Save:

Once the integration is menu-enabled, you will be able to view the new item:

Sites

Sites, in Datto RMM, represent an organizational unit that generally corresponds to a client or a physical location of a client.

These are used to group and manage devices by client or location to securely separate data.

Within Deepser in the Integration > Datto > RMM > Site section, we will find Sites that have been created on Datto RMM and synchronized.

Below are the main fields provided and synchronized on Deepser:

Field	Definition
Site Id	Unique identifier automatically assigned by Datto RMM to the Site
Uid	Unique code in UUID format assigned to the Site.
Name	It is the descriptive name of the Site

Devices

Devices, in Datto RMM, correspond to the devices that are monitored and managed through the platform.

These can be: Computers, Laptops, Servers, Network Devices, Printers, etc…

The main functions associated with Devices can be: monitoring, remote management, Alerting.

Within Deepser in the Integration > Datto > RMM > Devices section, we will find the Devices that have been created on Datto RMM and synchronized.

Below are the main fields provided and synchronized on Deepser:

Field	Definition
Device Id	Unique identifier automatically assigned by Datto RMM to the Device
Uid	Unique code in UUID format assigned to the Device
Hostname	Device hostname
Site Uid	Uid code of the Site with which the Device is associated.
Site Name	Name of the Site with which the Device is associated
Type	Device Type
Category	Device Category
Domain	Device Domain
Description	Device Description

Alerts

Alerts, in Datto RMM, correspond to notifications automatically generated by the system when specific problems, anomalies or conditions are detected on monitored devices.

The most common types of Alerts are listed below:

Hardware: problems with RAM, disk, temperature, etc.
Software/services: shutdown of a Windows service, failure to update antivirus, etc.
Performance: excessive CPU or RAM usage, slowdowns.
Device status: offline for too long, agents not updated.
Patches/updates: failure to install or errors during update.

These can be manually closed or auto-resolved if the condition that generated them is within normal parameters.

Within Deepser in the Integration > Datto > RMM > Alerts section, we will find the alerts that have been created on Datto RMM and synchronized.

Below are the main fields that are expected and synchronized on Deepser:

Field	Definition
Alert Uid	Unique code in UUID format assigned to the Device
Priority	Alert Priority
Resolved	Indicates whether the Alert is resolved
Resolved By	Operator who resolved the Alert
Resolved On	Alert resolution date
Ticket Number	Number of the ticket linked to the alert
Device Uid	Uid code of the device that triggered the alert
Device Name	Name of the device that triggered the alert
Site Uid	Uid code of the site connected to the device
Site Name	Name of the site connected to the device

Datto RMM – Configuration

The following will explain how to proceed with Deepser-side and Datto RMM-side configuration.

Connection

From the Deepser menu, go to System > Integration > Datto > RMM > Connection, and create a new Connection by clicking the “Add Connection” button.

In the screen that will open we set:

Name: name we assign to the connection
OAuth Client: we select an existing Oauth client or create a new one via the + button located below the drop-down menu

Oauth Client

In the floating window that will open, set the following fields:

Name: name of the Oath Client
Provider: Datto RMM
Domain: Select the domain related to your geographic area.

App Configuration

On Datto RMM, we navigate to Setup > Global Settings.

Here we enable the “Enable API Access” switch.

We then navigate to Setup > Users, and enter the form for editing a user.

At the bottom of the form, we click on the “Generate API Keys” button.

Once the button is clicked, the following will be generated:

API URL: url of our Datto RMM instance.
API key.
API Secret Key.

Let’s go back to Deepser and access the DeepPassword – Password module from the “Password” item in the menu on the left.

NOTE: To use the Password module, you must first have created a Passphrase.

Below is a link to articles devoted to the module: https://docs.deepser.com/deepser-documentation/deepser-documentation/password-management-9543/

From the DeepPassword – Password form, we create a new Password in which we set:

Username: value of the API key
Password: value of the API Secret Key

We save the Password and return to the Deepser OAuth Client.

So let’s set the “Password” field with the password we created just now.

At this point, we should be in this situation on Deepser’s OAuth Client:

Provider: Datto RMM
Domain: domain related to your geographic area
Password: selected from the drop-down menu the password created just now.

An example configuration of a Deepser OAuth Client is shown below:

If everything has been configured correctly, clicking the Get Token button will return the first Access Token.

Now the Datto RMM OAuth Client is configured correctly, and is ready to be used within a Connection.

Having reached this point we are ready to use this Connection within the Actions of the Download and Upload Flow of Datto RMM entities.

Get Sites, Devices, Alarms

To retrieve and create/update Sites and Devices on Deepser, we use a flow with a cron set up

Then go to Flow > Designer from the Deepser menu and click the New button and select Flow

Give the flow a Name and click Save.

As a Trigger for the flow we set “Cron” and set a time value. This value will indicate how often Sites and Devices will be created and/or updated on Deepser.

In the Flow, click + to add a new node to the flow, then Action.

In the drop-down menu, select Integration > Datto RMM > Dowload Multiple > Sites.

Once the action is added, we select the previously configured connection to Datto RMM and click “Save”

Once the Sites have been retrieved, we can proceed to cycle them. We add a new node with the + button, then select Logic and Foreach:

We select the Sites collection created earlier (from the right-hand menu).

Finally, based on each Sites obtained by foreach, we obtain the devices.

Webhook

Webhooks provide a real-time method for receiving notifications within the Datto RMM platform. Datto RMM leverages HTTP POST requests to integrate with external services, thereby streamlining the management and automation of IT workflows.

We will utilize webhooks to automatically create a ticket in Deepser whenever an alert is generated in Datto RMM.

As a flow trigger, select “Datto RMM Webhook” and click “Save.”

From the trigger we have just created, copy the link highlighted in the screenshot below.

Webhook Configuration in Datto RMM

After creating the flow and copying the link, proceed to Datto RMM to configure the webhook within the application.

Navigate to Setup > Integrations > Global Webhooks.

Click the “Turn On” button to activate webhooks:

At this point, configure the following parameters:

URL: Enter the URL copied previously from the Flow with API Trigger.
Content-Type: Select application/json.
Custom Request Headers: Set the following headers:
- Authorization: Bearer <deepser_user_api_token>
- Accept: */*
Alert Raised Payload: Customize the request body that Datto RMM will send to Deepser.

Once configured, you can test the Datto RMM call to Deepser by clicking the “Test Alert Raised Webhook” button located at the bottom right of the page.

NOTE: The authorization token is obtained from the API user created in Deepser. For more information, refer to the following article:

https://docs.deepser.com/deepser-documentation/deepser-documentation/deepser-api-9524/api-authentication-10303/

Datto RMM flow configuration

In this example, we will set up a flow to create a ticket when an alert is raised and to update its status upon resolution.

Begin by configuring the trigger and selecting “Datto RMM Webhook.”

As the second step in the flow, insert a conditional check to identify whether the received alert is a trigger event or a resolution event. The check is performed on the alert’s “Resolved” field:

If the value is 0, it signifies an event trigger alert.

Next, create a node for ticket creation, defining the required values for the ticket that will be created in Deepser.

NOTE: The “Alert Datto UID” field is a custom field used to store the alert identifier. This field is crucial for retrieving the ticket during resolution.