Automated Flywheel Plugin Update Audits
Every night, WebRun signs into Flywheel, walks every WordPress site on the account, records which plugins, themes, and core versions are behind, checks a recent backup exists, files the audit in Google Drive, and WhatsApps you the sites that need patching first.
How do I track outdated WordPress plugins across all my Flywheel sites?
Every night, WebRun signs into Flywheel, walks each WordPress site, and records the plugins, themes, and core versions that are behind. It checks a recent backup exists, files the audit in Google Drive, and WhatsApps you the sites furthest behind, so patching happens before a client site breaks.
- The update backlog is visible per site every single night
- Sites with no recent backup are flagged before anyone patches them
- Client maintenance reports come straight from the Google Drive history
Built for WordPress agencies · freelance web developers · site maintenance teams · in-house marketing 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
getflywheel.comin a real browser with your saved login - no setup, no API keys. -
1
Flywheel - audit plugins and themes per site
getflywheel.com
WebRun opens Flywheel to audit plugins and themes per site. - Open Flywheel and list every site on the account
- For each site, record the WordPress core version and the plugins and themes with an update available
- Note how many versions behind each plugin is and whether a staging site exists
- Confirm a recent backup is in place before the site is marked safe to patch
Done when Every site has its update backlog and backup status recorded.
-
2
Google Drive - file the nightly report
drive.google.com
WebRun opens Google Drive to file the nightly report. - Write tonight's audit into your maintenance report in Google Drive
- One row per site with core version, count of outdated plugins and themes, and backup date
- Keep the previous nights so you can see a backlog growing or shrinking
- Name the file with the date so month-end reporting to clients is a copy and paste
Done when Tonight's audit is filed in Google Drive alongside the history.
-
3
WhatsApp - flag the sites furthest behind
whatsapp.com
WebRun opens WhatsApp to flag the sites furthest behind. - Send your maintenance chat in WhatsApp the sites that need patching first
- Rank by how far behind the site is, with core version updates above plugin updates
- Call out any site that is behind and has no recent backup
- Leave running the updates to a person. WebRun never installs an update or touches a live site
Done when The team has tonight's patch list, ranked by how far behind each site is.
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 install the updates itself?
No. WebRun only reads what is behind and reports it. Installing a plugin, theme, or core update stays a human decision, so a client site is never changed overnight without someone choosing to.
How does it decide what to patch first?
It ranks by how far behind each item is, puts WordPress core updates above plugin and theme updates, and flags any site that is behind and has no recent backup on record.
Does it check backups before recommending an update?
Yes. Each site's most recent backup date is recorded in the audit, and a site that is behind with no recent backup is called out separately so you restore that safety net first.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.