HumationHuman + Automation
Back to Catalog

Scan Confluence pages with the REST API for inactive page owners

Alexander SchnablAlexander Schnabl
14 views
2/3/2026
SlackWebhookNotificationsData ValidationSalesforce
Official Page

Scan Confluence pages for inactive page owners

This workflow scans selected Confluence spaces, resolves page ownership and filters pages with inactive owners, helping teams maintain clear ownership and prevent orphaned documentation.

What it does

  • Scans Confluence pages across selected spaces.

  • Resolves page owners and checks their account status.

  • Filters pages where the owner is inactive (owner.accountStatus !== active).

  • Uses Confluence REST API v2 to fetch spaces, pages, and user data.

  • Resolves page owners efficiently via the users-bulk API.

  • Produces a consolidated report containing:

    • Page title

    • Owner email

    • Owner account status

    • Last updated date

    • Direct page URL

  • Useful for documentation governance, ownership audits, and cleanup initiatives.

How it works

  • A Set Variables node defines:

    • Atlassian domain

    • Space keys to scan

  • Get Spaces (v2) retrieves matching spaces and extracts their IDs.

  • Get Pages (v2) fetches all pages from the selected spaces.

  • Unique page ownerIds are collected and resolved using Bulk User Lookup (v2).

  • Page metadata is merged with user account data (ownerId ↔ accountId).

  • Pages are filtered to include only those with inactive owners.

Setup

  • Configure the Set Variables node:

    • atlassianDomain → your Confluence base URL

    • spaceKeys → comma-separated list of space keys (e.g. ENG, HR)

  • Create an HTTP Basic Auth credential:

    • Atlassian email + API token

    • Assign it to all HTTP Request nodes

  • Optional enhancements:

    • Add pagination if spaces contain many pages.

    • Extend the workflow with email notifications, Slack alerts, or CSV export.

Notes

  • Requires permission to read Confluence spaces, pages, and users.

  • Pages are flagged when owner.accountStatus !== active.

  • Current page fetch limit is 50 items per request.

Confluence Inactive Page Owner Scanner

This n8n workflow scans Confluence pages via the REST API to identify pages with inactive owners. It helps maintain a clean and up-to-date Confluence instance by flagging pages whose owners may no longer be active within the organization, potentially indicating orphaned content.

What it does

  1. Manual Trigger: Starts the workflow when manually executed.
  2. HTTP Request (Get Pages): Fetches a list of pages from a Confluence instance using its REST API.
  3. Split Out: Takes the array of pages received from Confluence and processes each page individually.
  4. Edit Fields (Set Page Owner): Extracts and sets the owner information for each page (details of the owner extraction logic are not fully visible in the provided JSON, but this step is intended for data manipulation).
  5. Merge: Combines the processed page data back into a single item or a structured list. This likely prepares the data for a subsequent HTTP request.
  6. HTTP Request (Check Owner Status): For each page owner, makes another API call (likely to an identity management system or another Confluence endpoint) to check if the owner is active or inactive.
  7. Filter: Evaluates the status of each page owner. It passes through only those pages where the owner is identified as inactive.
  8. Aggregate: Collects all pages identified with inactive owners into a single output. This step prepares a consolidated list for further action.

Prerequisites/Requirements

  • Confluence Instance: Access to a Confluence instance with the necessary REST API permissions to read page content and potentially user information.
  • Confluence API Token/Credentials: An API token or username/password for authenticating with the Confluence REST API.
  • Identity Management System (Optional): If checking owner activity requires querying an external system (e.g., Active Directory, Okta, internal user database), credentials and API access to that system will be needed.
  • n8n Instance: A running n8n instance to host and execute the workflow.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Confluence API Credentials:
    • Locate the "HTTP Request" nodes (specifically the one labeled "HTTP Request (Get Pages)").
    • Configure the Authentication section with your Confluence API token or username/password.
    • Update the URL to point to your Confluence instance's API endpoint for fetching pages (e.g., https://your-confluence-domain.com/rest/api/content).
  3. Configure Owner Status Check (if applicable):
    • Locate the "HTTP Request (Check Owner Status)" node.
    • Configure its Authentication and URL to query your identity management system or Confluence for user activity status. You will need to ensure the request correctly uses the owner information passed from previous nodes.
  4. Review "Edit Fields" and "Filter" Nodes:
    • Examine the "Edit Fields" node to understand how page owner data is being extracted and transformed. Adjust if your Confluence page structure or user data differs.
    • Review the "Filter" node's conditions to ensure it correctly identifies "inactive" owners based on the response from the "Check Owner Status" API call.
  5. Execute the Workflow: Click "Execute Workflow" to run the scan.
  6. Review Results: The "Aggregate" node will output a consolidated list of pages with inactive owners. You can then connect further nodes (e.g., a Slack node to send notifications, a Google Sheets node to log the findings, or another HTTP Request to update Confluence page labels) to act on these results.

Related Templates

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616