Automated Prismic Stale Draft Content Chase
Every morning, WebRun opens Prismic, reviews draft documents across your repository, finds any sitting unpublished for more than a week, creates a Trello card for tracking, and messages the content owner on WhatsApp so finished content does not quietly stay unpublished.
How do I stop Prismic drafts from sitting unpublished for weeks?
WebRun reviews Prismic draft documents every morning, finds any sitting unpublished for more than a week, and creates a Trello card for tracking. It then messages the content owner directly on WhatsApp, so finished content that is ready to go does not quietly sit in draft status because everyone assumed someone else would publish it.
- Stale drafts get a card and a ping within a day of going stale
- Content owners are notified directly instead of relying on someone noticing
- Finished content stops sitting unpublished by accident
Built for Content teams · marketing teams · headless CMS admins · editorial 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
prismic.io/dashboardin a real browser with your saved login - no setup, no API keys. -
1
Prismic - review draft documents
- Open Prismic and review draft documents across the repository
- Check how long each has sat in draft status
- Flag anything unpublished for more than seven days and note its owner
Done when Every draft unpublished for more than seven days is identified with its owner.
-
2
Trello - create the follow-up card
trello.com
WebRun opens Trello to create the follow-up card. - Open the Content Follow-ups Trello board
- Create a card for each stale draft with its title and a link to Prismic
- Place it in the Needs Decision column
Done when A Trello card exists for every draft unpublished for more than a week.
-
3
WhatsApp - ping the content owner
whatsapp.com
WebRun opens WhatsApp to ping the content owner. - Message the content owner on WhatsApp
- Include the document title and how long it has been in draft
- Ask them to publish it or confirm it is intentionally on hold
Done when The content owner has been messaged about every stale draft.
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 the draft itself?
No. It only tracks how long a draft has waited and notifies the owner. Publishing any document stays a manual decision made in Prismic.
What if a draft is intentionally on hold?
It still gets listed for visibility, but once the owner confirms it is intentionally on hold, the team knows it is not simply forgotten.
Does it cover every content type?
Yes, every document type in the repository you connect it to, so nothing published by one team gets missed because it uses a different content type.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.