Automated Syncplicity Sync Failure Reconciliation
Every night, WebRun opens Syncplicity, checks every shared folder for sync failures and files stuck out of date, logs each issue to Airtable, and emails IT through Gmail with what needs attention.
How do I catch Syncplicity sync failures before they pile up?
WebRun checks every shared folder in Syncplicity each night for sync failures and files stuck out of date, logging each issue to Airtable with the affected user and device. It emails IT a nightly summary through Gmail, so a stalled sync gets caught and tracked before it piles up unnoticed.
- Sync failures caught the same night, not weeks later
- Every issue logged with the affected user and device
- Resolved issues close themselves out automatically
Built for IT admins · enterprise teams · managed service providers · operations teams
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.syncplicity.comin a real browser with your saved login - no setup, no API keys. -
1
Syncplicity - check sync status
syncplicity.com
WebRun opens Syncplicity to check sync status. - Open each shared folder and check its current sync status
- Note any file stuck out of date or failed to sync
- Capture the affected user and device for each
Done when Every folder's sync status has been checked.
-
2
Airtable - log sync issues
airtable.com
WebRun opens Airtable to log sync issues. - Log each sync issue as a row with the affected folder and user
- Mark whether the issue is new or was already logged
- Close out rows for issues resolved since the last run
Done when Every current sync issue has a row in Airtable.
-
3
Gmail - email IT the summary
gmail.com
WebRun opens Gmail to email IT the summary. - Draft a short email to IT listing tonight's sync issues
- Sort by how long each issue has been open
- Send it to the IT distribution address
Done when IT has tonight's sync issue summary in Gmail.
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 force a resync or fix the failure itself?
No. WebRun only reads sync status and logs issues. Forcing a resync or fixing a device is left to IT.
How is an issue marked resolved?
It checks the live sync status each night, so an issue that clears on its own is closed out in Airtable automatically.
Does IT get emailed every single night even with no issues?
Yes, a short email goes out either way, so IT knows the check ran even on a clean night.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.