Automated Sticky Password Health Export
Every Monday, WebRun opens Sticky Password, reads the team's security audit for weak, reused, and old passwords, exports the counts to Google Drive, and texts IT via Twilio when the weak password count crosses your threshold.
How do I track my team's Sticky Password health and get alerted past a threshold?
WebRun checks Sticky Password every Monday for the team's weak, reused, and old password counts, exports the figures to Google Drive alongside prior weeks, and texts IT via Twilio when the weak count crosses your threshold. It only reads the aggregate audit, never an actual saved password.
- Password health trend is exported every week, not just at audit time
- IT gets a text only when the weak count crosses your threshold
- WebRun never opens, types, or stores an actual password
Built for IT admins · small business owners · security teams · MSPs
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.stickypassword.comin a real browser with your saved login - no setup, no API keys. -
1
Sticky Password - read the security audit
WebRun opens Sticky Password to read the security audit. - Open the Sticky Password admin console and check the team security audit
- Read the counts of weak, reused, and old passwords across the team
- Never open, view, or copy an actual saved password
Done when This week's weak, reused, and old password counts are read.
-
2
Google Drive - export the weak password counts
WebRun opens Google Drive to export the weak password counts. - Open the password health tracking folder in Google Drive
- Export this week's counts alongside prior weeks so the trend is visible
- Keep the file updated in place rather than creating duplicates
Done when This week's counts are saved to Google Drive.
-
3
Twilio - text IT past the threshold
WebRun opens Twilio to text IT past the threshold. - If the weak password count is above your set threshold, text the IT lead via Twilio
- Include the count and a link to the exported file
- Stay silent when the count is under threshold to avoid noise
Done when IT has been texted whenever the weak password 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
Does WebRun ever see or handle an actual password?
No. WebRun only reads the aggregate audit counts from Sticky Password's own dashboard. It never opens, types, or stores a password, key, or seed.
Will it fix a weak or reused password?
No. It only exports the counts and alerts past your threshold. Updating a specific password is always done by that user.
What sets the alert threshold?
You set the weak password count that should trigger a text. WebRun only texts IT once that count is reached or crossed.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.