Automated Jamf Device Compliance Alerts
Every morning, WebRun opens Jamf, checks every managed Apple device for missing encryption or an outdated OS version, exports the non-compliant list to Google Drive, and texts IT via Twilio when the count crosses your threshold.
How do I get alerted when Apple devices fall out of Jamf compliance?
WebRun checks Jamf every morning for managed Apple devices missing encryption or running an outdated OS, exports the non-compliant list to Google Drive, and texts IT via Twilio when the count crosses your threshold. It only reads device compliance, so pushing updates or enforcing policy stays with your team.
- Non-compliant devices are caught before an audit does
- IT gets a text only when the count crosses your threshold
- No device is ever encrypted, updated, or wiped without a human
Built for IT admins · Apple device management teams · MSPs · security operations
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.jamf.comin a real browser with your saved login - no setup, no API keys. -
1
Jamf - check device compliance
WebRun opens Jamf to check device compliance. - Open Jamf Pro and check every managed device's FileVault encryption and OS version
- Flag devices missing encryption or more than one OS version behind
- Count how many devices are currently non-compliant
Done when Every managed device has a checked compliance status.
-
2
Google Drive - export the non-compliant list
WebRun opens Google Drive to export the non-compliant list. - Open the device compliance folder in Google Drive
- Export the non-compliant device list with owner and reason
- Replace the previous export so the file always reflects today's count
Done when Today's non-compliant device list is saved to Google Drive.
-
3
Twilio - text IT past the threshold
WebRun opens Twilio to text IT past the threshold. - If the non-compliant count is above your set threshold, text the IT lead via Twilio
- Include the count and a link to the exported list
- Stay silent when the count is under threshold to avoid noise
Done when IT has been texted whenever the non-compliant count crosses the threshold.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will WebRun encrypt a device or push an OS update?
No. WebRun only reads compliance status in Jamf. Pushing an update, enforcing encryption, or changing a profile stays with your IT team.
What sets the alert threshold?
You set the non-compliant device count that should trigger a text. WebRun only texts IT once that count is reached or crossed.
Does it lock or wipe a non-compliant device?
No. WebRun never takes action on a device. It only reports which devices are non-compliant and why, for IT to act on.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.