What the SolarWinds Service Desk integration does
Devices from your RMM land on the right client's records every hour: serial number, operating system, IP and MAC address, warranty and when each one last checked in. New devices are added, changed ones updated, and anything your techs wrote by hand is left alone.
Setting it up
- In SolarWinds Service Desk go to Setup › Users, open the user DokLocker should act as (one who can see hardware), and under Actions choose Generate JSON Web Token. Copy the token.
- In DokLocker pick your data center (United States, Europe or Australia, matching the address you sign in at), choose whether each client is a site or a department, and paste the token.
Hardware the discovery agent found comes in every hour with its name, category, operating system, serial number, make and model, IP address, the latest warranty end date and when it was last scanned. Each site (or department) is matched to a client on Sync and matching; hardware with no site is skipped. Built from SolarWinds' API documentation and not yet tried against a live account; tell us if anything is missing.
ConnectWise Automate
- In Automate, make a user for DokLocker that can read your clients and computers, without two-factor sign-in.
- Get an integrator Client ID from the ConnectWise developer portal (developer.connectwise.com). Automate requires one for every API connection.
- In DokLocker enter your Automate address (like
https://yourcompany.hostedrmm.com), the Client ID, the username and password.
Each Automate client is matched to a client on Sync and matching. Computers come in with type, operating system, serial number, IP and MAC address and last contact, every hour. Built from ConnectWise's documentation and not yet tried against a live server.
Datto RMM
In Datto RMM, turn on API access under Setup › Global Settings › Access Control. Then open your user under Setup › Users and click Generate API Keys. In DokLocker pick the platform (the word in your Datto RMM address, such as merlot or pinotage) and paste the key and secret.
Zabbix
Needs Zabbix 6.4 or later. In Zabbix go to User settings › API tokens (admins: Users › API tokens) and create a token for a user who can read the host groups you want. In DokLocker enter your Zabbix web address and the token. If your Zabbix uses a self-signed certificate, choose Allow a self-signed certificate.
If the test says HTTP 403, something in front of Zabbix (often Cloudflare) blocked the request. Use Zabbix's local address instead, such as http://192.168.1.20/zabbix.
Host groups are matched to clients. After the test passes, click Sync and matching, then Sync now. Each Zabbix host group is listed; one named like a client is matched for you. Pick the client for the others, and choose Ignore for shared groups such as Linux servers. A host in several groups goes to the first one matched to a client. Hosts come in with their IP address and, when Zabbix inventory is turned on, serial number, make, model, OS and MAC address.
Cisco Meraki
In the Meraki dashboard go to Organization › Settings, turn on API access, then open My profile › API access and generate a key. Paste it into DokLocker.
Each Meraki organization is matched to a client. If you keep all your clients in one Meraki organization, DokLocker matches each network instead. Security appliances become network devices with the role Firewall, switches Switch, and wireless Access point; cameras and sensors become other hardware. Each comes with serial number, model, MAC, LAN IP and firmware. A role you've set yourself is never changed.
Auvik
In Auvik open your user menu (top right) › API Key and create a key. A read-only user is enough. Your region is in your Auvik address: yourcompany.us1.my.auvik.com means us1. In DokLocker enter the region, the user's email and the key.
Each Auvik client is matched to a DokLocker client on Sync and matching. Everything Auvik has discovered (firewalls, routers, switches, access points, servers, printers and more) comes in with make, model, serial, IP, firmware, online status and last seen, every hour.
Domotz
- In the Domotz portal open your user menu › API Keys and create a key with read access.
- In DokLocker go to Admin › Integrations, find Domotz under Network and phones, choose your region, paste the key and click Test.
- Click Sync and matching. Each Domotz agent (the collector on a client's network) is matched to the client with the same name; pick a client for the rest.
Devices sync every hour. Printers, switches, access points, servers and computers become the matching record type (from their name, maker and Domotz type), with IP and MAC address, make, model and firmware. Each record shows whether Domotz sees it as online and when that last changed. Devices are matched to existing records by MAC address, then by name.
ThreatLocker
In the ThreatLocker portal go to Integrations › API, create an API user with the API Administrator role, and copy its API key. Pick the instance your portal uses: it's the letter in your API address (portalapi.g.threatlocker.com). Leave Organization ID blank to sync every child organization, or enter one to sync only that one. Each child organization becomes a client, and every computer with ThreatLocker is matched to its record, showing its ThreatLocker mode (Secured, Learning or Installation), its computer group and agent version, so you can spot machines that were left in Learning mode. Computers sync every hour.
Watchman Monitoring
Enter your Watchman subdomain (the first part of your dashboard address, yourcompany.monitoringclient.com) and an API key from Settings › API in Watchman. Each Watchman group becomes a client. Every Mac and PC that reports to Watchman lands on its client's record every hour with its platform, OS version, serial number, model and last report time, plus whether Watchman flags it as needing attention. Archived computers and hidden groups are left out.
SentinelOne
In the SentinelOne console go to Settings › Users › Service Users and create a service user with the Viewer role at account scope (or global scope if you manage several accounts), then copy its API token. Enter your console address (like usea1-partners.sentinelone.net) and the token. Each SentinelOne site becomes a client. Every hour each computer with the agent lands on its client's record with its serial number, model, OS, IP and MAC address and when it was last active, plus its agent version, network status (connected or disconnected) and whether it's infected. Decommissioned and uninstalled agents are left out. SentinelOne counts as a security agent on Security coverage.
Avanan
In the Avanan MSP portal create an MSP SmartAPI key and copy its application ID and client secret. Pick the region the key belongs to (United States, Europe, Canada, Australia, United Kingdom or India). Every 6 hours each customer tenant is matched to a client and gets a Software license record named Avanan with its package (like Advanced or Complete), its add-ons and the number of protected users. Tenants still in a trial show "Trial (POC)" and the date it ends. Tenant names come from their Avanan portal address, so match any that don't line up on the Sync page once.
Proofpoint Essentials
Enter your partner domain (the domain your partner account in Proofpoint Essentials is under), its data center (US1 to US5 or EU1, from your sign-in address), and the email and password of a partner administrator. A dedicated admin used only for DokLocker is best. Every 6 hours each customer organization is matched to a client and gets a Software license record named Proofpoint Essentials with its package (like Business or Advanced) and the number of active, billable users, so seat counts are on the client without signing in to Proofpoint.
Tailscale
In the Tailscale admin console go to Settings › OAuth clients and create a client with the devices:core:read scope (it never expires), or go to Settings › Keys and create an API key (it expires within 90 days). Leave Tailnet blank to use the key's own tailnet. Choose where clients come from: the tailnet (one client, for a tailnet per customer) or device tags (each tag such as tag:acme is a client, for one tailnet shared by several customers; untagged machines fall under the tailnet). Every hour each machine lands on its client's record with its OS and last-seen date, plus its Tailscale address, Tailscale name, user, client version, whether it's online, whether it's waiting for approval or has an update available, and when its key expires. The Tailscale address is added beside the record's own IP address, not over it. Machines shared in from other tailnets are left out.
NetBird
In NetBird go to Team › Service Users, create a service user with the User role (or Admin), and create an access token for it. If you host NetBird yourself, enter your management address (like netbird.yourmsp.com); otherwise leave it blank for NetBird Cloud. Choose where clients come from: the account (one client) or peer groups (each peer's first group other than All is a client; peers only in All are skipped until you put them in a group). Every hour each peer lands on its client's record with its OS, serial number, MAC address and last-seen date, plus its NetBird address, whether it's connected, its NetBird version, location and whether its login expired.
TeamViewer
In the TeamViewer Management Console open your profile › Apps › Create script token, and give it read access to Group management and Computers & Contacts. Each TeamViewer group becomes a client. Every hour each device in a group lands on its client's record with its TeamViewer ID, whether it's online and when it was last seen. Devices outside any group are left out.
Mailbox search for DokBot
Lets each person connect their own mailbox so DokBot can search it. See Search your email with DokBot.
Mail intake: Postmark, Mailgun, Microsoft 365, Google, Proton Mail or IMAP
Forward email into DokLocker's Inbox and file it to a client or the knowledge base. Use Postmark or Mailgun inbound, or a mailbox that DokLocker reads every 2 minutes: Microsoft 365, Google Workspace, Proton Mail (through Proton Mail Bridge) or any IMAP host. Only your team, your clients and senders on the allow list go straight to the Inbox; everything else waits in quarantine. Setup for each source is in Inbox and mail intake.
SMTP2GO and SMTP (sending email)
Send DokLocker's emails (info requests, share links, invites and alerts) from your own address. For SMTP2GO, verify your sending domain under Sending › Verified Senders (with the SPF and DKIM records it gives you), create an SMTP user under Sending › SMTP Users, and enter that user, its password and the address to send from. For any other service choose SMTP server and enter its host, port and sign-in. Test connection signs in without sending anything. More in Sending email from your domain.
Cloudflare
In Cloudflare go to My Profile › API Tokens › Create Token. Start from the Read all resources template, or make a custom token with Zone › Zone › Read and Zone › DNS › Read for all zones, and paste it into DokLocker. Once a day every domain in the account lands on its client's Domains tab with Cloudflare as the DNS host and its name servers, and a DNS records: domain note lists every record (type, name, where it points and whether it's proxied). Domains you've already added to a client go to that client automatically; match the rest on the Sync page. Registration and SSL expiry keep being checked every night as before.
Pax8 and Sherweb (cloud subscriptions)
Every client's subscriptions from your distributor become Software license records on the client, with the product, vendor, seats, start date and when the commitment ends, so renewals show up with your other expiring items. They're refreshed every 6 hours. Match each Pax8 company or Sherweb customer to a client on the Sync page. When a subscription is canceled its record stays, with 0 seats and the status shown, so you keep the history.
- Pax8: ask your Pax8 partner contact, or open the Pax8 app's API settings, for API credentials (client ID and secret) and paste them in.
- Sherweb: in Sherweb Cumulus go to Security › APIs, create API credentials and copy the client ID, client secret and the Service Provider API subscription key.
Azure and AWS
Each client's Azure VMs and AWS EC2 instances become server records, with a note listing their networks, databases and storage and anything left open to the internet. See Azure and AWS.
Backup monitoring: Axcient, Datto, Slide, Veeam, Comet Backup, Backup Radar and Wasabi
Every client's backup results, every hour, with an alert when one fails: Axcient x360Recover, Datto BCDR, Slide, Veeam Service Provider Console or a single Veeam Backup & Replication server, Comet Backup and Backup Radar. Wasabi adds each client's backup storage, with an alert when it suddenly jumps or drops. See Backup status for setup and what you see.
Dell and Lenovo warranty lookup
Fill in warranty end dates straight from the manufacturer. Every record with a Warranty expires field, a Serial number and Manufacturer Dell or Lenovo is looked up: new devices within the hour, and each one again every 30 days. Empty purchase dates are filled from the ship date. If you typed a later warranty date yourself, for example an extended warranty bought from a reseller, it's kept.
- Dell: sign up for Dell TechDirect at techdirect.dell.com, request access to the Warranty API under APIs, then paste the client ID and secret Dell sends you under Admin › Integrations › Dell warranty. Approval usually takes a day or two.
- Lenovo: Lenovo gives partners a warranty API key (a ClientID). Ask your Lenovo partner contact or Lenovo Partner Hub for access to the warranty API and paste the key under Lenovo warranty.
Each record then shows a Warranty lookup line with the support level and when it was last checked, and a Check now button for that one device. Dates feed the warranty column, Expirations, Hardware lifecycle and alerts as usual.
HP doesn't offer an open warranty API to MSPs, so HP warranty dates still come from your RMM sync or by hand.
UniFi
- Cloud (best for MSPs): at unifi.ui.com open Settings › API and create an API key. One key covers every console on your UI account.
- Local console: on the console open UniFi Network › Settings › Control Plane › Integrations, create an API key, and enter the console's address (for example
https://192.168.1.1).
After Test connection passes, click Sync and matching, then Sync now:
- DokLocker lists each UniFi console (cloud) or UniFi site (local console). One with the same name as a client is matched straight away; pick the client for the others.
- Click Sync now again. Each device comes in as a Network device record (cameras as Assets) on the client's first site, with its model, MAC address, IP address, firmware and online status.
- A device that's already documented is updated instead of copied: DokLocker matches by MAC address, then by name.
After that it syncs every hour. To check it worked, open a client's Records tab, or search for a device name or MAC address.
Included in every plan
Every integration is included at no extra cost, on the hosted service and self-hosted. Connect it under Admin › Integrations, click Test, and the first sync starts straight away.