Generate Stale Page Reports for Confluence Spaces (REST API v1 & v2)

This n8n workflow is designed to identify and report on stale pages within Confluence spaces using both Confluence REST API v1 and v2. It provides a flexible way to manage content freshness by allowing you to define what constitutes a "stale" page and then process those pages.

What it does

This workflow performs the following key steps:

1. Manual Trigger: The workflow is initiated manually, allowing for on-demand execution.
2. Sticky Note: Provides a descriptive note about the workflow's purpose.
3. Edit Fields (Set): This node is likely used to define parameters or initial data for the workflow, such as Confluence instance details, authentication tokens, or criteria for "stale" pages (e.g., last modified date threshold).
4. HTTP Request: Makes a request to the Confluence API (either v1 or v2 based on configuration) to fetch page data for a specified space. This will retrieve information about pages, including their last modification dates.
5. Split Out: If the API response contains an array of pages or nested data, this node will split each item into a separate n8n item for individual processing.
6. Filter: This node applies logic to determine if a page is "stale" based on the criteria defined in the "Edit Fields" node. It will likely compare the page's last modified date against a threshold. Pages that meet the "stale" criteria will pass through.
7. Aggregate: After filtering, this node collects all the "stale" page items back into a single item or a consolidated list, preparing them for further reporting or action.
8. Switch: This node likely provides conditional branching based on the aggregated results. For example, it might check if any stale pages were found, and if so, proceed to a reporting step, or if not, end the workflow or send a "no stale pages" notification.

Prerequisites/Requirements

• n8n Instance: A running instance of n8n.
• Confluence Instance: Access to a Confluence instance.
• Confluence API Token/Credentials: An API token or username/password with sufficient permissions to read page data from Confluence spaces.
• HTTP Request Node Configuration: Proper configuration of the HTTP Request node with your Confluence instance URL and authentication details.
• "Stale" Page Definition: You will need to define the logic for what constitutes a "stale" page within the "Edit Fields" and "Filter" nodes (e.g., pages not updated in the last 90 days).

Setup/Usage

1. Import the Workflow: Import the provided JSON into your n8n instance.
2. Configure Credentials:
   • Open the "Edit Fields" node and configure any necessary parameters, such as your Confluence base URL, API token, or the number of days after which a page is considered stale.
   • Ensure the "HTTP Request" node is correctly configured with your Confluence instance URL and authentication (e.g., Bearer Token for API v2, or Basic Auth for API v1).
3. Define Stale Logic: Adjust the "Filter" node's conditions to accurately reflect your definition of a "stale" page based on the data retrieved from Confluence.
4. Add Reporting/Action Nodes: After the "Aggregate" and "Switch" nodes, you will typically add further nodes to handle the identified stale pages. This could include:
   • Sending a report to Slack, email, or a Google Sheet.
   • Updating a task in a project management tool.
   • Triggering a review process for the identified pages.
5. Execute the Workflow: Click "Execute Workflow" to run it manually and test its functionality.