Automated Clockify Project Budget Alerts
Every morning, WebRun opens Clockify, reads hours logged against every active project and compares them with the project estimate, posts a burn table to Microsoft Teams showing percent used and hours remaining, and texts the project lead on your saved list when a project crosses the threshold you set.
How do I know when a project is about to blow through its budgeted hours?
WebRun opens Clockify every morning and compares hours logged against each active project's estimate, calculating percent used, hours remaining, and the projected run-out date. It posts a burn table to Microsoft Teams with the closest-to-limit projects first, and texts the project lead when one crosses your threshold.
- An overrun is visible while there is still time to act, not at invoicing
- Every project shows percent used and a projected run-out date daily
- Projects without an estimate are named as untracked instead of guessed at
Built for agencies · consultancies · project managers · operations leads
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
clockify.mein a real browser with your saved login - no setup, no API keys. -
1
Clockify - compare hours against estimates
WebRun opens Clockify to compare hours against estimates. - Open Clockify and list every active project with an estimate set
- Read total hours logged against each project to date
- Calculate percent of estimate used and hours remaining
- Read the hours logged in the last 7 days to get the current weekly burn
- Project the date each budget runs out at that burn rate
Done when Every active project has percent used, hours left, and a projected run-out date.
-
2
Microsoft Teams - post the burn table
WebRun opens Microsoft Teams to post the burn table. - Post a burn table to your delivery channel
- Show project, estimate, hours used, percent used, and hours remaining
- Sort so the projects closest to their limit sit at the top
- Highlight anything already over its estimate in a separate line
- Keep projects under half their budget in a single summarised count
Done when The delivery channel has today's project burn table.
-
3
Twilio - text the lead on a breach
WebRun opens Twilio to text the lead on a breach. - Text the project lead when a project crosses your percentage threshold
- Send only to the numbers on the internal team list you saved
- Keep the text to project name, percent used, and hours left
- Never text a client and never send anything outside your saved list
- Stay silent on days when no project crosses the threshold
Done when Leads of over-burning projects have been texted, or nothing was sent.
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 text clients about a project going over?
No. Texts go only to the internal numbers on your saved team list. WebRun never contacts a client, and telling a client about an overrun stays a conversation your team chooses to have.
Can it edit time entries or change an estimate?
No. WebRun reads projects, estimates, and logged hours. It never edits a time entry, approves a timesheet, changes a rate, or raises a project budget.
What if a project has no estimate set?
It is listed separately as untracked rather than guessed at. WebRun never invents a budget, so a project with no estimate simply shows its hours used with no percentage.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.