HumationHuman + Automation
Back to Catalog

Generate AI-powered markdown posts from workflow JSON with Gemini & LlamaIndex

Khairul MuhtadinKhairul Muhtadin
195 views
2/3/2026
Google DriveSpreadsheetData TransformationExcelFile Upload
Official Page

This AI-powered workflow transforms n8n workflow JSON files into publication-ready, SEO-optimized markdown posts for the n8n community. Simply upload your workflow's JSON, and let Google Gemini 2.5 Pro, guided by a LlamaIndex-powered knowledge base of best practices, automatically generate compelling content.

Why Use This Workflow?

Time Savings: Reduces the time to create a detailed workflow post from over an hour of manual writing to under 2 minutes.

Cost Reduction: Eliminates the need for separate AI content subscriptions or outsourcing content creation tasks.

Error Prevention: Enforces content quality and structural consistency by using a knowledge base of n8n's official guidelines, minimizing formatting errors.

Ideal For

  • n8n Workflow Creators: To quickly document and share their creations on the community platform without the tedious, time-consuming writing process.
  • Developer Advocates: To standardize and accelerate the production of technical tutorials and workflow showcases.
  • Content & Marketing Teams: To streamline the content pipeline for n8n-related blog posts, tutorials, and community engagement initiatives.

How It Works

  1. Trigger: The process starts when you upload an n8n workflow JSON file via a simple web form.
  2. Data Extraction: The workflow automatically extracts the JSON content from the uploaded file.
  3. Intelligence Layer: An advanced AI agent, powered by Google Gemini 2.5 Pro, analyzes the structure, nodes, and metadata of your workflow.
  4. Knowledge Retrieval: The agent consults a specialized, in-memory knowledge base built from n8n's content guidelines. This knowledge base is created by parsing documents with LlamaIndex and refined with a Cohere Reranker for maximum accuracy.
  5. Content Generation: The AI agent synthesizes the technical details from your JSON with the best practices from the knowledge base to write a complete, benefit-driven markdown post.
  6. Output & Delivery: The final, polished markdown content is generated as the workflow's output, ready to be copied and pasted into the n8n community platform.

Setup Guide

Prerequisites

| Requirement | Type | Purpose | |-------------|------|---------| | n8n instance | Essential | Workflow execution platform | | Google Gemini API Key | Essential | Powers the core AI content generation | | LlamaIndex Cloud API Key | Essential | Parses documents for the knowledge base | | Cohere API Key | Optional | Improves knowledge base search results | | Google Drive Account | Optional | For automatically updating the knowledge base from a Google Doc |

Installation Steps

  1. Import the JSON file to your n8n instance.
  2. Configure credentials:
    • Google Gemini: In the "GEmini 2.5 pro" node, create and add your Google Gemini API credential.
    • LlamaIndex: In the three HTTP Request nodes named "Parse Document...", "Monitor Document...", and "Retrieve Parsed...", create an HTTP Header Auth credential. The header name is Authorization and the value is Bearer YOUR_LLAMA_INDEX_API_KEY.
    • Cohere: (Optional) In the "Reranker Cohere" node, create and add your Cohere API credential.
    • Google Drive: (Optional) If you plan to auto-update the knowledge base, configure Google Drive OAuth2 credentials for the "Knowledge Base Updated Trigger" and "Download Knowledge Document" nodes.
  3. Update environment-specific values:
    • To use the knowledge base auto-update feature, go to the "Knowledge Base Updated Trigger" node and select the Google Drive file containing your content guidelines.
  4. Customize settings:
    • The primary system prompt in the "n8ncreator" agent node can be modified to adjust the tone, style, or structure of the generated content.
  5. Test execution:
    • Run the workflow manually and use the form to upload a sample n8n workflow JSON file to verify that all connections work correctly.

Technical Details

Core Nodes

| Node | Purpose | Key Configuration | |------|---------|-------------------| | Form Trigger | Initiates the workflow via a file upload. | Set the "Input Json Workflow" field to required. | | Langchain Agent | Orchestrates the entire content creation process. | The system prompt contains all instructions for the AI. | | ChatGoogleGemini | Provides the core generative AI capabilities. | Select your Gemini model of choice (e.g., gemini-2.5-pro). | | VectorStoreInMemory | Acts as the agent's knowledge base tool. | Configured to use embeddings from a Google Gemini model. | | HTTPRequest | Interacts with the LlamaIndex API to parse documents. | Set up with LlamaIndex API endpoint and authentication. |

Customization Options

Basic Adjustments:

  • Change AI Model: Replace the ChatGoogleGemini node with another LLM node (e.g., OpenAI, Anthropic) to use a different provider.
  • Adjust System Prompt: Modify the prompt in the "n8ncreator" node to tailor the output for different platforms (e.g., blog, internal wiki) or change the writing style.

Advanced Enhancements:

  • Automated Publishing: Connect the output of the "n8ncreator" node to a Ghost, WordPress, or GitHub node to automatically publish the generated post.
  • Add Web Search: Equip the Langchain Agent with a web search tool to allow it to fetch live information about new n8n nodes or services.
  • Batch Processing: Replace the Form Trigger with a Read Binary Files node to process an entire folder of workflow JSON files in a single run.

Performance & Optimization

| Metric | Expected Performance | Optimization Tips | |--------|---------------------|-------------------| | Execution time | ~1 minute per run | Largely dependent on the Gemini API response time. | | API calls | 1 LLM call per post | Knowledge base updates trigger LlamaIndex/Google calls separately. | | Error handling | Built-in retry logic for document parsing | Add an error workflow path after the "n8ncreator" node to handle AI generation failures. |

Troubleshooting

Common Issues:

| Problem | Cause | Solution | |---------|-------|----------| | AI output is generic or incomplete | The input JSON file is invalid or lacks key information (e.g., no node names). | Ensure you are uploading a valid, exported n8n workflow JSON. Verify the workflow has been saved with descriptive node names. | | LlamaIndex parsing fails | The LlamaIndex API key is incorrect or the source document is inaccessible. | Double-check your LlamaIndex API credential. Ensure the Google Doc sharing settings allow access. | | Credential Error | API keys are missing or incorrect for Gemini, LlamaIndex, or Cohere. | Go to the specified nodes and verify that the correct credentials have been created and selected. |

Created by: khaisa Studio Category: AI Tags: AI, Content Generation, Google Gemini, LlamaIndex, Automation Need custom workflows? Contact us

Connect with the creator: Portfolio • Workflows • LinkedIn • Medium • Threads

Generate AI-Powered Markdown Posts from Workflow JSON with Gemini & LlamaIndex

This n8n workflow automates the creation of comprehensive Markdown blog posts by analyzing n8n workflow JSON definitions. It leverages Google Gemini for AI generation and LlamaIndex for intelligent document processing and retrieval, allowing you to quickly document and share your n8n workflows.

What it does

This workflow takes an n8n workflow's JSON definition as input and performs the following steps:

  1. Triggers on Input: The workflow can be triggered either by a new file being added to a specified Google Drive folder or by a manual form submission.
  2. Extracts Workflow JSON: If triggered by Google Drive, it downloads and extracts the content of the .json file. If triggered by a form, it directly uses the provided JSON.
  3. Loads Data for AI Processing: The extracted JSON content is then loaded into a format suitable for LlamaIndex processing.
  4. Creates a Simple Vector Store: The workflow initializes a simple in-memory vector store, which helps the AI agent efficiently retrieve relevant information from the workflow JSON.
  5. Embeds Data using Google Gemini: The workflow uses Google Gemini's embedding model to convert the workflow JSON data into vector embeddings, enabling semantic search and retrieval.
  6. Reranks Retrieved Information (Optional): It includes a Cohere Reranker node, which can be used to re-order and prioritize the most relevant information retrieved from the vector store, ensuring the AI focuses on the most critical details.
  7. Generates Markdown Post with Google Gemini AI Agent: An AI Agent powered by Google Gemini Chat Model is then used to analyze the workflow JSON and the retrieved information. It generates a detailed Markdown blog post, including a title, description, step-by-step explanation, and prerequisites.
  8. Outputs the Markdown Post: The generated Markdown content is then available for further use, such as publishing to a blog, saving to a file, or sending via email.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • Google Account: For Google Drive Trigger and Google Gemini credentials.
    • Google Drive API Access: If using the Google Drive Trigger.
    • Google Gemini API Key: For the AI Agent and Embeddings.
  • Cohere API Key (Optional): If you intend to use the Cohere Reranker node.

Setup/Usage

  1. Import the Workflow: Download the workflow JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Google Drive: Set up your Google Drive OAuth2 credentials for the Google Drive Trigger and Google Drive nodes.
    • Google Gemini: Configure your Google Gemini API Key credentials for the Embeddings Google Gemini and Google Gemini Chat Model nodes.
    • Cohere (Optional): If you plan to use the Reranker Cohere node, configure your Cohere API Key credentials.
  3. Configure Trigger:
    • Google Drive Trigger (531): Specify the Google Drive folder you want to monitor for new workflow JSON files.
    • On form submission (1225): If you prefer to manually submit JSON, activate this trigger and note its webhook URL. You can then send a POST request with your workflow JSON in the body.
  4. Activate the Workflow: Once configured, activate the workflow.

Now, whenever a new n8n workflow JSON file is added to the specified Google Drive folder (or a form is submitted), the workflow will automatically generate a Markdown post.

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

AI-powered code review with linting, red-marked corrections in Google Sheets & Slack

Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting — all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow — reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n — combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.

higashiyama By higashiyama
90

Automated YouTube video uploads with 12h interval scheduling in JST

This workflow automates a batch upload of multiple videos to YouTube, spacing each upload 12 hours apart in Japan Standard Time (UTC+9) and automatically adding them to a playlist. ⚙️ Workflow Logic Manual Trigger — Starts the workflow manually. List Video Files — Uses a shell command to find all .mp4 files under the specified directory (/opt/downloads/单词卡/A1-A2). Sort and Generate Items — Sorts videos by day number (dayXX) extracted from filenames and assigns a sequential order value. Calculate Publish Schedule (+12h Interval) — Computes the next rounded JST hour plus a configurable buffer (default 30 min). Staggers each video’s scheduled time by order × 12 hours. Converts JST back to UTC for YouTube’s publishAt field. Split in Batches (1 per video) — Iterates over each video item. Read Video File — Loads the corresponding video from disk. Upload to YouTube (Scheduled) — Uploads the video privately with the computed publishAtUtc. Add to Playlist — Adds the newly uploaded video to the target playlist. 🕒 Highlights Timezone-safe: Pure UTC ↔ JST conversion avoids double-offset errors. Sequential scheduling: Ensures each upload is 12 hours apart to prevent clustering. Customizable: Change SPANHOURS, BUFFERMIN, or directory paths easily. Retry-ready: Each upload and playlist step has retry logic to handle transient errors. 💡 Typical Use Cases Multi-part educational video series (e.g., A1–A2 English learning). Regular content release cadence without manual scheduling. Automated YouTube publishing pipelines for pre-produced content. --- Author: Zane Category: Automation / YouTube / Scheduler Timezone: JST (UTC+09:00)

ZaneBy Zane
226