HumationHuman + Automation
Back to Catalog

Cluster webpage topics from Google Sheets to Google Sheets for AI discovery

Rahul JoshiRahul Joshi
143 views
2/3/2026
Conditional LogicEmail AutomationWebhookCRM IntegrationData Entry
Official Page

📊 Description

Streamline AI-focused SEO research by automatically analyzing URLs stored in Google Sheets, extracting semantic signals from each webpage, and generating high-quality topic clusters for AI discovery. 🤖🔍 This automation fetches URLs weekly, scrapes headings (H1–H6), extracts entities, keywords, topics, and summaries using GPT-4o-mini, and classifies each page into clusters and subclusters optimized for LLM search visibility. It also generates internal linking suggestions for better topical authority and writes all results back into Google Sheets. Perfect for content strategists, SEO teams, and AI-search optimization workflows. 📈🧩

🔁 What This Template Does

1️⃣ Triggers weekly to process URLs stored in Google Sheets. 📅 2️⃣ Fetches all URL records from the configured sheet. 📥 3️⃣ Processes URLs in batches to avoid API overload. 🔁 4️⃣ Extracts webpage HTML and pulls semantic headings (H1–H6). 📰 5️⃣ Sends headings + URL context to GPT-4o-mini for structured extraction of: — title — entities — keywords — topics — summary 6️⃣ Generates high-level cluster + subcluster labels for each page. 🧠 7️⃣ Recommends 3–5 internal linking URLs to strengthen topical authority. 🔗 8️⃣ Updates Google Sheets with all extracted fields + status flags. 📊 9️⃣ Repeats the process until all URLs are analyzed. 🔄

⭐ Key Benefits

✅ Automates topical clustering for AI search optimization ✅ Extracts entities, keywords, and topics with high semantic accuracy ✅ Strengthens internal linking strategies using AI suggestions ✅ Eliminates manual scraping and analysis work ✅ Enables scalable content audits for large URL datasets ✅ Enhances visibility in AI-driven search systems and answer engines

🧩 Features

  • Google Sheets integration for input + output
  • HTML parsing for H1–H6 extraction
  • GPT-4o-mini structured JSON extraction
  • Topic clustering engine (cluster & subcluster classification)
  • Internal linking recommendation generator
  • Batch processing for large URL datasets
  • Status-based updating in Google Sheets

🔐 Requirements

  • Google Sheets OAuth2 credentials
  • OpenAI API key (GPT-4o-mini)
  • Publicly accessible URLs (or authenticated HTML if applicable)
  • n8n with LangChain nodes enabled

🎯 Target Audience

  • SEO teams performing semantic clustering at scale
  • Content strategists creating AI-ready topic maps
  • Agencies optimizing large client URL collections
  • AI-search consultants building structured content libraries
  • Technical marketers needing automated content analysis

Cluster Webpage Topics from Google Sheets to Google Sheets for AI Discovery

This n8n workflow automates the process of extracting webpage content from URLs listed in a Google Sheet, using an AI agent to identify key topics, and then writing these topics back to another Google Sheet. This is particularly useful for content analysis, SEO research, or competitive intelligence, allowing for efficient discovery of themes across multiple web pages without manual review.

What it does

  1. Triggers on Schedule: The workflow is set to run periodically (e.g., daily, weekly) to check for new URLs.
  2. Reads URLs from Google Sheet: It fetches URLs from a specified Google Sheet.
  3. Fetches Webpage Content: For each URL, it makes an HTTP request to retrieve the HTML content of the webpage.
  4. Extracts Main Content: It then uses an HTML node to extract the main textual content from the fetched HTML, focusing on relevant elements like paragraphs and headings.
  5. Processes in Batches: URLs are processed in batches to manage API limits and improve efficiency.
  6. Analyzes with AI Agent: An AI Agent (powered by an OpenAI Chat Model) analyzes the extracted webpage content to identify and cluster key topics.
  7. Structures AI Output: A Structured Output Parser ensures the AI's response is in a usable, structured format (e.g., JSON).
  8. Writes Topics to Google Sheet: Finally, the identified topics are written to a designated output Google Sheet, associating them with their original URLs.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Google Sheets Account: Access to Google Sheets to read input URLs and write output topics.
  • Google Sheets Credentials: Configured Google Sheets credentials in n8n.
  • OpenAI API Key: An OpenAI API key with access to chat models (e.g., GPT-3.5, GPT-4) for the AI Agent.
  • OpenAI Credentials: Configured OpenAI credentials in n8n.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON workflow.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the three dots next to the "New Workflow" button and select "Import from JSON".
    • Paste the workflow JSON or upload the file.
  2. Configure Credentials:
    • Locate the "Google Sheets" nodes and configure your Google Sheets credentials.
    • Locate the "OpenAI Chat Model" node and configure your OpenAI API key credentials.
  3. Configure Google Sheets Input:
    • In the first "Google Sheets" node, specify the spreadsheet ID and sheet name where your URLs are listed. Ensure the column containing URLs is correctly referenced.
  4. Configure Google Sheets Output:
    • In the final "Google Sheets" node, specify the spreadsheet ID and sheet name where the extracted topics should be written. Configure the column mappings to match the AI's output structure (e.g., URL, Topic 1, Topic 2).
  5. Configure Schedule Trigger:
    • Adjust the "Schedule Trigger" node to your desired frequency for running the workflow (e.g., once a day, every hour).
  6. Activate the Workflow:
    • Save and activate the workflow. It will now run automatically according to the schedule.

This workflow provides a powerful, automated way to gain insights from a large collection of web pages, streamlining content analysis and research efforts.

Related Templates

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

Tax deadline management & compliance alerts with GPT-4, Google Sheets & Slack

AI-Driven Tax Compliance & Deadline Management System Description Automate tax deadline monitoring with AI-powered insights. This workflow checks your tax calendar daily at 8 AM, uses GPT-4 to analyze upcoming deadlines across multiple jurisdictions, detects overdue and critical items, and sends intelligent alerts via email and Slack only when immediate action is required. Perfect for finance teams and accounting firms who need proactive compliance management without manual tracking. 🏛️🤖📊 Good to Know AI-Powered: GPT-4 provides risk assessment and strategic recommendations Multi-Jurisdiction: Handles Federal, State, and Local tax requirements automatically Smart Alerts: Only notifies executives when deadlines are overdue or critical (≤3 days) Priority Classification: Categorizes deadlines as Overdue, Critical, High, or Medium priority Dual Notifications: Critical alerts to leadership + daily summaries to team channel Complete Audit Trail: Logs all checks and deadlines to Google Sheets for compliance records How It Works Daily Trigger - Runs at 8:00 AM every morning Fetch Data - Pulls tax calendar and company configuration from Google Sheets Analyze Deadlines - Calculates days remaining, filters by jurisdiction/entity type, categorizes by priority AI Analysis - GPT-4 provides strategic insights and risk assessment on upcoming deadlines Smart Routing - Only sends alerts if overdue or critical deadlines exist Critical Alerts - HTML email to executives + Slack alert for urgent items Team Updates - Slack summary to finance channel with all upcoming deadlines Logging - Records compliance check results to Google Sheets for audit trail Requirements Google Sheets Structure Sheet 1: TaxCalendar DeadlineID | DeadlineName | DeadlineDate | Jurisdiction | Category | AssignedTo | IsActive FED-Q1 | Form 1120 Q1 | 2025-04-15 | Federal | Income | John Doe | TRUE Sheet 2: CompanyConfig (single row) Jurisdictions | EntityType | FiscalYearEnd Federal, California | Corporation | 12-31 Sheet 3: ComplianceLog (auto-populated) Date | AlertLevel | TotalUpcoming | CriticalCount | OverdueCount 2025-01-15 | HIGH | 12 | 3 | 1 Credentials Needed Google Sheets - Service Account OAuth2 OpenAI - API Key (GPT-4 access required) SMTP - Email account for sending alerts Slack - Bot Token with chat:write permission Setup Steps Import workflow JSON into n8n Add all 4 credentials Replace these placeholders: YOURTAXCALENDAR_ID - Tax calendar sheet ID YOURCONFIGID - Company config sheet ID YOURLOGID - Compliance log sheet ID C12345678 - Slack channel ID tax@company.com - Sender email cfo@company.com - Recipient email Share all sheets with Google service account email Invite Slack bot to channels Test workflow manually Activate the trigger Customizing This Workflow Change Alert Thresholds: Edit "Analyze Deadlines" node: Critical: Change <= 3 to <= 5 for 5-day warning High: Change <= 7 to <= 14 for 2-week notice Medium: Change <= 30 to <= 60 for 2-month lookout Adjust Schedule: Edit "Daily Tax Check" trigger: Change hour/minute for different run time Add multiple trigger times for tax season (8 AM, 2 PM, 6 PM) Add More Recipients: Edit "Send Email" node: To: cfo@company.com, director@company.com CC: accounting@company.com BCC: archive@company.com Customize Email Design: Edit "Format Email" node to change colors, add logo, or modify layout Add SMS Alerts: Insert Twilio node after "Is Critical" for emergency notifications Integrate Task Management: Add HTTP Request node to create tasks in Asana/Jira for critical deadlines Troubleshooting | Issue | Solution | |-------|----------| | No deadlines found | Check date format (YYYY-MM-DD) and IsActive = TRUE | | AI analysis failed | Verify OpenAI API key and account credits | | Email not sending | Test SMTP credentials and check if critical condition met | | Slack not posting | Invite bot to channel and verify channel ID format | | Permission denied | Share Google Sheets with service account email | 📞 Professional Services Need help with implementation or customization? Our team offers: 🎯 Custom workflow development 🏢 Enterprise deployment support 🎓 Team training sessions 🔧 Ongoing maintenance 📊 Custom reporting & dashboards 🔗 Additional API integrations Discover more workflows – Get in touch with us

Oneclick AI SquadBy Oneclick AI Squad
93