See llms.txt for all machine-readable content.
Turn any n8n workflow JSON into a publication-ready, SEO-optimized markdown post for the n8n community. Upload your workflow file and let Google Gemini 2.5 Pro, guided by a LlamaIndex knowledge base of best practices, write the post for you.
Last updated: September 2026.
Time Savings: A detailed workflow post drops from over an hour of manual writing to under 2 minutes.
Cost Reduction: No separate AI content subscriptions or outsourced writing needed.
Error Prevention: A knowledge base of n8n's official guidelines keeps content quality and structure consistent, minimizing formatting errors.
| 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 |
Authorization and the value is Bearer YOUR_LLAMA_INDEX_API_KEY.| 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. |
Basic Adjustments:
ChatGoogleGemini node with another LLM node (e.g., OpenAI, Anthropic) to use a different provider.Advanced Enhancements:
Ghost, WordPress, or GitHub node to automatically publish the generated post.Form Trigger with a Read Binary Files node to process an entire folder of workflow JSON files in a single run.| 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. |
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. |
What do I upload?
Any exported n8n workflow JSON file, through the built-in web form.
Which AI writes the post?
Google Gemini 2.5 Pro, guided by a LlamaIndex knowledge base of content guidelines.
Where does the post go?
It is generated as workflow output, ready to copy-paste into the community platform.
Made by: khmuhtadin
Category: AI
Tags: AI, Content Generation, Google Gemini, LlamaIndex, Automation
Need custom workflows? Contact me
Connect with the creator:
Portfolio • Workflows • LinkedIn • Medium • Threads
Built with n8n. Need an assessment on your business? Feel free to reach out at https://khmuhtadin.com/consultation/