Monthly
Find Confluence pages nobody has updated
Each month you get the pages in a space untouched for six months, with their author and a link, ready for review.
- Runs
- Monthly
- Apps
- Confluence
- AI
- Not needed
- Access
- read
Send this to your assistant
Create a ClickRuntime automation: on the 1st of each month, email me every page in Confluence space DOCS that hasn't been updated in 180 days, with the author, last update date and link.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Documentation decays quietly. A page written two years ago still shows up in search, still looks authoritative, and describes a process that changed last spring. New hires follow it, make mistakes, and lose trust in the whole wiki.
Once a month, this searches your space for pages that nobody has updated in the last 180 days, collects each page's title, author and last-updated date, and emails you the list. Instead of guessing which pages are old, you receive a concrete worklist for a cleanup.
It is aimed at documentation owners, support leads and team leads who want a regular, low-effort way to keep a wiki trustworthy. The 180 day rule is applied in the search itself, so you receive only the pages that really have not been touched, with their authors and dates ready for a review.
What you get out of it
Keep trusted documents trustworthy
When old pages are reviewed or archived, search results lead to current information. Employees stop learning that the wiki cannot be relied on. Employees who find current answers in search stop doubting the wiki, and the habit of using it survives.
Give each page an owner to chase
The list includes authors, so you know whom to ask whether a page is still true. It turns a vague cleanup into a set of small questions. Authors are named in the list, so a vague cleanup becomes a set of quick questions about whether each page is still true.
Reduce mistakes from outdated procedures
An obsolete onboarding or deployment guide causes real errors. Finding it during a monthly review prevents the next person from following wrong steps. An obsolete onboarding or deployment guide causes mistakes, and the monthly review catches it before another person follows it.
Shrink the wiki to what matters
Archiving pages nobody needs makes search cleaner. The monthly list shows candidates without anyone trawling through the space tree. Archiving pages nobody needs makes search results cleaner, and you pick candidates from the list and not by browsing the tree.
Prepare for audits and reviews
Regular evidence of content review supports quality processes. The emails show that pages were checked on a schedule. Regular proof that documents are reviewed supports quality systems, and the monthly emails show that checks happened on schedule.
How it works
What happens, step by step
Once a month, ClickRuntime looks through your Confluence space for pages that haven't been updated in six months.
For each one it notes the title, the author and when it was last updated.
You get the list by email, so you can review, update or archive old pages.
Before it runs live
- Connect Confluence
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Run it at a different time, more or less often, or only on weekdays
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Slack
- Combine it with other Confluence steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_trigger, notify, http, credentials
SITE = "https://northwind.atlassian.net"
@on_trigger
def run(event):
auth = (credentials.secret("CONFLUENCE_EMAIL"), credentials.secret("CONFLUENCE_API_TOKEN"))
lines, start = [], 0
while True:
data = http.get(f"{SITE}/wiki/rest/api/content/search", auth=auth, params={
"cql": 'space = DOCS and type = page and lastmodified < now("-180d") order by lastmodified',
"expand": "version,history", "limit": 100, "start": start,
}).json()
for p in data["results"]:
lines.append(f"{p['title']} | {p['history']['createdBy']['displayName']} | last updated {p['version']['when'][:10]}\n{SITE}/wiki{p['_links']['webui']}")
if data["size"] < 100:
break
start += 100
notify.email_me(f"{len(lines)} stale pages in DOCS", "\n\n".join(lines) or "No pages older than 180 days.")
return {"stale": len(lines)}FAQ
Common questions
What counts as a stale page?
Can I use a different time period such as 90 days?
Does it cover blog posts and attachments?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Get a Friday list of changed Confluence pages
One email at the end of the week lists every page created or updated, grouped by space.
See how it worksGet a weekly summary of what changed in your docs
On Fridays you read a few lines per page explaining what was added or changed, instead of opening each one.
See how it worksPost Confluence page edits to Slack
When a page in your space is changed, your channel sees its title, who edited it and a link.
See how it worksKeep exploring
Set up “Find Confluence pages nobody has updated” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.