HumationHuman + Automation
Back to Catalog

Website content scraper & SEO keyword extractor with GPT-5-mini and Airtable

Abhishek PatoliyaAbhishek Patoliya
22016 views
2/3/2026
HTTP TriggerDebuggingWebhookSalesforceTesting
Official Page

This workflow allows you to scrape website content, clean the HTML, extract structured information using GPT-5-mini, and store the results along with SEO keywords into Airtable. Ideal for building keyword lists and organizing web content for SEO research.

Setup Instructions

1. Prerequisites

  • n8n Community or Cloud instance
  • Airtable account with a base and table ready
  • OpenAI API Key with access to GPT-5-mini

2. Airtable Structure

Ensure your Airtable table has the following fields:

| Field Name | Type | Notes | | ------------ | ------- | ------------------------------- | | Website Name | String | Name or URL of the website | | Data | String | Cleaned website text | | Keyword | String | Extracted SEO keyword list | | Status | Options | Values: Todo, In progress, Done |

3. Node Setup

✅ Form Trigger: Collects website URL from the user.

✅ HTTP Request: Fetches the website content.

✅ HTML Cleaner (Code Node): Strips out styles, tags, and whitespace to get clean text.

✅ Topic Extractor (AI Agent + GPT-5-mini): Extracts topic-wise information from the cleaned website content.

✅ Text Cleaner (Code Node): Removes unwanted symbols like ### and **.

✅ Keyword Extractor (AI Agent + GPT-5-mini): Generates a list of 90 important SEO keywords.

✅ Airtable Upsert: Stores the cleaned data, keywords, and status in Airtable.

4. Key Features

✅ Automatic website content scraping ✅ Clean HTML and extract plain text ✅ Use GPT-5-mini for topic-wise information extraction ✅ Generate 90-keyword SEO lists ✅ Store and manage data in Airtable

5. Use Cases

  • SEO Keyword Research
  • Competitor Website Content Analysis
  • Structured Website Data Collection

Additional Workflow Recommendations

✅ Rename Nodes for Clarity

| Current Name | Suggested Name | | ------------ | ------------------------------- | | Website Name | Website URL Input Form | | HTTP Request | Fetch Website Content | | Code | HTML to Plain Text Cleaner | | Split Out1 | Clean Text Splitter | | AI Agent1 | Topic Extractor (GPT-5-mini) | | Code1 | Text Cleanup Formatter | | Split Out2 | Final Text Splitter | | AI Agent | Keyword Extractor (GPT-5-mini) | | Airtable | Airtable Data Upsert | | Wait1 | Delay Before Merge | | Merge | Combine Data for Airtable |

n8n Website Content Scraper & SEO Keyword Extractor with GPT-5 Mini and Airtable

This n8n workflow automates the process of extracting content from a website, analyzing it with an AI agent (presumably GPT-5 Mini, though the specific model is not explicitly defined in the JSON), and storing the results in Airtable. It's triggered by a form submission, making it easy to initiate content analysis on demand.

What it does

  1. Triggers on Form Submission: The workflow starts when an n8n form is submitted. This form is expected to contain the URL of the website to be scraped.
  2. Scrapes Website Content: It makes an HTTP request to the provided URL to fetch the website's HTML content.
  3. Extracts Relevant Text: A Code node processes the HTML response to extract the main content, likely cleaning it up for AI analysis.
  4. Analyzes Content with AI Agent: The extracted text is then fed into an AI Agent (configured with an OpenAI Chat Model), which is tasked with performing analysis. Based on the directory name, this step is expected to extract SEO keywords and potentially summarize content.
  5. Splits AI Agent Output: The output from the AI Agent is split into individual items, preparing them for structured storage.
  6. Stores Results in Airtable: The processed data, including the original URL and the AI-generated insights, is then saved as a new record in a specified Airtable base.
  7. Includes a Wait Step: A Wait node is included, which might be used to introduce a delay between operations, potentially to respect API rate limits or allow for asynchronous processing.
  8. Merges Data: A Merge node is present, indicating that data from different branches or steps might be combined at a certain point in the workflow.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance to host and execute the workflow.
  • Airtable Account: An Airtable account with a base and table configured to store the scraped content and SEO keywords. You'll need an Airtable API key and the Base ID/Table Name.
  • OpenAI API Key: An OpenAI API key for the AI Chat Model used by the AI Agent. The workflow uses an "OpenAI Chat Model" which implies interaction with OpenAI's language models.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Airtable: Set up your Airtable credential with your API Key. In the Airtable node, select your credential and configure the Base ID and Table Name where the data will be stored.
    • OpenAI: Set up your OpenAI credential with your API Key. Ensure the "OpenAI Chat Model" node uses this credential.
  3. Configure the n8n Form Trigger:
    • The "On form submission" node will generate a unique URL. Share this URL or embed the form on your website to trigger the workflow.
    • Ensure the form collects the website URL as an input field, which will be passed to the HTTP Request node.
  4. Customize the Code Node: Review the "Code" node (ID 834) to understand how it extracts content from the HTTP response. You might need to adjust the JavaScript code based on the specific HTML structure of the websites you intend to scrape.
  5. Customize the AI Agent:
    • The "AI Agent" node (ID 1119) uses an "OpenAI Chat Model" (ID 1153).
    • Configure the prompt for the AI Agent to specify what kind of analysis you want it to perform (e.g., "Extract 5 main SEO keywords," "Summarize the content," "Identify the target audience").
  6. Activate the Workflow: Once configured, activate the workflow to make it ready for use.

Now, whenever the n8n form is submitted with a website URL, the workflow will automatically scrape the content, analyze it using the AI agent, and save the results to your Airtable base.

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