Automated Filmora Stalled Project Reports
Every Monday, WebRun opens Filmora, lists the projects with no edit in the last 14 days, checks the matching client folder in Google Drive for a delivered file, and posts Slack a short list of the edits that stalled and who owns each one.
How do I find video projects that have stalled mid-edit?
WebRun opens Filmora every Monday and lists the projects with no edit in the past 14 days. It checks the matching Google Drive folder to see whether a finished video was ever delivered, then posts Slack a ranked list of the genuinely stalled edits with the owner and days idle for each.
- Forgotten edits surface every Monday instead of at a client check-in
- Delivered work is filtered out, so the list stays short and real
- Every stalled project has a named owner and an age
Built for video editors · content studios · marketing teams · creative agencies
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
filmora.wondershare.comin a real browser with your saved login - no setup, no API keys. -
1
Filmora - find projects nobody has touched
WebRun opens Filmora to find projects nobody has touched. - Open Filmora and go to the project list
- Capture every project whose last modified date is more than 14 days ago
- Record the project name, the client or campaign it belongs to, and how long it has been idle
- Note whether the project has ever been exported or is still mid-edit
Done when Every project idle for more than 14 days is listed with its age and status.
-
2
Google Drive - check for a delivered file
WebRun opens Google Drive to check for a delivered file. - Open the deliveries folder in Google Drive
- Look for a finished video file matching each idle project name
- Mark projects with a delivered file as done and drop them from the chase list
- Mark projects with no matching file as genuinely stalled, and note the last asset date
Done when Each idle project is marked either delivered or genuinely stalled.
-
3
Slack - post the stalled edit list
WebRun opens Slack to post the stalled edit list. - Post the stalled edit list to your production channel in Slack
- Put the oldest and the highest-value client work at the top
- Give each line the project name, days idle, and the editor who owns it
- Leave the list for the team to action. Never message a client about a late edit
Done when The team has this week's stalled edit list in Slack.
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 delete or archive old projects?
No. WebRun only reads your project list and your Drive folder. It never deletes a project, moves a file, or renders anything. Clearing out old work stays a human decision made from the list it posts.
How long is too long for an idle project?
14 days by default. Set it to 7 if you turn edits around inside a week, or 30 if you run longer productions. The threshold is a single setting and the rest of the run is unchanged.
Will it chase clients about late edits?
No. The list goes to your internal Slack channel only. WebRun never emails or messages a client, so any conversation about a slipped deadline is one you choose to have.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.