On a schedule
Get Friday's hours by project and person
At the end of each week you receive the hours your team logged, split by project and by person.
- Runs
- On a schedule
- Apps
- Harvest
- AI
- Not needed
- Access
- read (admin/manager)
Send this to your assistant
Create a ClickRuntime automation: every Friday at 5pm, email me this week's Harvest hours totalled by project and by person.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Friday afternoon is when project leads want to know where the week went. Who spent 31 hours on the website rebuild, how much of the team's time went into an unbillable internal project, which client absorbed the extra support work? Harvest has reports for all of it, but someone has to open the page, set the date range, run two or three views and copy the figures into an email or deck. It is the kind of chore that gets skipped in a busy week.
On Friday, the week's time reports are pulled from Harvest, formatted into a readable summary showing hours by project and hours by person, and emailed to you. The same layout arrives every week, so changes in where time goes are easy to notice.
It suits agency owners, delivery managers and finance leads who review utilization weekly.
What you get out of it
Weekly review takes minutes
The numbers arrive formatted and ready to read. The review can start with a conversation about what they mean instead of a hunt for the data. That makes the meeting about decisions rather than data collection, and it shortens the whole routine.
Utilization problems show up early
If a team member's billable hours drop for two weeks, you see it in time to rebalance work, rather than at the end of the quarter. Rebalancing work early is much cheaper than fixing an underused team member's quarter.
Project effort is visible to everyone
A summary that goes to leads and owners aligns people on where effort is really going, which helps with scope conversations with clients. It also gives account leads facts to bring to the next client conversation.
Unbillable time is easier to manage
Seeing hours spent on internal work each week keeps meetings, admin and pitching from quietly eating margin. Seeing those hours weekly keeps internal meetings, admin and pitching from quietly eating margin without anyone noticing.
A weekly archive in your inbox
Search your email for any week to see what the team did, which is handy for invoices, retrospectives and answering client questions months later. Searching for a week later is faster than rebuilding a report.
Fair workload conversations
Seeing hours by person each week supports honest talks about overload. If one person has logged 52 hours for three weeks, a manager can step in before burnout, and not after a resignation.
How it works
What happens, step by step
Every Friday at 5pm, ClickRuntime pulls this week's hours from Harvest.
It totals them by project and by person.
You get one email with both lists and the week's total hours in the subject line.
Before it runs live
- Connect Harvest
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Run it at a different time, more or less often, or only on weekdays
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Slack
- Combine it with other Harvest steps into one automation
Under the hood
The code that runs this automation
from datetime import date, timedelta
from clickruntime import on_trigger, notify, http, credentials
API = "https://api.harvestapp.com/v2/reports/time"
@on_trigger
def run(event):
headers = {"Authorization": "Bearer " + credentials.secret("HARVEST_TOKEN"),
"Harvest-Account-Id": credentials.secret("HARVEST_ACCOUNT_ID"), "User-Agent": "ClickRuntime"}
monday = date.today() - timedelta(days=date.today().weekday())
params = {"from": monday.isoformat(), "to": date.today().isoformat()}
projects = http.get(f"{API}/projects", headers=headers, params=params).json()["results"]
team = http.get(f"{API}/team", headers=headers, params=params).json()["results"]
by_project = "\n".join(f" {p['total_hours']:6.1f}h {p['client_name']} / {p['project_name']}" for p in sorted(projects, key=lambda p: -p["total_hours"]))
by_person = "\n".join(f" {u['total_hours']:6.1f}h {u['user_name']}" for u in sorted(team, key=lambda u: -u["total_hours"]))
total = sum(p["total_hours"] for p in projects)
notify.email_me(f"Harvest week of {monday:%b %d}: {total:.1f}h", f"By project\n{by_project}\n\nBy person\n{by_person}")
return {"hours": total}FAQ
Common questions
Does it include non-billable hours?
Which days does the week cover?
Can the summary go to clients?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Find out who didn't log their hours yesterday
Each weekday morning your channel lists the people whose tracked time for the previous day fell short.
See how it worksHear when a project uses 80% of its budget
You get one email for each project that crosses 80% of its budget, early enough to talk to the client.
See how it worksCatch Harvest timers left running in the evening
At 7pm you get a list of any timers still going, with the person, project and hours so far, and no email when there are none.
See how it worksKeep exploring
Set up “Get Friday's hours by project and person” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.