Jirav Automated Model Refresh Reminders
Every Monday, WebRun opens Jirav and checks the last-updated timestamp on each financial model, identifies any model that has not been refreshed within your configured window, creates Google Calendar reminders for the responsible finance team members, and logs each stale model in an Airtable refresh queue so the team has a single place to track and close out outstanding updates.
How do I automatically send financial model refresh reminders from Jirav?
WebRun checks every Jirav financial model each Monday for stale last-updated timestamps, creates Google Calendar reminders for the responsible finance team members, and logs each outstanding model in an Airtable refresh queue. Resolved models are automatically marked closed on the next run, keeping the queue current without any manual tracking.
- Stale financial models flagged every Monday before they affect forecasts
- Each team member gets a calendar reminder tied to the model they own
- Refresh queue in Airtable gives finance a single place to track all outstanding updates
Built for FP and A teams · finance managers · financial planning analysts · CFOs · corporate controllers
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
app.jirav.comin a real browser with your saved login - no setup, no API keys. -
1
Jirav - check model last-updated timestamps
jirav.com
WebRun opens Jirav to check model last-updated timestamps. - Open Jirav and navigate to the financial models list
- Read the last-updated timestamp for each model
- Identify models that have not been updated within the staleness window you configured (for example, 7 days)
- Note the model name, owner, and days since last update for each stale model
Done when Every stale financial model is identified with its name, owner, and days overdue.
-
2
Google Calendar - create refresh reminders
calendar.google.com
WebRun opens Google Calendar to create refresh reminders. - Create a calendar reminder for each stale model on the responsible team member's calendar
- Set the reminder title to include the model name and the number of days since last update
- Schedule the reminder for the next available working day so it surfaces at the right time
Done when A Google Calendar reminder exists for each stale model, assigned to the responsible team member.
-
3
Airtable - log the refresh queue
airtable.com
WebRun opens Airtable to log the refresh queue. - Open the Airtable refresh queue base
- Add a new record for each stale model with fields: model name, owner, last updated date, days overdue, and status set to Open
- Update existing records for models already in the queue to reflect the current days-overdue count
- Mark any models in the queue as Refreshed if their Jirav timestamp has been updated since the last run
Done when The Airtable refresh queue reflects the current state of every stale model, with new records added and resolved ones marked closed.
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
How does WebRun know which team member owns each Jirav model?
WebRun reads the owner field already recorded in Jirav for each model. During setup you map Jirav owner names to their Google Calendar accounts, so reminders land on the right person's calendar automatically.
Will reminders be sent externally or emailed to stakeholders?
No external emails are sent. All reminders are internal Google Calendar events and Airtable records visible only to your finance team. WebRun never sends email or external notifications on its own.
What happens when a model is refreshed after a reminder is created?
On the next run, WebRun re-reads the Jirav timestamps and marks any previously stale model as Refreshed in the Airtable queue. The corresponding calendar reminder is left in place, as the team member can dismiss it once the update is confirmed.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.