Automated Strapi Cloud Content Publishing Digest
Every morning, WebRun opens Strapi Cloud, reviews content entries published, updated, or still in draft since yesterday, saves a dated export to Google Drive, and posts a short digest to Slack so the content and dev teams know what shipped.
How do I get a daily digest of what changed in my Strapi content?
WebRun checks Strapi Cloud every morning for entries published, updated, or left in draft since the day before, saves a dated backup export to Google Drive, and posts a short Slack digest with the counts and any drafts sitting unpublished for over a week, so the content team always knows what shipped.
- The team sees what published and what is still stuck in draft every morning
- Content changes are backed up to Drive automatically each day
- Drafts sitting untouched for a week get flagged instead of forgotten
Built for Content teams · headless CMS admins · marketing ops · product content managers
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
cloud.strapi.io/loginin a real browser with your saved login - no setup, no API keys. -
1
Strapi Cloud - check content changes
- Open the Strapi Cloud admin panel and review content entries changed since yesterday
- Group entries by published, updated, and still-in-draft status
- Note the content type and title for each changed entry
Done when Every entry changed since yesterday is grouped by status with its title and content type.
-
2
Google Drive - back up the content export
drive.google.com
WebRun opens Google Drive to back up the content export. - Open the Strapi Backups folder in Google Drive
- Save a dated export listing yesterday's published and updated entries
- Keep the most recent 30 days of exports and remove older ones
Done when A dated backup of yesterday's content changes is saved in Google Drive.
-
3
Slack - post the daily digest
slack.com
WebRun opens Slack to post the daily digest. - Post a digest to the content Slack channel
- List how many entries were published, updated, and left in draft
- Flag any draft entry that has been sitting unpublished for more than a week
Done when The content team has today's publishing 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
Will WebRun publish or unpublish content on its own?
No. WebRun only reads content status and reports on it. Publishing, unpublishing, or editing any entry stays a manual action in Strapi.
How far back does the backup export go?
Each daily export covers the previous day's changes, and WebRun keeps a rolling 30 days of exports in Google Drive.
What counts as a stale draft?
Any entry still in draft status seven days after its first save gets flagged in the Slack digest so an editor can follow up.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.