Catch the goals that stopped moving mid cycle
Every Monday, WebRun opens Leapsome, reads the goals in the current cycle with their owner and last progress update, creates a Trello card for every objective that has gone quiet, and logs the week's stall count in Airtable so the trend across the quarter is visible.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I find goals that have stopped getting progress updates?
WebRun opens Leapsome every Monday and reads the goals in the current cycle, capturing each objective's owner, progress and last update date. It cards every goal that has gone quiet in Trello and logs the week's stall count in Airtable, so a drifting objective gets corrected during the quarter.
- A stalled objective is caught mid quarter, not at review time
- Every quiet goal is grouped under the person who owns it
- The stall trend across the cycle is recorded week by week
Built for people leads · HR teams · engineering managers · scaling companies
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
leapsome.comin a real browser with your saved login - no setup, no API keys. -
1
Leapsome - find goals with no progress update
WebRun opens Leapsome to find goals with no progress update. - Open Leapsome and go to the goals for the current cycle
- Capture each goal's owner, current progress and the date of its last update
- Flag goals with no progress update since the cycle started or since your staleness threshold
Done when Every stalled goal is listed with its owner and last update date.
-
2
Trello - card each stalled goal
WebRun opens Trello to card each stalled goal. - Create a card per stalled goal with the objective, its owner and days since the last update
- Group cards by owner so a manager sees their whole set at once
- Close cards for goals that were updated since the previous run
Done when Each stalled goal has a card assigned to its owner.
-
3
Airtable - log the stall trend
WebRun opens Airtable to log the stall trend. - Write a weekly row with the number of stalled goals and how many are newly stalled
- Record which teams and owners appear most often across the cycle
- Keep every week of the cycle so the trend is readable at review time
Done when This week's stall count is recorded against the cycle.
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 message goal owners directly?
No. WebRun creates internal Trello cards and an Airtable log. It never emails or notifies an employee, so the conversation stays with you and their manager.
Does it edit goals or progress in Leapsome?
No. WebRun reads the goals module only. Updating progress, changing a target or closing a goal stays with the owner inside Leapsome.
How does it decide a goal has stalled?
It uses the staleness threshold you set, measured in days since the last progress update. Goals updated inside that window are left alone entirely.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.