Automated blog generation with Gemini AI, GitHub & Jekyll publishing
π Use Case
This n8n workflow automates the creation and publication of technical blog posts based on a list of topics stored in Google Sheets. It fetches context using Tavily and Wikipedia, generates Markdown-formatted content with Gemini AI, commits it to a GitHub repository, and updates a Jekyll-powered blog β all without manual intervention.
Ideal for developers, bloggers, or content teams who want to streamline technical content creation and publishing.
βοΈ Setup Instructions
π Prerequisites
- n8n (cloud or self-hosted)
- Tavily API key
- Google Sheets with blog topics
- Gemini (Google Palm) API key
- GitHub repository (Jekyll enabled)
- GitHub OAuth2 credentials
- Google OAuth2 credentials
π§© Setup Steps
- Import the workflow JSON into your n8n instance.
- Set up the following credentials in n8n:
Tavily APIGoogle Sheets OAuth2Google Palm/Gemini AIGitHub OAuth2
- Prepare your Google Sheet:
- Columns:
Title,status,row_number - Set
statusto blank for topics to be picked up.
- Columns:
- Configure:
- GitHub repo and
_posts/path - Jekyll setup (front matter,
_config.yml, GitHub Pages)
- GitHub repo and
- Adjust prompt/custom parameters if needed.
- Enable and deploy the workflow. Schedule it daily or trigger manually.
π Workflow Details
| Node | Function |
|------|----------|
| Schedule Trigger | Triggers the flow at a set interval |
| Google Sheets (Get Topic) | Fetches the next incomplete blog topic |
| Extract Topic | Parses topic text from the sheet |
| Tavily Search | Gathers up-to-date content related to the topic |
| Wikipedia Tool | Optionally adds more context or images |
| Summarize Results | Formats the context for the AI |
| Gemini AI Agent (LangChain) | Generates a Markdown blog post with YAML front matter |
| Set File Parameters | Prepares the filename, content, and commit message |
| GitHub Commit | Uploads the .md file to the _posts/ directory |
| Update Google Sheet | Marks topic as done after successful commit |
π οΈ Customization Options
- Change LLM prompt (e.g. tone, depth, format).
- Use OpenAI instead of Gemini by switching nodes.
- Modify filename pattern or GitHub repo path.
- Add Slack/Discord notifications after publish.
- Extend flow to upload images or embed YouTube links.
β οΈ Community Nodes Used
This workflow uses the following community nodes:
@tavily/n8n-nodes-tavily.tavilyβ for deep search
> β οΈ Ensure these are installed and enabled in your n8n instance.
π‘ Pro Tips
- Use GitHub Actions to trigger an automatic Jekyll build post-commit.
- Structure blog posts with front matter, headings, and table of contents for SEO.
- Set
Schedule Triggerto daily at a fixed time to keep content flowing. - Enhance formatting in AI output using code blocks, images, and lists.
β Example Output
---
title: "How LLMs Are Changing Web Development"
date: "2025-07-25"
categories: [webdev, AI]
tags: [LLM, Gemini, n8n, automation]
excerpt: "Learn how LLMs like Gemini are transforming how we generate and deploy developer content."
author: "Saswat Saubhagya"
---
## Table of Contents
- [Introduction](#introduction)
- [Understanding LLMs](#understanding-llms)
- [Use Cases in Web Development](#use-cases-in-web-development)
- [Challenges](#challenges)
- [Conclusion](#conclusion)
...
Automated Blog Generation with Gemini AI and GitHub/Jekyll Publishing
This n8n workflow automates the entire process of generating blog posts using Google Gemini AI and publishing them to a GitHub repository, suitable for Jekyll-based blogs. It streamlines content creation from idea to publication, making it ideal for maintaining an active blog with minimal manual effort.
What it does
This workflow performs the following key steps:
- Triggers on a Schedule: The workflow is initiated on a predefined schedule (e.g., daily, weekly) to check for new content ideas.
- Fetches Blog Post Ideas from Google Sheets: It reads a Google Sheet to retrieve a list of potential blog post topics or prompts.
- Generates Blog Content with Google Gemini AI: For each topic, it uses the Google Gemini Chat Model via an AI Agent to generate comprehensive blog post content. It leverages a Wikipedia tool to gather information, ensuring the generated content is well-researched.
- Formats Content for Jekyll: The generated content is then processed by a Code node and an Edit Fields (Set) node to format it correctly for Jekyll, including adding front matter (title, date, layout, etc.) and converting it into a Markdown file.
- Publishes to GitHub: Finally, the workflow creates a new file (the blog post) in a specified GitHub repository, effectively publishing the blog post to a Jekyll site.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance (self-hosted or cloud).
- Google Sheets Account: A Google Sheets spreadsheet containing your blog post ideas/prompts.
- Google Gemini API Key: Access to the Google Gemini Chat Model (configured as an n8n credential).
- GitHub Account: A GitHub repository where your Jekyll blog is hosted. You'll need a GitHub Personal Access Token (PAT) with repository write access (configured as an n8n credential).
Setup/Usage
- Import the Workflow:
- Copy the provided JSON code.
- In your n8n instance, click "New" to create a new workflow.
- Go to "File" > "Import from JSON" and paste the copied JSON.
- Configure Credentials:
- Google Sheets: Set up a Google Sheets credential. Ensure it has access to the spreadsheet containing your blog post ideas.
- Google Gemini Chat Model: Configure a credential for the Google Gemini Chat Model. This typically involves providing your API key.
- GitHub: Set up a GitHub credential. This should be a Personal Access Token (PAT) with
reposcope to allow the workflow to create files in your repository.
- Customize Nodes:
- Schedule Trigger (Node 839): Adjust the schedule to your desired frequency for generating and publishing blog posts.
- Google Sheets (Node 18):
- Specify the Spreadsheet ID and Sheet Name where your blog post ideas are located.
- Ensure the sheet has a column that the workflow can read for post topics (e.g.,
topic).
- AI Agent (Node 1119):
- Review the prompt used for generating content. You might want to customize it to better suit your blog's style and requirements.
- The Wikipedia tool (Node 1201) is already configured as a tool for the agent.
- Edit Fields (Node 38) and Code (Node 834): These nodes are responsible for formatting the AI-generated content into a Jekyll-compatible Markdown file with front matter. You may need to adjust the fields and logic here to match your specific Jekyll blog's front matter requirements (e.g.,
layout,categories,tags). - GitHub (Node 16):
- Provide your Owner (GitHub username or organization) and Repository name.
- Specify the Branch (e.g.,
mainormaster) where you want to commit the new blog posts. - Define the File Path where the blog posts should be created (e.g.,
_posts/{{ $json.fileName }}.md). - Customize the Commit Message.
- Activate the Workflow: Once all configurations are complete, activate the workflow. It will now run automatically based on your defined schedule.
Related Templates
AI multi-agent executive team for entrepreneurs with Gemini, Perplexity and WhatsApp
This workflow is an AI-powered multi-agent system built for startup founders and small business owners who want to automate decision-making, accountability, research, and communication, all through WhatsApp. The βvirtual executive team,β is designed to help small teams to work smarter. This workflow sends you market analysis, market and sales tips, It can also monitor what your competitors are doing using perplexity (Research agent) and help you stay a head, or make better decisions. And when you feeling stuck with your start-up accountability director is creative enough to break the barrier π― Core Features π§βπΌ 1. President (Super Agent) Acts as the main controller that coordinates all sub-agents. Routes messages, assigns tasks, and ensures workflow synchronization between the AI Directors. π 2. Sales & Marketing Director Uses SerpAPI to search for market opportunities, leads, and trends. Suggests marketing campaigns, keywords, or outreach ideas. Can analyze current engagement metrics to adjust content strategy. π΅οΈββοΈ 3. Business Research Director Powered by Perplexity AI for competitive and market analysis. Monitors competitor moves, social media engagement, and product changes. Provides concise insights to help the founder adapt and stay ahead. β° 4. Accountability Director Keeps the founder and executive team on track. Sends motivational nudges, task reminders, and progress reports. Promotes consistency and discipline β key traits for early-stage success. ποΈ 5. Executive Secretary Handles scheduling, email drafting, and reminders. Connects with Google Calendar, Gmail, and Sheets through OAuth. Automates follow-ups, meeting summaries, and notifications directly via WhatsApp. π¬ WhatsApp as the Main Interface Interact naturally with your AI team through WhatsApp Business API. All responses, updates, and summaries are delivered to your chat. Ideal for founders who want to manage operations on the go. βοΈ How It Works Trigger: The workflow starts from a WhatsApp Trigger node (via Meta Developer Account). Routing: The President agent analyzes the incoming message and determines which Director should handle it. Processing: Marketing or sales queries go to the Sales & Marketing Director. Research questions are handled by the Business Research Director. Accountability tasks are assigned to the Accountability Director. Scheduling or communication requests are managed by the Secretary. Collaboration: Each sub-agent returns results to the President, who summarizes and sends the reply back via WhatsApp. Memory: Context is maintained between sessions, ensuring personalized and coherent communication. π§© Integrations Required Gemini API β for general intelligence and task reasoning Supabase- for RAG and postgres persistent memory Perplexity API β for business and competitor analysis SerpAPI β for market research and opportunity scouting Google OAuth β to connect Sheets, Calendar, and Gmail WhatsApp Business API β for message triggers and responses π Benefits Acts like a team of tireless employees available 24/7. Saves time by automating research, reminders, and communication. Enhances accountability and strategy consistency for founders. Keeps operations centralized in a simple WhatsApp interface. π§° Setup Steps Create API credentials for: WhatsApp (via Meta Developer Account) Gemini, Perplexity, and SerpAPI Google OAuth (Sheets, Calendar, Gmail) Create a supabase account at supabase Add the credentials in the corresponding n8n nodes. Customize the system prompts for each Director based on your startupβs needs. Activate and start interacting with your virtual executive team on WhatsApp. Use Case You are a small organisation or start-up that can not afford hiring; marketing department, research department and secretar office, then this workflow is for you π‘ Need Customization? Want to tailor it for your startup or integrate with CRM tools like Notion or HubSpot? You can easily extend the workflow or contact the creator for personalized support. Consider adjusting the system prompt to suite your business
π 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.
Send WooCommerce discount coupons to customers via WhatsApp using Rapiwa API
Who is this for? This workflow is ideal for WooCommerce store owners who want to automatically send promotional WhatsApp messages to their customers when new coupons are created. Itβs designed for marketers and eCommerce managers looking to boost engagement, streamline coupon sharing, and track campaign performance effortlessly through Google Sheets. Overview This workflow listens for WooCommerce coupon creation events (coupon.created) and uses customer billing data to send promotional WhatsApp messages via the Rapiwa API. The flow formats the coupon data, cleans phone numbers, verifies WhatsApp registration with Rapiwa, sends the promotional message when verified, and logs each attempt to Google Sheets (separate sheets for verified/sent and unverified/not sent). What this Workflow Does Listens for new coupon creation events in WooCommerce via the WooCommerce Trigger node Retrieves all customer data from the WooCommerce store Processes customers in batches to control throughput Cleans and formats customer phone numbers for WhatsApp Verifies if phone numbers are valid WhatsApp accounts using Rapiwa API Sends personalized WhatsApp messages with coupon details to verified numbers Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Automated coupon distribution: Triggers when new coupons are created in WooCommerce Customer data retrieval: Fetches all customer information from WooCommerce Phone number validation: Verifies WhatsApp numbers before sending messages Personalized messaging: Includes customer name and coupon details in messages Dual logging system: Tracks both successful and failed message attempts Rate limiting: Uses batching and wait nodes to prevent API overload Data formatting: Structures coupon information for consistent messaging Google Sheet Column Structure A Google Sheet formatted like this β€ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: | name | number | email | address1 | couponCode | couponTitle | couponType | couponAmount | createDate | expireDate | validity | status | | ----------- | ------------- | --------------------------------------------------- | --------- | ---------- | -------------- | ---------- | ------------ | ------------------- | ------------------- | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | verified | sent | Requirements n8n instance with the following nodes: WooCommerce Trigger, Code, SplitInBatches, HTTP Request, IF, Google Sheets, Wait WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Message Content: The current message template references the first coupon only (coupons[0]). Adjust if you need to handle multiple coupons. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen