Automated Asset Dependency Alerts
Through the day, WebRun opens Vani Software, walks the asset dependency links, and finds shots that cannot progress because an upstream model, rig, or texture is unfinished, then pings the lead responsible for that asset on Telegram, so a blocking dependency is chased within hours instead of surfacing at the next production meeting.
How do I alert a lead when an asset dependency blocks a shot?
WebRun checks Vani Software every hour, walking the asset dependency links to find shots stalled by an unfinished upstream model, rig, or texture. It pings the responsible lead on Telegram once per blocker, naming the asset and the shots it holds up, so a bottleneck gets chased within hours instead of surfacing at the next production meeting.
- Blocking dependencies get chased within hours, not at the next meeting
- The right lead is nudged once per blocker, without spam
- Blocked shots read live from the Vani Software dependency graph
Built for VFX pipeline leads · asset supervisors · CG leads · animation production 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
vanisoftware.comin a real browser with your saved login - no setup, no API keys. -
1
Vani Software - find blocked dependencies
vanisoftware.com
WebRun opens Vani Software to find blocked dependencies. - Open Vani Software and read the asset status and dependency links for active shots
- Find shots waiting on an upstream asset that is not yet approved or delivered
- Identify the blocking asset, its current status, and the lead assigned to it
- Capture the downstream shots each blocked asset is holding up
Done when Every shot blocked by an unfinished upstream asset is listed with the responsible lead.
-
2
Telegram - ping the responsible lead
telegram.org
WebRun opens Telegram to ping the responsible lead. - Send the responsible lead a Telegram message naming the blocking asset and its status
- List the downstream shots that are stalled until the asset is ready
- Only notify once per blocker until its status changes, so leads are not spammed
- Keep it to an internal team nudge, no client or vendor is contacted
Done when Each lead has a Telegram nudge for every asset currently blocking their shots.
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 leads get pinged over and over for the same blocker?
No. WebRun notifies once per blocking asset and stays quiet until its status changes in Vani Software, so a lead gets a single clear nudge instead of a stream of repeat pings.
Does it contact anyone outside the team?
No. WebRun only messages the internal lead on Telegram. No client, vendor, or outside artist is ever contacted, so the nudge stays a private production signal.
How does it know which asset is blocking a shot?
It reads the asset dependency links in Vani Software, so it follows the same graph your pipeline uses. Any upstream asset that is unfinished and holding a downstream shot is flagged with its owner.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.