Automated Workfront Weekly Request Scorecard
Every Friday, WebRun opens Workfront, pulls the status of every open request and pending approval across the queue, logs the full weekly scorecard to Google Sheets for the record, and updates the shared status page in Notion so stakeholders can check progress without filing another request.
How do I get a weekly scorecard of open Workfront requests?
WebRun checks Workfront every Friday for the status of every open request and pending approval, logs the full scorecard to Google Sheets for the record, and updates a shared Notion status page, so stakeholders can see where their request stands without filing a follow-up or waiting on a status meeting.
- Stakeholders can check request status without filing a follow-up
- Overdue requests get flagged automatically every week
- A running scorecard builds up in Sheets for reporting
Built for PMOs · marketing operations · enterprise IT · shared services 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
www.workfront.comin a real browser with your saved login - no setup, no API keys. -
1
Workfront - pull the status of every open request and approval
- Open the request queue and approval inbox
- Collect the status and age of every open item
- Flag requests waiting longer than the team's target turnaround
Done when Every open request and approval has a status and age recorded.
-
2
Google Sheets - log the weekly scorecard
google.com
WebRun opens Google Sheets to log the weekly scorecard. - Open the weekly scorecard sheet
- Append this week's counts by status and requester
Done when The sheet has this week's full scorecard logged.
-
3
Notion - update the shared status page
notion.so
WebRun opens Notion to update the shared status page. - Open the shared status page
- Update the summary with this week's open, approved, and overdue counts
Done when The status page reflects this week's scorecard.
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 approve or reject any requests?
No. It only reads the current status of each request. Approving, rejecting, or reassigning is always done by the approver in Workfront.
Can stakeholders see this without a Workfront login?
Yes. That's the point of updating the Notion status page: they can check progress there without needing access to Workfront itself.
How is a request flagged as overdue?
By comparing its age against the team's target turnaround time, using the status already visible in the Workfront queue.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.