Proofread markdown blog posts with Gemini, Groq fallback and GitHub auto-commit
Ready for 3.0What this workflow does
This AI workflow has 22 nodes and runs manually, when you click “Execute workflow”. Along the way it connects GitHub, Google Gemini Chat Model and Groq Chat Model.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Github Config (Edit Fields (Set)): sets 4 fields: repoOwner, repoName, filePath…
- Fetch Blog Post from GitHub (GitHub): get (file)
- Decode Base64 & Add Line Numbers (Code): runs custom JavaScript code
- QA Agent - Analyze Content (AI Agent): runs an AI agent, with model: QA Agent LLM, Fallback Chat Model
- Parse QA Issues JSON (Code): runs custom JavaScript code
- Has Issues? (If): checks a condition and branches into true / false
- Editor Agent - Generate Edit Ops (AI Agent): runs an AI agent, with model: Fallback Model, Editor Agent LLM
- Format Clean Report (Code): runs custom JavaScript code
- Parse Edit Operations JSON (Code): runs custom JavaScript code
- Save QA Report to GitHub Without Issues (GitHub): work with file
…plus 7 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Manual Trigger
n8n-nodes-base.manualTrigger - If
n8n-nodes-base.if - GitHub
n8n-nodes-base.github - Code
n8n-nodes-base.code - AI Agent
@n8n/n8n-nodes-langchain.agent - Google Gemini Chat Model
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - Groq Chat Model
@n8n/n8n-nodes-langchain.lmChatGroq - Edit Fields (Set)
n8n-nodes-base.set
From the author
Your personal editor that finds tone, grammar, and clarity issues in markdown, then fixes them and commits back to GitHub automatically. Stop manually proofreading markdown files. This workflow uses two AI agents to review your blog posts, generate precise…