Triage supplier capacity risk with Groq, Gmail, Slack, and Google Sheets
Ready for 3.0What this workflow does
This AI workflow has 22 nodes and runs on a schedule (every day at 09:00). Along the way it connects Groq Chat Model, Gmail, Slack and Google Sheets. It also calls mocki.io over HTTP.
How it runs
Trigger: On a schedule (every day at 09:00).
- Initialize Risk Config (Edit Fields (Set)): sets 3 fields: risk_threshold, min_fulfillment, max_delay
- Get Supplier Performance Data (HTTP Request): calls mocki.io
- Check Valid Orders (If): checks a condition and branches into true / false
- Normalize Supplier Data (Code): runs custom JavaScript code
- Compute Risk Metrics (Code): runs custom JavaScript code
- Classify Supplier Risk (AI) (AI Agent): runs an AI agent, with model: LLM Risk Engine
- Validate & Merge Risk Output (Code): runs custom JavaScript code
- Check High Risk Condition (If): checks a condition and branches into true / false
- Generate Mitigation Actions (AI Agent): runs an AI agent, with model: LLM Action Generator
- Get Backup Supplier Options (HTTP Request): calls mocki.io
…plus 9 more steps. See the full node list below.
Services it uses
HTTP calls to: mocki.io
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)
- Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if - Code
n8n-nodes-base.code - Groq Chat Model
@n8n/n8n-nodes-langchain.lmChatGroq - AI Agent
@n8n/n8n-nodes-langchain.agent - Merge
n8n-nodes-base.merge - Gmail
n8n-nodes-base.gmail - Slack
n8n-nodes-base.slack - Google Sheets
n8n-nodes-base.googleSheets - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
Quick overview This workflow runs daily to pull supplier performance data from an HTTP endpoint, calculate fulfillment and delay risk metrics, use Groq (Llama 3.3) to classify supplier risk and generate mitigation actions, then notify via Gmail and Slack and…