# Confluence - Stale Page Report

> Identify outdated and potentially risky Confluence pages automatically.

The Confluence - Stale Page Report workflow helps teams regain visibility over outdated documentation by automatically detecting pages that haven't been updated within a defined time frame. Instead of manually reviewing spaces, the workflow scans selected Confluence spaces and produces a clear, actionable report of stale content.

- Area: n8n Automation
- Type: Free
- Category: IT Operations
- n8n template: https://n8n.io/workflows/12237-generate-stale-page-reports-for-confluence-spaces-with-rest-api-v1-and-v2/
- Source: https://www.sus-tech.com/en/solutions/confluence-stale-page-report

## Confluence - Stale Page Report

Keep your Confluence documentation accurate, relevant and actively maintained by automatically identifying outdated pages.

### What this workflow solves
Over time, Confluence spaces tend to accumulate outdated or forgotten pages. Manually reviewing content is time-consuming and error-prone. This workflow automates the process by generating a clear report of pages that have not been updated within a configurable time window.

### Key features
- Detects Confluence pages **not updated within a defined cutoff period** (in days)
- Supports both:
  - Confluence REST API v1 (CQL search) for legacy setups
  - Confluence REST API v2 (spaces + pages) for modern environments
- Produces a consolidated report containing:
  - Page title
  - Page status
  - Last updated date
  - Days overdue
  - Direct page URL
- Ideal for:
  - Content audits
  - Documentation hygiene
  - Ownership and responsibility reviews

### How it works
- The workflow is triggered manually.
- Configuration is handled via a single **Set Variables** node:
  - Atlassian domain
  - Space keys to scan
  - Cutoff age (in days)
  - API version toggle (v1 or v2)
- Depending on the selected API version:
  - v1 uses a CQL search to retrieve outdated pages
  - v2 fetches spaces and pages, then filters by last modification date
- All results are normalized and aggregated into a single `stalePages` array for easy reuse.

### Setup requirements
- Atlassian / Confluence Cloud account
- HTTP Basic Auth credential (email + API token)
- Optional extensions:
  - Email or Slack notifications
  - CSV or spreadsheet export
  - Scheduled execution for recurring audits

### Notes
- API v2 is recommended for future-proof setups.
- Default pagination is limited to 50 pages per request.
- Tested with Confluence Cloud environments.

## Related blog posts

- [Maintaining Documentation Compliance: Automating Stale Content Detection in Confluence](https://www.sus-tech.com/en/blog/maintaining-documentation-compliance-in-confluence.md)

## Contact

Consulting and implementation: https://www.sus-tech.com/en/contact