We have two major features to announce today. Both ChromeOS monitoring and HaloPSA have been running in early access for the past few months, and we’re now making them available to all Watchman Monitoring customers.
ChromeOS Monitoring
Back in September we sent out a survey asking what Watchman Monitoring users wanted us to build. ChromeOS Monitoring was one of the top requests, and now it’s out! ChromeOS monitoring works through a Google Workspace integration. Once connected, Watchman Monitoring syncs your ChromeOS devices and displays them alongside the rest of your Computers.
What you get:
- Chromebook devices appear in your Computers list, grouped however you organize your other machines
- Device details pulled from Google Workspace: serial number, model, OS version, enrollment status, last sync time, and more
- A dedicated sync status indicator so you can see at a glance whether the integration is healthy
- Email alerts if the sync fails or your Google Workspace credentials need attention
- An initial set of plugins for monitoring ChromeOS devices. We would love your feedback here on what Plugins you’d like added/changed!
How to get started:
Navigate to Installers → ChromeOS in your dashboard. You’ll need a Google Workspace service account with read-only access to the Chrome Devices API. The setup form walks you through it step by step, and you can test the connection before saving.
If you ran into any issues during early access, we’ve shipped several reliability improvements since the initial release – including better error messages when authentication fails, sequential device processing to avoid sync conflicts, and proper handling when a target group is being deleted. For more information, check out our Help Center article here.
HaloPSA Integration
For teams using HaloPSA, Watchman Monitoring can now create and update tickets in your PSA automatically – no manual hand-off required.
When a plugin alert fires, Watchman Monitoring opens a ticket in HaloPSA. When the issue clears, the ticket is updated. You stay in HaloPSA; Watchman Monitoring handles the signal.
What you can configure:
- Which ticket type, status, and priority to use for new alerts
- Asset matching – Watchman Monitoring will attempt to link computers to their corresponding assets in HaloPSA by serial number
- Per-company ticket behavior through the HaloPSA settings page in your dashboard
How to get started:
Go to Integrations in your Watchman Monitoring dashboard and click the HaloPSA card. You’ll be prompted to enter your HaloPSA API credentials. Once connected, you can configure ticket behavior and test the connection from the settings page. For more information, check out our Help Center Article here.
Other Fixes
Webhook fix for long URLs: Some webhook endpoints (particularly certain Zapier and Teams URLs) were being rejected because of a length limit in the database. That limit has been removed. If you had a webhook endpoint that refused to save, try again.
What’s Next
We’re continuing to work on reliability and depth across all three of these integrations. On the roadmap:
- Apple ABM/ASM Integration – Correlating Watchman Monitoring data with Apple Business Manager and Apple School Manager device enrollment
- More ChromeOS monitoring depth – Additional device properties and plugin-level checks for ChromeOS devices
- Improved Duplicate Computer Logic – There are a few issues that we’re planning to patch related to duplicate detection (especially in Windows)
- New Zendesk Integration – We’ll be launching a new Zendesk integration that supports OAuth
- Big Infrastructure Changes – We’re spending a lot of time on our backend infrastructure with the aim of being able to ship faster once it’s completed.
As always, the best place to share feedback or vote on what comes next is the Watchman Monitoring Community Forum.
Ian, Garrett & Allen