Optimize RFx supplier awards with Groq, Notion, and Slack alerts
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 13 nodes and runs on Notion events. Along the way it connects Notion, Groq Chat Model and Slack.
How it runs
Trigger: On Notion events.
- Filter: Run Simulation Status (If): checks a condition and branches into true / false
- Get: Vendor Bids DB Info (Notion): work with data source
- Fetch: Project Vendor Bids (Notion): get many (database page)
- Compute: Math & Scenario Optimization (Code): runs custom JavaScript code
- Set: Scenario Variables (Edit Fields (Set)): sets 5 fields: best_cost_scenario, lowest_risk_scenario, balanced_scenario…
- AI: Generate Executive Summary (Basic LLM Chain): sends a prompt to an LLM, with model: Groq LLM Model
- Format: Markdown to Notion Blocks (Code): runs custom JavaScript code
- API: Update Notion Project Page (HTTP Request): calls an HTTP API (PATCH)
- Fetch: Project Metadata (Notion): work with data source
- Filter: Deduplicate & Slack Format (Code): runs custom JavaScript code
…plus 1 more step. 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 (9)
- Notion Trigger
n8n-nodes-base.notionTrigger - If
n8n-nodes-base.if - Notion
n8n-nodes-base.notion - Code
n8n-nodes-base.code - Edit Fields (Set)
n8n-nodes-base.set - Basic LLM Chain
@n8n/n8n-nodes-langchain.chainLlm - Groq Chat Model
@n8n/n8n-nodes-langchain.lmChatGroq - HTTP Request
n8n-nodes-base.httpRequest - Slack
n8n-nodes-base.slack
From the author
Quick overview This workflow receives an RFx completion webhook, scores suppliers against cost, risk, lead time, and rating constraints, generates award scenarios, and uses Groq (LangChain agent) to produce a structured procurement recommendation, then stores…