HumationHuman + Automation
Back to Catalog

Create high-converting sales copy with Hormozi Framework, LangChain & Google Docs

HunyaoHunyao
563 views
2/3/2026
GhostWebhookAutomationPublishingCMS
Official Page

Note: This workflow assumes you already have your product’s Amazon reviews saved in a Google Sheet. If you still need those reviews, run my Amazon Reviews Scraper workflow first, then plug the resulting spreadsheet into this template.

What it does Transforms any draft Google Doc into multiple high-converting sales pages. It blends Alex Hormozi’s value-stacking tactics with persona targeting based on Maslow’s Hierarchy of Needs, using your own customer reviews for proof and voice of customer (VOC).

Perfect for • Growth and creative strategists • Freelance copywriters and agencies • Founders sharpening offers and funnels

Apps used Google Sheets, Google Docs, LangChain OpenRouter LLM

How it works

  1. Form Trigger collects Drive folder IDs, base copy URL and options.
  2. Workflow fetches the draft copy and product feature doc.
  3. It samples reviews, extracts VOC insights and maps them to Maslow needs.
  4. LLM drafts headlines and hooks following Hormozi’s $100M Offers principles.
  5. Personas drive tone, objections and urgency in each copy variant.
  6. Loop writes one Google Doc per variant in your chosen folder.
  7. Customer analysis docs are saved to a second folder for reuse.

Setup

  1. Share two Drive folders, copy the IDs (text after folders/).
  2. Paste each ID into Customer Analysis Folder ID and Advertorial Copy Folder ID.
  3. Provide File Name, Base copy (Google Docs URL) and Product Feature/USPs Doc.
  4. Optional: Reviews Sheet URL, Number of reviews to use, Target City.
  5. Set Number of Copies you need (1–20).
  6. Add Google Docs OAuth2 and Google Sheets OAuth2 credentials in n8n.

If you have any questions in running the workflow, feel free to reach out to me at my youtube channel: https://www.youtube.com/@lifeofhunyao

Create High-Converting Sales Copy with Hormozi Framework using LangChain and Google Docs

This n8n workflow automates the generation of high-converting sales copy based on the Hormozi framework, leveraging AI agents (LangChain) and Google Docs. It allows you to input product/service details and desired output format via a form, then generates and saves the sales copy to a Google Doc.

What it does

  1. Triggers on Form Submission: The workflow starts when a user submits data through an n8n form.
  2. Prepares Input Data: It extracts and structures the product/service details, target audience, and desired output format from the form submission.
  3. Generates Sales Copy with AI Agent: An AI Agent (LangChain) is used to generate sales copy following the Hormozi framework, utilizing a "Think" tool for structured thought processes and an OpenRouter Chat Model for language generation.
  4. Parses AI Output: The AI-generated output, which is expected to be in a structured format (e.g., JSON), is parsed to extract the final sales copy.
  5. Creates Google Doc: A new Google Doc is created with the generated sales copy.
  6. Updates Google Sheet (Optional/Placeholder): A Google Sheets node is present, which could be used to log requests or generated content, although its specific configuration is not detailed in the provided JSON.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Google Account: For Google Docs integration. Ensure your Google account has the necessary permissions to create documents.
  • OpenRouter API Key: For the OpenRouter Chat Model to access various large language models.
  • LangChain Credentials: If specific LangChain credentials are required beyond the OpenRouter API key, ensure they are configured.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON code.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button and paste the workflow JSON.
  2. Configure Credentials:
    • Google Docs: Set up your Google OAuth2 credentials for Google Docs.
    • OpenRouter Chat Model: Configure your OpenRouter API key credential.
  3. Configure the n8n Form Trigger:
    • Open the "On form submission" node.
    • Define the form fields that will collect information like product name, description, target audience, pain points, desired outcome, and output format.
    • Activate the workflow.
  4. Test the Workflow:
    • Access the public URL of the "On form submission" node (available after activating the workflow).
    • Fill out the form with your product/service details and submit it.
    • Observe the execution in n8n to ensure the sales copy is generated and saved to Google Docs correctly.
  5. Customize (Optional):
    • AI Agent Prompt: Adjust the prompts within the "AI Agent" node to fine-tune the sales copy generation based on the Hormozi framework or other specific requirements.
    • Structured Output Parser: Modify the parser if the AI output format changes.
    • Google Sheets: Configure the "Google Sheets" node to log relevant data if needed.
    • Google Docs Content: Adjust how the content is inserted into Google Docs if you need specific formatting or templates.

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