Back to Integrations
integrationDiscord node
integrationGoogle Gemini Chat Model node

Discord and Google Gemini Chat Model integration

Save yourself the work of writing custom integrations for Discord and Google Gemini Chat Model and use n8n instead. Build adaptable and scalable Communication, HITL, AI, and Langchain workflows that work with your technology stack. All within a building experience you will love.

How to connect Discord and Google Gemini Chat Model

  • Step 1: Create a new workflow
  • Step 2: Add and configure nodes
  • Step 3: Connect
  • Step 4: Customize and extend your integration
  • Step 5: Test and activate your workflow

Step 1: Create a new workflow and add the first step

In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.

Discord and Google Gemini Chat Model integration: Create a new workflow and add the first step

Step 2: Add and configure Discord and Google Gemini Chat Model nodes

You can find Discord and Google Gemini Chat Model in the nodes panel. Drag them onto your workflow canvas, selecting their actions. Click each node, choose a credential, and authenticate to grant n8n access. Configure Discord and Google Gemini Chat Model nodes one by one: input data on the left, parameters in the middle, and output data on the right.

Discord and Google Gemini Chat Model integration: Add and configure Discord and Google Gemini Chat Model nodes

Step 3: Connect Discord and Google Gemini Chat Model

A connection establishes a link between Discord and Google Gemini Chat Model (or vice versa) to route data through the workflow. Data flows from the output of one node to the input of another. You can have single or multiple connections for each node.

Discord and Google Gemini Chat Model integration: Connect Discord and Google Gemini Chat Model

Step 4: Customize and extend your Discord and Google Gemini Chat Model integration

Use n8n's core nodes such as If, Split Out, Merge, and others to transform and manipulate data. Write custom JavaScript or Python in the Code node and run it as a step in your workflow. Connect Discord and Google Gemini Chat Model with any of n8n’s 1000+ integrations, and incorporate advanced AI logic into your workflows.

Discord and Google Gemini Chat Model integration: Customize and extend your Discord and Google Gemini Chat Model integration

Step 5: Test and activate your Discord and Google Gemini Chat Model workflow

Save and run the workflow to see if everything works as expected. Based on your configuration, data should flow from Discord to Google Gemini Chat Model or vice versa. Easily debug your workflow: you can check past executions to isolate and fix the mistake. Once you've tested everything, make sure to save your workflow and activate it.

Discord and Google Gemini Chat Model integration: Test and activate your Discord and Google Gemini Chat Model workflow

Auto-Generate & Publish SEO Blog Posts to WordPress with OpenRouter & Runware

Automate Blog Creation and Publishing with Ultra-Low Cost AI

This n8n workflow — BlogBlizt: Runaware Edition — automates the creation, enrichment, and publishing of SEO-optimized blog posts for WordPress using entirely free OpenRouter AI models for text and metadata generation, plus ultra-low-cost Runware AI for realistic featured images (as low as $0.0016 per image).

It’s triggered every 3 hours or manually via Telegram. Each run generates 1,500–3,500-word articles on trending topics in Technology, AI, Tech Facts, History, or Tips — all complete with catchy titles, slugs, meta descriptions, and visuals.

💰 Why This Is So Cost-Efficient

✅ Free metadata + article generation (OpenRouter free-tier models)
💸 Only cost is for image generation via Runware:
Image generation: ~$0.0016/image (the cheapest model could be $0,00065)

This is ideal for scale — generating dozens of high-quality blog posts with minimal expense.

⚡ Who Is This For?

Bloggers who want high-quality content without writing
SEO marketers seeking fresh, long-form articles
WordPress site owners automating publishing workflows
Growth hackers targeting high-volume content generation

❓ What Problem Does It Solve?

Creating SEO-rich blog content is time-consuming, expensive, and requires expertise. BlogBlizt eliminates this friction by using free models (OpenRouter) to generate text and metadata — making this workflow nearly free to operate, with the only cost being the featured image (~$0.0016/image).

🔧 What This Workflow Does

⏱ Triggers: Every 3 hours (or via Telegram command: generate)
🧠 Generates Metadata: Title, slug, category, focus keyphrase, and meta description using OpenRouter
✍️ Writes SEO Article: 1,500–3,500 words with headings, H2/H3s, CTA, and outbound links
🖼️ Creates Image: Generates realistic 1024×1024 blog image with Runware AI
📤 Publishes to WordPress: Auto-publishes with category ID, featured image, and Yoast SEO fields
📣 Notifies: Sends publish link to Discord and Telegram (optional)

🔐 Setup Instructions

Import .json into n8n
Add credentials:
OpenRouter API (free LLMs like LLaMA-3, Nemotron)
Runware API key (get it here)
(Optional) Telegram Bot + Discord Webhook
Test by sending the word generate via Telegram

🧩 Pre-Requirements

Self-hosted or cloud-based n8n instance
WordPress with category IDs configured:
Technology → 3
AI → 4
Tech Fact → 7
Tech History → 8
Tech Tips → 9
OpenRouter API Key (free)
Runware API Key (for images)
WordPress user ID (admin, default is 1)
Telegram bot (optional)
Discord webhook (optional)

🛠️ Customize It Further

Change writing tone or prompt in ✍️ Compose SEO Article Content node
Cofigure the category
Swap free LLMs (Claude, Gemini, GPT, etc.) in OpenRouter settings
Adjust schedule (every 6h, daily, etc.)
Extend alerts (email, Slack, Notion)

🧠 Nodes Used

Schedule Trigger
Telegram Trigger
@n8n/n8n-nodes-langchain (OpenRouter)
WordPress Node
HTTP Request (Runware API)
Discord Webhook
Sticky Notes (Documentation inside canvas)

📞 Support

Created by: Khaisa Studio
Tag: youtube, summarizer, telegram, openai
Category: AI Automation, Video Tools
Need a custom? contact me on LinkedIn or Web

Nodes used in this workflow

Popular Discord and Google Gemini Chat Model workflows

+2

Generate AI-Curated Reddit Digests for Telegram, Discord & Slack with Gemini

Automatically fetch, curate, and distribute Reddit content digests using AI-powered filtering. This workflow monitors multiple subreddits, ranks posts by relevance, removes spam and duplicates, then delivers beautifully formatted digests to Telegram, Discord, or Slack. Who's it for Perfect for content creators tracking trends, marketers monitoring discussions, researchers following specific topics, and community managers staying informed. Anyone who wants high-quality Reddit updates without manually browsing multiple subreddits. How it works The workflow fetches top posts from your chosen subreddits using Reddit's JSON API (no authentication required). Posts are cleaned, deduplicated, and filtered by upvote threshold and custom keywords. An AI model (Google Gemini, OpenAI, or Claude) then ranks remaining posts by relevance, filters out low-quality content, and generates a formatted digest. The final output is delivered to your preferred messaging platform on a schedule or on-demand. Setup requirements n8n version 1.0+ AI provider API key (Google Gemini recommended - has free tier) At least one messaging platform configured: Telegram bot token + chat ID Discord webhook URL Slack OAuth token + channel access How to set up Open the Configuration node and edit subreddit list, post counts, and keywords Configure the Schedule Trigger or use manual execution Add your AI provider credentials in the AI Content Curator node Enable and configure your preferred delivery platform (Telegram/Discord/Slack) Test with manual execution, then activate the workflow Customization options Subreddits**: Add unlimited subreddits to monitor (comma-separated) Time filters**: Choose from hour, day, week, month, year, or all-time top posts Keywords**: Set focus keywords to prioritize and exclude keywords to filter out Post count**: Adjust how many posts to fetch vs. how many appear in final digest AI prompt**: Customize ranking criteria and output format in the AI node Schedule**: Use cron expressions for hourly, daily, or weekly digests Output format**: Modify the formatting code to match your brand style Add email notifications, database storage, or RSS feed generation by extending the workflow with additional nodes.

Summarize Bitcoin news in Japanese and post to Discord with Gemini AI

Automate your Bitcoin content pipeline by turning the latest CoinDesk headlines into structured Japanese summaries posted to Discord every six hours — completely hands-free. Who is this for Crypto traders, Discord community managers, and content creators who want to keep their audience updated on Bitcoin news without writing posts manually. No coding required. What this workflow does On a six-hour schedule, the workflow fetches the three newest articles from the CoinDesk RSS feed. Each article is sent to Google Gemini 2.5 Flash via a Basic LLM Chain node. A Structured Output Parser then extracts the AI response into four clean fields: a one-line Japanese summary, a brief AI commentary, the article URL, and hashtags. The structured post is delivered to a Discord channel via webhook. Each post is also saved to Google Sheets for auditing, and a Slack notification confirms every successful run. How to set up Open the Set config values node and fill in your Google Sheet ID, Discord Webhook URL, and hashtags. Add your Google Gemini API credential to the Gemini 2.5 Flash node (free tier works). In Discord, go to your channel settings → Integrations → Webhooks, create a new webhook, and paste the URL into Set config values. Connect your Google Sheets OAuth2 credential and set the target sheet name. Add your Slack credential and update the channel ID in the Notify Slack node. Activate the workflow — it will run automatically every six hours. Requirements Google Gemini API key (free tier works) Discord server with webhook permission Google Sheets OAuth2 credential Slack API credential How to customize Swap the RSS URL in Set config values to follow Ethereum, Solana, or any crypto feed. Edit the prompt inside Basic LLM Chain to change language or post style. Update the hashtags in Set config values. Adjust the posting interval in the Schedule Trigger node (default: every 6 hours). Add a Filter node between RSS and LLM to post only articles matching specific keywords.

Automate Blog Updates via Discord with GitHub and Gemini AI

Automate blog updates via Discord with GitHub and customizable AI chatbot > ⚠️ Disclaimer: This template uses the n8n-nodes-discord-trigger community node, which means it works only in self-hosted n8n instances.(works for both cloud and localhost) Who’s it for This workflow is designed for developers, bloggers, and technical writers who want a hands-free way to draft and publish blog posts directly from Discord. Instead of juggling multiple tools, you just send a message to your Discord bot, and the workflow creates a properly formatted Markdown file in your GitHub repo. How it works Listens for new messages in a Discord channel or DM using the Discord Trigger (community node). Passes your message to an AI chatbot model (Google Gemini, OpenAI GPT, or any other connector you prefer) to draft or format the content. Uses GitHub nodes to check existing files, read repo contents, and create new .md posts in the specified directory. Adds the correct timestamp with the Date & Time node. Sends a confirmation reply back to Discord(Regular Message Node). Guardrails ensure it only creates new Markdown files in the correct folder, without overwriting or editing existing content. How to set up Import the workflow (or download the file here BlogAutomationclean.json) into your self-hosted n8n. Install the n8n-nodes-discord-trigger community node inside n8n workflow dashboard(click the link for the steps of setup). Create credentials for: Discord bot trigger from the community node Discord bot send Message from the Regular Discord Message Node GitHub (personal access token with repo permissions) Your AI provider (Gemini, OpenAI, etc.) Update the GitHub nodes with: Owner → your GitHub username Repo → your blog repo name Path → target directory for new Markdown posts Customize the AI agent’s system prompt to match your tone and workflow. (Default prompt included below.) Test it in a private Discord channel before going live. Requirements Self-hosted n8n instance(works both on cloud and localhost) GitHub repository with write access Discord bot credentials(**BOTH ARE REQUIRED: COMMUNITY NODE FOR TRIGGER AND REGULAR NODE** read below for reasoning) AI model credentials (Gemini, OpenAI, or other supported provider) How to customize the workflow Swap the AI model node for any provider you like: Gemini, OpenAI, or even a local LLM. Adjust the prompt to enforce your blog style guide. Add additional steps like auto-publishing, Slack notifications, or Notion syncs. Modify the directory path or file naming rules to fit your project. Reason for Using The Community Discord Trigger Node and Regular Discord Message Node From Testing, the Community Discord node cannot send big messages(Has a Certain limit), while the Original/Regular Discord Message Node can send far beyond that amount which helps for viewing Files. Feel Free to use both trigger and Send Message from the community node if facing issues, it will still work flawless other than message limit Default Prompt Core Identity & Persona You are the n8n Blog Master, a specialized AI agent. Your primary function is to assist your user with content management. Your Mission:** Automate the process of creating, formatting, editing, and saving blog posts as Markdown files within the user’s specified repository. User Clarification:* The repository owner always refers to your user and, in the context of API calls, the repository owner*. It is never part of a file path. Personality:** Helpful, precise, security-conscious. Semi-casual and engaging, but never overly cheerful. Operational Zone & Constraints Repository:* You may only interact with the repository <insert-repo-name-here>*. Owner:* The repository owner is <insert-username-here>*. Branch:** Always operate on the main branch. Directory Access:* You can only write or edit files in the directory <insert-directory-path-here>*. You are forbidden from interacting elsewhere. File Permissions:** You may create new .md files. If a file already exists, notify the user and ask if they want to edit it. Editing is only allowed if the user explicitly confirms (e.g., “yes”, “go ahead”, “continue”). If the user confirms, proceed with editing. Available Tools & Usage Protocol You have a limited but well-defined toolset. Always use them exactly as described: Date & Time Tool Purpose: Always fetch the current date and time in IST (India Standard Time). Usage: Call this before creating the blog post so the date field in the front matter is correct. Do not use any other timezone. GitHub Nodes Create:* Used to create new files within <insert-directory-path-here>*. Requires three parameters: owner → always <insert-username-here> repo → always <insert-repo-name-here> path → must be <insert-directory-path-here>/<filename>.md List:* Can list files inside <insert-directory-path-here>*. Use it to check existing filenames before creating new ones. Read:** Can fetch contents of files if needed. Edit:* Can update a specific file in <insert-directory-path-here>*. Protocol: Before editing, explicitly ask: “Are you sure you want me to edit <filename>.md?” If the user responds with “yes”, “continue”, or similar confirmation, proceed. If the user declines, do nothing. Constraint: Never attempt operations outside the specified directory. Data Storage & Message History Purpose: Store temporary user confirmations and recall previous user messages as part of memory. Example: If you ask for edit confirmation and the user replies “yes” or “continue”, record that in storage. If later in the same conversation the user says “go ahead” without repeating the filename, check both storage and previous messages to infer intent. Always reset confirmation after the action is completed. Standard Workflow: Creating or Editing Blog Posts Activation: Begin when the user says: “Draft a new post on…” “Make the body about…” “Use my rough notes…” “Modify it to include…” “Edit the file…” Information Gathering: Ask for the Title (mandatory for new posts). Gather topic, points, or raw notes from the user. If user provides incomplete notes, expand them into a coherent, well-structured article. Drafting & Formatting: Call the Date & Time tool. Format posts in the following template: --- title: "The Title Provided by the User" date: "YYYY-MM-DD" --- [Well-structured blog content goes here. Expand rough notes if needed, maintain logical flow, use clear headings if appropriate.] Thanks for Reading! Writing rules: Tone: Neutral, informative, lightly conversational — not too cheerful. Flow: Use line breaks for readability. Expansion: If notes are provided, polish and structure them. Modification: If asked, revise while preserving original meaning. File Naming: Generate a short kebab-case filename from the title (e.g., "Making My Own Java CLI-Based RPG!" → java-cli-rpg.md). File Creation vs Editing: If creating → Use the GitHub Create tool. If file already exists → Ask the user if they want to edit it. Store their response in Data Storage. If confirmation = yes → proceed with GitHub Edit tool. If no → cancel operation. Final Action: Confirm success to the user after creation or editing. Advanced Error Handling: "Resource Not Found" If the create_github_file tool fails with "Resource not found": First Failure: Notify the user that the attempt failed. State the exact path used. Retry automatically once. Second Failure: If it fails again, explain that standard creation isn’t working. Suggest it may be a permissions issue. Await user instructions before proceeding further. Contact and Changes Feel Free To Contribute to it I do not own anything made here, everything was made by their respective owners Shout-out to katerlol for making the discord Node Trigger Contact me Here if you need any help!
+4

Publish SEO blogs to WordPress with GPT-4.1, DALL-E, Gemini, and Google Sheets

Automatically publish blog content to WordPress with AI-generated branded images, internal linking, and client reporting using Google Sheets, OpenAI, and Gemini What this workflow does This workflow receives written blog content from your content creation automation and handles the complete WordPress publishing process. It adds internal links to your content based on target keywords, generates 3 AI-powered branded images (thumbnail + 2 content images), uploads them to WordPress, inserts them into your article, publishes the complete blog with proper categories, updates tracking sheets, and notifies clients automatically. Perfect for agencies managing multiple client blogs who want to eliminate manual publishing tasks while maintaining brand consistency and SEO optimization. Key features Intelligent internal linking: Automatically analyzes your target keywords and adds up to 3 natural anchor links within the content to improve site SEO and user navigation AI image generation: Creates 3 professional branded images using DALL-E based on your blog topic and brand colors - one thumbnail with overlay text and two supporting content images Automated WordPress publishing: Publishes blogs with proper categories, sets featured images, and handles all WordPress REST API interactions without manual intervention Multi-client management: Processes different projects based on individual client settings including image preferences, brand colors, and reporting requirements Tracking and reporting: Updates Google Sheets with live URLs and publish dates, sends Discord notifications to project managers, and triggers client reporting workflows How it works Receives content from writing automation: Triggered by your blog content creation workflow with title, body content, focus keyword, and client details Fetches project configuration: Loads client-specific settings from Google Sheets including website URL, WordPress API credentials, image creation preferences, and brand guidelines Adds internal links: Retrieves target keywords and URLs from project sheets, filters valid links, and uses Gemini AI to intelligently insert 3 contextual anchor links Generates branded images (if enabled): Uses OpenAI GPT to create detailed image prompts based on blog topic and brand colors, then generates 3 images with DALL-E (thumbnail with text overlay + 2 content images) Uploads to WordPress media library: Processes each image through a loop, uploads to WordPress, stores metadata including URLs and alt text Inserts images into content: Uses Gemini AI to intelligently place images at strategic positions within the article while preserving existing HTML structure and anchor links Publishes to WordPress: Creates the blog post with proper title, content, categories, and sets the thumbnail as featured image via REST API Updates tracking sheets: Records the live blog URL and publish date in Google Sheets for project management Sends notifications: Triggers Discord alerts for project managers and executes the Reporting Manager workflow for client communication via email, Slack, or WhatsApp Setup requirements Tools you'll need: Active n8n instance (self-hosted or n8n Cloud) Google Sheets with OAuth access for project management WordPress site with REST API enabled and proper authentication OpenAI API key (for DALL-E image generation) Google Gemini API key (for content processing) Discord bot (optional, for team notifications) Blog Content Creation workflow (Part 1 - sold separately or built independently) Estimated setup time: 30-40 minutes Configuration steps Add credentials in n8n: Google Sheets OAuth API OpenAI API (for DALL-E image generation) Google Gemini API (for AI content processing) Discord Bot API (for notifications) WordPress credentials (API tokens) Set up Project Central Sheet: Create a master Google Sheet with these columns: Client ID Website URL Blog API (WordPress auth token) GMB Name (business name) Image Creation (Yes/No) Image Instructions (specific image guidelines) Color and Font (brand colors in hex format) Discord Channel ID Project Manager Discord ID On Page Sheet (URL to client's tracking sheet) Project Information Sheet (URL to internal linking keywords sheet) Categories (WordPress category IDs) Update the sheet URL in the "Fetch Project Configuration" node Create client-specific sheets: For each client, maintain two sheets: Sheet 1: TGT Keywords (for internal linking) Keywords column: Target keywords to link Target Pages column: Full URLs to link to Sheet 2: Content Requirement & Posting (for tracking) row_number: Unique identifier Focus Keyword: Target SEO keyword Content Topic: Blog title Publish URLs: Live blog URL (auto-filled) Published Date: Publish date (auto-filled) Configure WordPress authentication: Enable REST API on your WordPress site Generate API authentication tokens Update authorization values in these nodes: "Upload to WordPress Media" "Publish Blog with Featured Image" "Set Thumbnail as Featured Image" "Publish Blog without Images" Connect to Blog Creation workflow: Ensure your Blog Content Creation workflow (Part 1) triggers this workflow The trigger should pass these workflow inputs: Client ID Blog S.NO. (row number) Blog Title Content (HTML formatted) OnPage SEO (tracking sheet URL) Focus Keyword Set up Reporting Manager (optional): Create or connect your client reporting workflow Update the workflow ID in "Trigger Client Reporting Workflow" node This sends automated reports to clients via email, Slack, or WhatsApp Test the workflow: Run your Blog Creation workflow manually with test data Verify images generate correctly with brand colors Check WordPress post publishes with featured image Confirm tracking sheet updates Test Discord notification delivery Use cases Marketing agencies: Manage blog publishing for 10+ clients with different brand guidelines and WordPress sites from a single automation Content teams: Eliminate 2-3 hours of manual work per blog by automating image creation, internal linking, and WordPress publishing SEO specialists: Ensure consistent internal linking and proper category assignment across all published content Freelance writers: Offer end-to-end blog services including branded image creation and WordPress publishing without manual intervention SaaS companies: Maintain consistent blog publishing schedule across multiple product blogs with automated tracking and reporting Customization options Modify image generation: Edit the "Generate Image Prompts with AI" node to change image style, dimensions, or prompt instructions Change DALL-E model or image size in "Generate Image with DALL-E" node Adjust internal linking: Modify the "Add Internal Links to Content" agent prompt to change linking strategy (more/fewer links, different placement rules) Change notification channels: Replace Discord with Slack, email, or webhook notifications Add multiple notification channels in parallel WordPress customization: Add custom fields, tags, or metadata to published posts Integrate with WordPress plugins via REST API extensions Troubleshooting Images not generating: Check OpenAI API key validity and account credits. Verify image prompt node receives content properly. WordPress publish fails: Confirm REST API is enabled, authentication tokens are correct, and site URL is properly formatted with trailing slash. Internal links not appearing: Ensure "TGT Keywords" sheet has valid URLs starting with "http" and filter node is working correctly. Tracking sheet not updating: Verify Google Sheets OAuth connection and that row_number matches between sheets. Discord notification fails: Check Discord bot permissions and channel ID accuracy. Resources n8n documentation WordPress REST API guide OpenAI DALL-E API Google Gemini API Google Sheets API Important notes This workflow is specifically for blog publishing. To use it correctly, you must first have a Blog Content Creation workflow that generates the blog title, content, and required metadata. I have already shared a Blog Writing Automation workflow, which you can use directly for content creation before running this publishing workflow. Make sure the content creation workflow runs before this publishing workflow, as this setup depends on the generated output. Support Need help or custom development? 📧 Email: [email protected] 🌐 Website: https://isawow.com/
+4

Create and publish SEO blog posts using Google Sheets, Gemini/OpenAI, Ideogram, and WordPress

This workflow automates the complete blog publishing process. It removes manual work from content creation, image generation, category management, and WordPress publishing by using AI and n8n. It helps agencies, SEO teams, and content creators manage blogs at scale. Key Features Scheduled or manual blog publishing Automated topic research and content writing AI-generated featured and in-content images using Ideogram Dynamic WordPress category detection and creation Automatic media upload with SEO-friendly alt text Internal linking using sitemap data Google Sheets logging for published URLs Error notifications for failed executions What This Workflow Does Input Blog topics or keywords stored in Google Sheets Target WordPress site details Publishing rules and schedule Processing Triggers the workflow on a schedule or manual run Fetches blog posting data from Google Sheets Validates active projects or websites Performs topic and SEO research Writes long-form, SEO-optimized blog content Generates image prompts and creates images using Ideogram Uploads images to WordPress with alt text Detects or creates blog categories dynamically Publishes the blog post to WordPress Output Live published blog post URL Updated Google Sheet with publishing details Notification alerts if any step fails Setup Instructions Prerequisites n8n instance (cloud or self-hosted) WordPress site with REST API access Google Sheets access AI model credentials (Google Gemini, OpenAI, or DeepSeek) Ideogram API access Notification service (Discord or Slack) Step 1: Import the Workflow Download or copy the workflow JSON In n8n, go to Workflows → Import from file / JSON Import the workflow Step 2: Configure Credentials Set up the required credentials inside n8n's credential manager: Google Sheets OAuth**: For reading posting data and saving URLs WordPress API**: For publishing posts and uploading media AI Model**: Connect Google Gemini, OpenAI, or DeepSeek Ideogram API**: For AI image generation Discord/Slack Webhook**: For error notifications Important: No credentials are hardcoded. All must be connected via n8n's credential manager. Step 3: Configure Google Sheets Prepare a Google Sheet containing: Blog topic or keyword Target website or domain Publishing status fields Domain ID for tracking Update the Sheet ID inside the Get_Post_Data node after import. Step 4: Configure Website Access Update the PBN_Website_Access node with your WordPress site access endpoint or API. This node should return: Complete WordPress URL Basic authentication token Sitemap post URL Step 5: Configure Publishing & Schedule Adjust the Schedule Trigger if auto-publishing is required Modify publishing frequency or time zone Review WordPress post status (draft or publish) Step 6: Test & Activate Add one test row in Google Sheets Run the workflow manually Verify: Content creation Image generation WordPress publishing Sheet updates Activate the workflow Usage Guide Adding New Blog Posts Add a new row in the connected Google Sheet with the required blog topic and website details. The workflow will automatically process and publish the post on the next execution. Understanding the Output After execution, the workflow: Publishes a complete blog post on WordPress Attaches featured and in-content images Assigns the correct category Logs the live URL back to Google Sheets Workflow Node Breakdown Get_Post_Data Fetches blog posting details from Google Sheets based on the current day. It pulls keywords, landing pages, domain IDs, and posting websites. get_client_status Checks the client's project status from the project sheet. It verifies whether the client is active or inactive before proceeding further. This prevents publishing content for paused or stopped clients. PBN_Website_Access Fetches WordPress website access details such as site URL, authentication token, and sitemap URL. These details are required for publishing posts, uploading images, and managing categories. Do the Research on the Topic Performs deep SEO research on the target keyword. It analyzes search intent, content gaps, and audience needs. This ensures the generated content is informative, relevant, and SEO-optimized. sitemap_crawl (internal_linking) Crawls the website sitemap to collect internal URLs. These URLs are later used for internal linking inside the blog content. Internal links help improve SEO and site structure. write_content Uses AI to write an 800-1000 word SEO-optimized blog article based on research data. The content includes proper HTML formatting, internal links, and anchor keyword placement. extract_title_body Separates the H1 title from the blog body content for proper WordPress publishing format. classify_category Automatically determines the most suitable category for the blog post by analyzing the blog title and content context. This keeps the website's category structure clean and relevant. get_category & create_category Checks if the determined category exists in WordPress. If not, it creates a new category automatically. generate_image_prompt Analyzes the blog content and generates AI prompts for creating relevant images including thumbnail and in-content images. Thumbnail Image Generator & Blog Image Generator Generate high-quality images using Ideogram API based on AI-generated prompts. Images are created with proper resolution and rendering settings. Thumbnail Uploading & Blog Image Uploading Upload generated images to WordPress media library and retrieve media IDs for post attachment. Add Alt Text in Images Adds SEO-friendly alt text to uploaded images to improve accessibility and search engine optimization. Blog and Photo Merge Merges the generated images into the blog content at appropriate positions within the article. publish_blog Publishes the complete blog post to WordPress with title, content, category, featured image, and publish status. save_live_url Saves the live published blog URL back into Google Sheets along with keyword, website URL, and timestamp for tracking and reporting. If Error Existed Then Get Notified Sends instant Discord or Slack notifications when any error occurs during workflow execution, ensuring no failure goes unnoticed. Customization Options Change blog length or tone in the content generation node Modify image style or resolution in Ideogram nodes Add multi-site publishing using Switch nodes Replace notification channel (Discord to Slack or Email) Extend workflow to social media posting Troubleshooting Blog not published Check WordPress credentials and REST API permissions. Images not generated Verify Ideogram API credentials and prompt formatting. Sheet not updating Ensure correct Sheet ID and OAuth permissions. Workflow stopped Review execution logs and error notification messages. Use Cases SEO blog automation for agencies Content publishing for niche websites Scalable blog management AI-assisted content operations Hands-free WordPress publishing Final Notes This workflow is designed to be reusable, scalable, and creator-friendly. It follows n8n best practices, avoids hardcoded credentials, and is suitable for public sharing as a workflow template. For any questions or support, please contact: [email protected] or fill out this form: https://www.incrementors.com/contact-us/
+4

Auto-Generate & Publish SEO Blog Posts to WordPress with OpenRouter & Runware

Automate Blog Creation and Publishing with Ultra-Low Cost AI This n8n workflow — BlogBlizt: Runaware Edition — automates the creation, enrichment, and publishing of SEO-optimized blog posts for WordPress using entirely free OpenRouter AI models for text and metadata generation, plus ultra-low-cost Runware AI for realistic featured images (as low as $0.0016 per image). It’s triggered every 3 hours or manually via Telegram. Each run generates 1,500–3,500-word articles on trending topics in Technology, AI, Tech Facts, History, or Tips — all complete with catchy titles, slugs, meta descriptions, and visuals. 💰 Why This Is So Cost-Efficient ✅ Free metadata + article generation (OpenRouter free-tier models) 💸 Only cost is for image generation via Runware: Image generation: ~$0.0016/image (the cheapest model could be $0,00065) This is ideal for scale — generating dozens of high-quality blog posts with minimal expense. ⚡ Who Is This For? Bloggers who want high-quality content without writing SEO marketers seeking fresh, long-form articles WordPress site owners automating publishing workflows Growth hackers targeting high-volume content generation ❓ What Problem Does It Solve? Creating SEO-rich blog content is time-consuming, expensive, and requires expertise. BlogBlizt eliminates this friction by using free models (OpenRouter) to generate text and metadata — making this workflow nearly free to operate, with the only cost being the featured image (~$0.0016/image). 🔧 What This Workflow Does ⏱ Triggers: Every 3 hours (or via Telegram command: generate) 🧠 Generates Metadata: Title, slug, category, focus keyphrase, and meta description using OpenRouter ✍️ Writes SEO Article: 1,500–3,500 words with headings, H2/H3s, CTA, and outbound links 🖼️ Creates Image: Generates realistic 1024×1024 blog image with Runware AI 📤 Publishes to WordPress: Auto-publishes with category ID, featured image, and Yoast SEO fields 📣 Notifies: Sends publish link to Discord and Telegram (optional) 🔐 Setup Instructions Import .json into n8n Add credentials: OpenRouter API (free LLMs like LLaMA-3, Nemotron) Runware API key (get it here) (Optional) Telegram Bot + Discord Webhook Test by sending the word generate via Telegram 🧩 Pre-Requirements Self-hosted or cloud-based n8n instance WordPress with category IDs configured: Technology → 3 AI → 4 Tech Fact → 7 Tech History → 8 Tech Tips → 9 OpenRouter API Key (free) Runware API Key (for images) WordPress user ID (admin, default is 1) Telegram bot (optional) Discord webhook (optional) 🛠️ Customize It Further Change writing tone or prompt in ✍️ Compose SEO Article Content node Cofigure the category Swap free LLMs (Claude, Gemini, GPT, etc.) in OpenRouter settings Adjust schedule (every 6h, daily, etc.) Extend alerts (email, Slack, Notion) 🧠 Nodes Used Schedule Trigger Telegram Trigger @n8n/n8n-nodes-langchain (OpenRouter) WordPress Node HTTP Request (Runware API) Discord Webhook Sticky Notes (Documentation inside canvas) 📞 Support Created by: Khaisa Studio Tag: youtube, summarizer, telegram, openai Category: AI Automation, Video Tools Need a custom? contact me on LinkedIn or Web

Build your own Discord and Google Gemini Chat Model integration

Create custom Discord and Google Gemini Chat Model workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.

Discord supported actions

Create
Create a new channel
Delete
Delete a channel
Get
Get a channel
Get Many
Retrieve the channels of a server
Update
Update a channel
Delete
Delete a message in a channel
Get
Get a message in a channel
Get Many
Retrieve the latest messages in a channel
React with Emoji
React to a message with an emoji
Send
Send a message to a channel, thread, or member
Send and Wait for Response
Send a message and wait for response
Get Many
Retrieve the members of a server
Role Add
Add a role to a member
Role Remove
Remove a role from a member

FAQs

  • Can Discord connect with Google Gemini Chat Model?

  • Can I use Discord’s API with n8n?

  • Can I use Google Gemini Chat Model’s API with n8n?

  • Is n8n secure for integrating Discord and Google Gemini Chat Model?

  • How to get started with Discord and Google Gemini Chat Model integration in n8n.io?

Looking to integrate Discord and Google Gemini Chat Model in your company?

Over 3000 companies switch to n8n every single week

Why use n8n to integrate Discord with Google Gemini Chat Model

Build complex workflows, really fast

Build complex workflows, really fast

Handle branching, merging and iteration easily.
Pause your workflow to wait for external events.

Code when you need it, UI when you don't

Simple debugging

Your data is displayed alongside your settings, making edge cases easy to track down.

Use templates to get started fast

Use 1000+ workflow templates available from our core team and our community.

Reuse your work

Copy and paste, easily import and export workflows.

Implement complex processes faster with n8n

red iconyellow iconred iconyellow icon