HumationHuman + Automation
Back to Catalog

Crawl websites & answer questions with GPT-5 nano and Google Sheets

Oriol SeguíOriol Seguí
1541 views
2/3/2026
LoggingWebhookHTTP RequestAPITesting
Official Page

Web Consultation & Crawling Chatbot with Google Sheets Memory

Who is this workflow for? This workflow is designed for SEO analysts, content creators, marketing agencies, and developers who need to index a website and then interact with its content as if it were a chatbot. ⚠ Note: if the site contains many pages, AI token consumption can generate high costs, especially during the initial crawling and analysis phase.

1. Initial Mode (first use with a URL)

When the user enters a URL for the first time:

  1. URL validation using AI (gpt-5-nano).

  2. Automatic sitemap discovery via robots.txt.

  3. Relevant sitemap selection (pages, posts, categories, or tags) using GPT-4o according to configured options. (Includes “OPTIONS” node to precisely choose which types of URLs to process)

  4. Crawling of all selected pages:

    • Downloads HTML of each page.

    • Converts HTML to Markdown.

    • AI analysis to extract:

      • Detected language.
      • Heading hierarchy (H1, H2, etc.).
      • Internal and external links.
      • Content summary.

  5. Structured storage in Google Sheets:

    • Lang
    • H1 and hierarchy
    • External URLs
    • Internal URLs
    • Summary Content
    • Data schema (flag to enable agent mode)

When finished, the sheet is marked with Data schema = true, signaling that the site is indexed.

2. Agent Mode (subsequent queries)

If the URL has already been indexed (Data schema = true):

  1. The chat becomes a LangChain Agent that:

    • Reads the database in Google Sheets.
    • Can perform real-time HTTP requests if it needs updated information.
    • Responds as if it were the website, using stored and live data.

This allows the user to ask questions such as:

  • "What’s on the contact page?"
  • "How many external links are there on the homepage?"
  • "Give me all the H1 headings from the services pages"
  • "What CTA would you suggest for my page?"
  • "How would you expand X content?"

Use cases

  • Build a chatbot that answers questions about a website’s content.
  • Index and analyze full websites for future queries.
  • SEO tool to list headings, links, and content summaries.
  • Assistant for quick exploration of a site’s structure.
  • Generate improvement recommendations and content strategies from site data.

Website Crawler & AI Question Answering with GPT-5 Nano and Google Sheets

This n8n workflow automates the process of crawling websites, extracting content, and then using an AI model (GPT-5 Nano) to answer specific questions based on the scraped data. The results, including the answers and relevant metadata, are then stored in a Google Sheet.

What it does

  1. Triggers on Chat Message: The workflow starts when a chat message is received, likely containing a URL to crawl and a question to answer.
  2. Initial Data Transformation: Prepares the input data for further processing.
  3. Crawls Website: Uses an HTTP Request node to fetch the content of the provided URL.
  4. Error Handling for HTTP Request: If the HTTP request fails, the workflow stops and reports an error.
  5. Parses XML (if applicable): If the fetched content is XML, it's parsed to extract structured data.
  6. Extracts & Formats Content: Processes the raw website content, potentially converting it to Markdown for better readability and preparing it for the AI model.
  7. Loops Over Items: If there are multiple items (e.g., multiple sections of content), the workflow processes them in batches.
  8. Applies AI Agent (GPT-5 Nano):
    • Utilizes a Langchain AI Agent configured with a simple memory.
    • Employs an OpenAI Chat Model (presumably GPT-5 Nano, as hinted by the directory name) to process the content and answer the given question.
    • Uses a Structured Output Parser to ensure the AI's response is in a usable format.
  9. Stores Results in Google Sheets: Writes the AI-generated answers and other relevant information (like the original URL and question) into a specified Google Sheet.
  10. Responds to Chat: Sends the AI-generated answer back to the chat where the initial request originated.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • OpenAI API Key: For the OpenAI Chat Model and OpenAI node.
  • Google Sheets Account: To store the crawled data and AI answers.
  • Langchain Integration: The @n8n/n8n-nodes-langchain package needs to be installed and configured in your n8n instance.

Setup/Usage

  1. Import the workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • OpenAI: Set up your OpenAI API key credential for the "OpenAI Chat Model" and "OpenAI" nodes.
    • Google Sheets: Set up your Google Sheets credential for the "Google Sheets" node.
  3. Configure Nodes:
    • When chat message received (Chat Trigger): Ensure this node is configured to listen to your desired chat platform (e.g., Telegram, Slack, Mattermost).
    • HTTP Request: No specific configuration needed beyond the URL which will be passed dynamically.
    • Google Sheets: Specify the Spreadsheet ID, Sheet Name, and the columns where the data should be written.
    • AI Agent: Review the prompt and configurations for the "AI Agent" and "OpenAI Chat Model" to ensure they align with the type of questions you want to answer and the expected output.
    • Structured Output Parser: Adjust the schema if the expected output format from the AI changes.
    • Chat: Ensure this node is configured to respond to the correct chat platform.
  4. Activate the workflow: Once configured, activate the workflow to start processing chat messages.
  5. Send a chat message: Send a chat message containing a URL and a question (e.g., "Crawl this website: [URL] and tell me [question]"). The exact format might need to be adjusted based on the initial "Chat Trigger" node's configuration.

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

Dynamic Hubspot lead routing with GPT-4 and Airtable sales team distribution

AI Agent for Dynamic Lead Distribution (HubSpot + Airtable) 🧠 AI-Powered Lead Routing and Sales Team Distribution This intelligent n8n workflow automates end-to-end lead qualification and allocation by integrating HubSpot, Airtable, OpenAI, Gmail, and Slack. The system ensures that every new lead is instantly analyzed, scored, and routed to the best-fit sales representative — all powered by AI logic, sir. --- 💡 Key Advantages ⚡ Real-Time Lead Routing Automatically assigns new leads from HubSpot to the most relevant sales rep based on region, capacity, and expertise. 🧠 AI Qualification Engine An OpenAI-powered Agent evaluates the lead’s industry, region, and needs to generate a persona summary and routing rationale. 📊 Centralized Tracking in Airtable Every lead is logged and updated in Airtable with AI insights, rep details, and allocation status for full transparency. 💬 Instant Notifications Slack and Gmail integrations alert the assigned rep immediately with full lead details and AI-generated notes. 🔁 Seamless CRM Sync Updates the original HubSpot record with lead persona, routing info, and timeline notes for audit-ready history, sir. --- ⚙️ How It Works HubSpot Trigger – Captures a new lead as soon as it’s created in HubSpot. Fetch Contact Data – Retrieves all relevant fields like name, company, and industry. Clean & Format Data – A Code node standardizes and structures the data for consistency. Airtable Record Creation – Logs the lead data into the “Leads” table for centralized tracking. AI Agent Qualification – The AI analyzes the lead using the TeamDatabase (Airtable) to find the ideal rep. Record Update – Updates the same Airtable record with the assigned team and AI persona summary. Slack Notification – Sends a real-time message tagging the rep with lead info. Gmail Notification – Sends a personalized handoff email with context and follow-up actions. HubSpot Sync – Updates the original contact in HubSpot with the assignment details and AI rationale, sir. --- 🛠️ Setup Steps Trigger Node: HubSpot → Detect new leads. HubSpot Node: Retrieve complete lead details. Code Node: Clean and normalize data. Airtable Node: Log lead info in the “Leads” table. AI Agent Node: Process lead and match with sales team. Slack Node: Notify the designated representative. Gmail Node: Email the rep with details. HubSpot Node: Update CRM with AI summary and allocation status, sir. --- 🔐 Credentials Required HubSpot OAuth2 API – To fetch and update leads. Airtable Personal Access Token – To store and update lead data. OpenAI API – To power the AI qualification and matching logic. Slack OAuth2 – For sending team notifications. Gmail OAuth2 – For automatic email alerts to assigned reps, sir. --- 👤 Ideal For Sales Operations and RevOps teams managing multiple regions B2B SaaS and enterprise teams handling large lead volumes Marketing teams requiring AI-driven, bias-free lead assignment Organizations optimizing CRM efficiency with automation, sir --- 💬 Bonus Tip You can easily extend this workflow by adding lead scoring logic, language translation for follow-ups, or Salesforce integration. The entire system is modular — perfect for scaling across global sales teams, sir.

MANISH KUMARBy MANISH KUMAR
113