Automated ownCloud Sync Conflict Alerts
Every night, WebRun opens ownCloud, checks the sync log for failed syncs and file conflicts, checks whether a clean copy exists in Google Drive, and texts IT through Twilio when a conflict needs a human decision.
How do I catch ownCloud sync conflicts before they overwrite someone's work?
WebRun checks your ownCloud sync log every night for failed syncs and file conflicts, then checks Google Drive for a clean copy of each affected file. It texts IT through Twilio with a summary, so a sync conflict gets a same day human decision instead of quietly overwriting someone's work.
- Sync conflicts caught the same night, not after a rewrite
- IT gets a clean copy comparison, not just a conflict name
- Resolved conflicts drop off the alert automatically
Built for IT admins · enterprise teams · universities · self-hosted storage users
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
owncloud.comin a real browser with your saved login - no setup, no API keys. -
1
ownCloud - check the sync log
owncloud.com
WebRun opens ownCloud to check the sync log. - Open the sync log and check for failed syncs and file conflicts
- Note which files and users are affected
- Sort conflicts by how long they have been unresolved
Done when Every current sync conflict and its affected files are listed.
-
2
Google Drive - check for a clean copy
drive.google.com
WebRun opens Google Drive to check for a clean copy. - Check whether a clean, unconflicted copy of the file exists in Drive
- Note its last modified date for comparison
- Flag files with no available clean copy
Done when Every conflicted file has been checked against Google Drive.
-
3
Twilio - text IT about conflicts
twilio.com
WebRun opens Twilio to text IT about conflicts. - Text IT a short summary of tonight's conflicts
- Include the file names and affected users
- Leave the actual conflict resolution to IT
Done when IT has been texted about tonight's sync conflicts.
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 it resolve the sync conflict or overwrite a file?
No. WebRun only reads and reports conflicts. Choosing which version to keep is always a decision IT or the file owner makes.
Why check Google Drive as well as ownCloud?
A clean copy in Drive often makes the fix obvious, so IT gets that context in the same text instead of digging for it.
What happens to a conflict once it's fixed?
It reads the live sync log each night, so a resolved conflict does not appear in the next text.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.