HumationHuman + Automation
Back to Catalog

Auto-generate SEO meta descriptions & keywords for Magento 2 with GPT-4.1 & LangChain

Kanaka Kishore KandregulaKanaka Kishore Kandregula
72 views
2/3/2026
Daily TriggerGoogle SheetsBirthdayGoogle ChatAutomation
Official Page

This workflow intelligently regenerates meta descriptions and meta keywords for Magento 2 product pages using OpenAI and SEO best practices.

🔍 What It Does:

  • Accepts SKU input via a public form
  • Fetches the product by SKU from your Magento 2 store
  • Extracts existing description, meta description, and keywords
  • Uses a LangChain-powered AI Agent with OpenAI to:
  • Analyze the current product content
  • Generate a high-conversion meta description (150–160 characters)
  • Generate 5–7 optimized SEO meta keywords (while retaining existing ones, avoiding duplicates)
  • Updates the product's metadata in Magento via REST API

⚙️ Technical Highlights:

  • Magento 2 REST integration
  • FormTrigger node for user input
  • Add Role so AI know the Tone of you
  • JavaScript code node for safe HTML parsing
  • LangChain AI Agent with OpenAI (GPT-4.1 mini)
  • Structured output parser to format AI response
  • Automatically pushes updated metadata back into Magento

🧪 Optional:

SerpAPI (plug-and-play support included but disabled) can be enabled to bring real-time search trend data into the AI prompt.

✅ Ideal For:

Magento 2 store owners, developers, and SEO teams who want to automate metadata updates and boost search performance without touching product pages manually.

How This AI Automation Workflow Helps Magento 2 Store Owners Stay Ahead

  1. Automates SEO Meta Updates at Scale
  2. Manually updating meta descriptions and keywords across hundreds or thousands of products is time-consuming and error-prone. This AI-driven workflow automatically reads the current product descriptions, analyzes SEO opportunities, and generates optimized meta keywords and descriptions — all without manual copywriting. This saves significant time and labor while keeping your SEO metadata fresh.
  3. Uses AI to Align with Latest Search Trends
  4. The workflow integrates with live search trend data (via SerpAPI or other tools) so that generated meta keywords and descriptions incorporate current popular search queries, trending phrases, and relevant semantic keywords. This ensures your product pages rank better by tapping into what buyers are actively searching for right now.
  5. Improves Search Engine Rankings and Click-Through Rates (CTR)
  6. Well-optimized meta descriptions that include power words, clear calls to action, and keyword clustering help improve Google’s understanding of your pages and entice more clicks from search results. This drives more organic traffic and increases the chance visitors convert into customers.
  7. Maintains Brand Authority and Trustworthiness
  8. The AI prompt is designed to follow Google’s E-A-T guidelines (Expertise, Authoritativeness, Trustworthiness), ensuring your product metadata builds credibility. Consistent, accurate meta descriptions contribute to a professional brand image and help improve SEO reputation.
  9. Keeps Magento Store Metadata Consistent and Up-to-Date
  10. Product content changes frequently—new features, specifications, or uses arise. This workflow allows easy regeneration of SEO metadata after product updates or on-demand, so your Magento store’s search snippets never become outdated or irrelevant.
  11. Simple Integration with Magento 2 API and Your Existing Workflow
  12. Since the automation fetches and updates product meta fields via Magento’s REST API, it works seamlessly with your current Magento setup without heavy manual work or additional plugins. This smooth integration minimizes technical complexity.

Why This Matters in the Current Market

  1. SEO remains a top driver of online sales — with evolving algorithms and user search behaviors, staying current and relevant in metadata is essential for visibility.
  2. Voice search, mobile search, and semantic search make keyword strategy more complex; AI-powered semantic keyword clustering simplifies this.
  3. E-commerce competition is fierce — automated, data-driven SEO optimizations give you an edge over stores relying on static, outdated meta descriptions.
  4. Content automation is becoming a necessity — businesses using AI for SEO benefit from faster iteration and more consistent messaging, helping them capture shifting consumer trends.

Summary

This AI + Automation + Workflow approach enables Magento 2 store owners to continuously and efficiently optimize their product metadata, leveraging live market data and SEO best practices to boost organic rankings, attract more visitors, and increase conversions — all while reducing manual workload.

n8n Workflow: Auto-Generate SEO Meta Descriptions & Keywords for Magento 2 with GPT-4 and Langchain

This n8n workflow automates the generation of SEO-optimized meta descriptions and keywords for Magento 2 product data using advanced AI capabilities from OpenAI (GPT-4) and Langchain. It's designed to streamline the SEO process for e-commerce stores, ensuring product pages are well-optimized for search engines.

Description

This workflow simplifies the complex task of creating compelling and keyword-rich meta descriptions and keywords for Magento 2 products. By leveraging a custom n8n form for input and integrating with OpenAI's GPT-4 via Langchain, it provides an efficient way to generate high-quality SEO content, which can then be used to update your Magento 2 store.

What it does

  1. Triggers on Form Submission: The workflow starts when a user submits data through a custom n8n form.
  2. Prepares Product Data: A "Code" node processes the incoming form data, likely structuring it for the AI agent. This step might involve extracting product names, descriptions, and other relevant details.
  3. Utilizes an AI Agent for SEO Generation: An "AI Agent" (Langchain) is employed to intelligently generate SEO content.
    • Leverages OpenAI Chat Model: The agent uses an "OpenAI Chat Model" (likely GPT-4) as its language model to understand the product context and generate human-quality text.
    • Incorporates Web Search (SerpAPI): The agent is equipped with a "SerpAPI (Google Search)" tool, allowing it to perform real-time web searches. This is crucial for gathering current SEO trends, competitor analysis, and relevant keywords to ensure the generated content is highly effective.
    • Structures Output: A "Structured Output Parser" ensures that the AI's response is formatted into a usable structure (e.g., JSON) containing the generated meta description and keywords.
  4. Conditional Processing (Placeholder): An "If" node is present, suggesting potential conditional logic for further processing based on the AI's output or other criteria. (Note: Without specific conditions defined in the JSON, its exact function is not fully detailed here but implies branching logic).
  5. Performs HTTP Request (Placeholder): An "HTTP Request" node is included, which would typically be used to send the generated SEO data to an external system, such as updating a Magento 2 API endpoint. (Note: The specific configuration for this request is not available in the provided JSON, but this is its likely purpose).

Prerequisites/Requirements

  • n8n Instance: A running n8n instance to host the workflow.
  • OpenAI API Key: An API key for OpenAI to access their language models (e.g., GPT-4). This will be configured within the "OpenAI Chat Model" node's credentials.
  • SerpAPI API Key: An API key for SerpAPI to enable web search capabilities for the AI agent. This will be configured within the "SerpAPI (Google Search)" node's credentials.
  • Magento 2 Access (API): Although not explicitly configured in the provided JSON, to fully utilize this workflow for updating Magento 2, you would need API access to your Magento 2 instance.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Locate the "OpenAI Chat Model" node and configure your OpenAI API key.
    • Locate the "SerpAPI (Google Search)" node and configure your SerpAPI API key.
  3. Customize the n8n Form Trigger: Access the "n8n Form Trigger" node and customize the form fields to collect the necessary product information (e.g., product name, existing description, key features) that you want the AI to use for generating SEO content.
  4. Review and Customize the "Code" Node: Inspect the "Code" node to understand how it processes the form input. Adjust the JavaScript code if your input structure or desired output for the AI agent differs.
  5. Refine the AI Agent Prompt (within AI Agent node): The "AI Agent" node will contain the core prompt that guides GPT-4 on how to generate meta descriptions and keywords. Refine this prompt to match your specific SEO requirements, tone, and target audience.
  6. Configure the HTTP Request Node:
    • If you intend to update Magento 2, configure the "HTTP Request" node with the appropriate Magento 2 API endpoint, authentication details, and payload structure to send the generated meta descriptions and keywords.
    • Map the output from the "Structured Output Parser" to the body of your HTTP request.
  7. Activate the Workflow: Once configured, activate the workflow. You can then test it by submitting data through the n8n form.

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.

Ranjan DailataBy Ranjan Dailata
161

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 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.

Le NguyenBy Le Nguyen
942