Generate procurement knowledge base articles with Groq, Gmail, and Google Sheets
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 29 nodes and runs on a schedule (every day at 09:00). Along the way it connects Groq Chat Model, Gmail and Google Sheets. It also calls jsonplaceholder.typicode.com over HTTP.
How it runs
Trigger: On a schedule (every day at 09:00).
- Retrieve Resolved Procurement Tickets (HTTP Request): calls jsonplaceholder.typicode.com
- Retrieve Procurement Chat Queries (HTTP Request): calls jsonplaceholder.typicode.com
- Combine Support Data Sources (Merge): merges the data from its input branches
- Normalize Ticket & Chat Data (Edit Fields (Set)): sets 4 fields: source, title, description…
- Cluster Similar Procurement Issues (Code): runs custom JavaScript code
- Generate Cluster Summaries (Code): runs custom JavaScript code
- Analyze Procurement Issue Patterns (AI Agent): runs an AI agent, with model: Groq Model – Issue Analysis
- Check Issue Analysis Output (If): checks a condition and branches into true / false
- Structure AI Analysis Results (Code): runs custom JavaScript code
- AI Analysis Failed Alert (Gmail): uses Gmail
…plus 13 more steps. See the full node list below.
Services it uses
HTTP calls to: jsonplaceholder.typicode.com
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 (11)
- Groq Chat Model
@n8n/n8n-nodes-langchain.lmChatGroq - If
n8n-nodes-base.if - AI Agent
@n8n/n8n-nodes-langchain.agent - Edit Fields (Set)
n8n-nodes-base.set - Gmail
n8n-nodes-base.gmail - No Operation, do nothing
n8n-nodes-base.noOp - HTTP Request
n8n-nodes-base.httpRequest - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Merge
n8n-nodes-base.merge - Code
n8n-nodes-base.code - Google Sheets
n8n-nodes-base.googleSheets
From the author
Quick overview This scheduled workflow pulls recent resolved procurement tickets and chat queries, clusters similar issues, and uses Groq LLMs to analyze patterns and draft Markdown knowledge base articles, then emails an approval request via Gmail and logs…