Automated Tome Weekly Deck Backup
Every Monday, WebRun opens Tome, exports decks created or edited in the last week as backup files, saves them to a dated folder in Google Drive, and posts a digest to Slack listing what was made so nothing lives only inside one account.
How do I back up my team's Tome decks automatically?
WebRun exports Tome decks created or edited in the last week as dated backups in Google Drive, and posts a Slack digest listing what was made and by whom every Monday. Presentation work gets a standing off-app backup and a visible weekly record instead of living only inside individual Tome accounts.
- Every deck gets a weekly off-app backup automatically
- The team sees what was created without checking Tome directly
- No presentation work lives only in one person's account
Built for Startup teams · sales teams · marketing teams · consultants
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
tome.appin a real browser with your saved login - no setup, no API keys. -
1
Tome - check decks created or edited
tome.app
WebRun opens Tome to check decks created or edited. - Open Tome and check decks created or edited in the last week
- Export each one as a backup file
- Note the deck title and who last edited it
Done when Every deck touched this week has an export ready.
-
2
Google Drive - save the backup exports
drive.google.com
WebRun opens Google Drive to save the backup exports. - Open the deck backups folder in Google Drive
- Save each export with the deck title and this week's date
- Keep prior weeks' backups in place
Done when This week's decks are backed up and dated in Drive.
-
3
Slack - post the weekly digest
slack.com
WebRun opens Slack to post the weekly digest. - Post the list of decks created or edited this week to the team channel
- Note who worked on each one
- Link to the backed-up copy in Drive
Done when The team has this week's deck digest 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
Does it edit or delete any deck in Tome?
No. WebRun only reads and exports a copy of decks that were already created or edited. Nothing in Tome itself is changed.
Who can see the backed-up decks?
Only whoever has access to the Google Drive folder you point WebRun at. The Slack digest only names the deck titles and editors.
What if no decks were touched last week?
The Slack digest still posts and simply notes there were no changes, so the team knows the check ran.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.