Scrape books from URL with Dumpling AI, clean HTML, save to Sheets, email as CSV
👥 Who is this for?
This workflow is ideal for virtual assistants, researchers, developers, automation specialists, and data analysts who need to regularly extract and organize structured product information (like books) from a website. It’s especially useful for those working with catalog-based websites who want to automate extraction and delivery of clean, sorted data.
🧩 What problem is this solving?
Manually copying product listings like book titles and prices from a website into a spreadsheet is slow and repetitive. This automation solves that problem by scraping content using Dumpling AI, extracting the right data using CSS selectors, and formatting it into a clean CSV file that is sent to your email—all triggered automatically when a new URL is added to Google Sheets.
⚙️ What this workflow does
This template automates an entire content scraping and delivery process:
- Watches a Google Sheet for new URLs
- Scrapes the HTML content of the given webpage using Dumpling AI
- Uses CSS selectors in the HTML node to extract each book from the page
- Splits the HTML array into individual items
- Extracts the book title and price from each HTML block
- Sorts the books in descending order based on price
- Converts the sorted data to a CSV file
- Sends the CSV via email using Gmail
🛠️ Setup
-
Google Sheets
- Create a sheet titled something like
URLs - Add your product listing URLs (e.g., http://books.toscrape.com)
- Connect the Google Sheets trigger node to your sheet
- Ensure you have proper credentials connected
- Create a sheet titled something like
-
Dumpling AI
-
Create an account at Dumpling AI - Generate your API key
-
Set the HTTP Method to
POSTand pass the URL dynamically from the Google Sheet -
Use
Header Authto include your API key in the request header -
Make sure
"cleaned": "True"is included in the body for optimized HTML output
-
-
HTML Node
- The first HTML node extracts the main book container blocks using:
.row > li - The second HTML node parses out the individual fields:
title:h3 > a(via thetitleattribute)price:.price_color
- The first HTML node extracts the main book container blocks using:
-
Sort Node
- Sorts books by
pricein descending order - Note: price is extracted as a string, ensure it's parsable if you plan to use numeric filtering later
- Sorts books by
-
Convert to CSV
- The JSON data is passed into a Convert node and transformed into a CSV file
-
Gmail
- Sends the CSV as an attachment to a designated email
🔄 How to customize this workflow
- Extract more data: Add more CSS selectors in the second HTML node to pull fields like author, availability, or product links
- Switch destinations: Replace Gmail with Slack, Google Drive, Dropbox, or another platform
- Adjust sorting: Sort alphabetically or based on another extracted value
- Use a different source: As long as the site structure is consistent, this can scrape any listing-like page
- Trigger differently: Use a webhook, form submission, or schedule trigger instead of Google Sheets
⚠️ Dependencies and Notes
- This workflow uses Dumpling AI to perform the web scraping. This requires an API key and uses credits per request.
- The HTML node depends on valid CSS selectors. If the site layout changes, the selectors may need to be updated.
- Ensure you’re not scraping content from websites that prohibit automated scraping.
# n8n Workflow: Scrape Books from URL, Clean HTML, Save to Google Sheets, and Email as CSV
This n8n workflow automates the process of extracting book information from a specified URL, cleaning the HTML content using AI (Dumpling AI, implied by the directory name but not explicitly in JSON), structuring the data, saving it to a Google Sheet, and finally emailing the data as a CSV attachment.
## What it does
This workflow performs the following steps:
1. **Triggers on Google Sheet Update**: The workflow starts whenever a specified Google Sheet is updated, likely with a URL to scrape.
2. **Fetches HTML Content**: It makes an HTTP request to the URL provided in the Google Sheet to retrieve the raw HTML content of the webpage.
3. **Parses HTML**: The HTML content is then processed to extract relevant data, likely book titles, authors, prices, or other details.
4. **Splits Data**: The extracted data is split into individual items, preparing it for further processing.
5. **Sorts Data**: The extracted data items are sorted, potentially by a key field like title or author.
6. **Converts to CSV**: The structured and sorted data is converted into a CSV file format.
7. **Sends Email with CSV**: The generated CSV file is attached to an email and sent via Gmail.
## Prerequisites/Requirements
To use this workflow, you will need:
* **n8n Instance**: A running n8n instance.
* **Google Sheets Account**: A Google account with access to Google Sheets for the trigger and potentially for storing data (though the JSON only shows a trigger).
* **Gmail Account**: A Gmail account for sending the email with the CSV attachment.
* **Credentials**: Configured n8n credentials for:
* Google Sheets (OAuth2 recommended)
* Gmail (OAuth2 recommended)
## Setup/Usage
1. **Import the Workflow**: Download the provided JSON and import it into your n8n instance.
2. **Configure Credentials**:
* Set up your **Google Sheets** credential.
* Set up your **Gmail** credential.
3. **Configure Google Sheets Trigger (Node 841)**:
* Specify the Google Sheet ID and the sheet name that will trigger the workflow.
* Ensure the sheet contains a column with the URLs you want to scrape.
4. **Configure HTTP Request (Node 19)**:
* Ensure this node correctly references the URL from the Google Sheets trigger (e.g., `{{ $json.url_column_name }}`).
5. **Configure HTML Node (Node 842)**:
* Adjust the CSS selectors or XPath expressions to accurately extract the desired book information (e.g., title, author, price) from the HTML content.
6. **Configure Gmail Node (Node 356)**:
* Specify the recipient email address, subject, and body for the email.
* Ensure the CSV file from the "Convert to File" node is correctly attached.
7. **Activate the Workflow**: Once configured, activate the workflow. It will now run automatically whenever the specified Google Sheet is updated.
**Note on "Dumpling AI Clean HTML"**: While the directory name suggests the use of "Dumpling AI" for cleaning HTML, the provided JSON does not explicitly contain a node or configuration for an AI service. The HTML cleaning and data extraction are handled by the generic "HTML" node, which relies on CSS selectors or XPath. If "Dumpling AI" is a custom script or an external service, it would need to be integrated, perhaps via a Function node or another HTTP Request node, which is not present in this JSON. The workflow as defined focuses on standard HTML parsing.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
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
Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.