Generate RFx documents from Notion sourcing requests with Groq and Slack

Quick overview This workflow monitors a Notion sourcing pipeline for RFx requests, uses Groq-hosted LLMs to draft an RFx using context from similar past Notion projects, writes the formatted document back into Notion, and waits for a manager approval webhook to update the request status. How it works 1. Triggers every minute when a page changes in the Notion “Sourcing Pipeline” database. 2. Checks that the request Status equals “Generate RFx” and stops if it does not match. 3. Queries the Notion “Past Projects” database for the top three similar projects (same Category and Sourcing Type) sorted by Success Score. 4. Selects the correct RFx system prompt (RFI/RFP/RFQ) and sends the request requirements to Groq to generate the draft scope content. 5. Sends the scope plus historical evaluation and timeline context to Groq to generate evaluation/pricing tables and a project timeline with submission guidelines. 6. Combines the AI outputs, converts the Markdown into Notion block JSON, sets the Notion page status to “Pending Approval,” and appends the generated blocks to the original Notion page. 7. Waits for a manager decision via a resume webhook and updates the Notion page status to “Sent to Suppliers” when approved or “Needs Revisions” when rejected. Setup 1. Add Notion credentials and select your Notion “Sourcing Pipeline” and “Past Projects” databases, ensuring the properties used by the workflow exist (Status, Project Name, Category, Sourcing Type, Business Requirements, Success Score, evaluation criteria, and standard timelines). 2. Add a Groq API credential and confirm the selected Groq chat models are available in your Groq account. 3. Ensure your Status property includes the values “Generate RFx,” “Pending Approval,” “Sent to Suppliers,” and “Needs Revisions,” and update the workflow’s status strings if your labels differ. 4. Provide Notion API access for the HTTP request that appends blocks (Notion predefined credentials) and keep the Notion-Version header aligned with your workspace API compatibility. 5. Share the Wait node’s resume webhook URL with your approver system (for example, an interactive Slack message) so it can call back with an action value of approve or reject. Additional info How To Customize Nodes Adjust AI Prompts: Open the Prompt Library (RFI/RFP/RFQ) node to customize the exact headers, rules, and procurement terminology the AI agents use when drafting documents. Swap AI Models: Open any of the Groq Model nodes to select a different language model (e.g., switching from qwen3.8-27b to llama3-70b) based on your preference for speed versus complex reasoning. Customize Slack Messaging: Modify the text in the Slack: Request Approval or Notify Team (RFx Live) nodes to include different database properties, @mentions for specific executives, or specific channel IDs. Add‑ons PDF Export Generation: Add an HTML-to-PDF conversion node after the final approval to automatically generate a formal PDF version of the RFx for direct email to suppliers. Email Distribution: Connect an Outlook or Gmail node at the end of the "Approve" branch to automatically email the finalized RFx link to a predefined list of vendor contacts. Jira/Asana Ticketing: If revisions are needed (the Reject branch), add a node to automatically create a ticket in your engineering or legal team's project board to review the draft. Use Case Examples While tailored for procurement, this core architecture is highly adaptable. Similar use cases include: 1. Automated Request for Information (RFI): Translating rough business requirements into exploratory market research documents. 2. Structured Request for Proposal (RFP): Generating formal Scope of Work documents outlining core objectives, technical requirements, and vendor responsibilities. 3. Specific Request for Quotation (RFQ): Drafting exact specifications, Service Level Agreements (SLAs), and delivery compliance requirements for vendor pricing. 4. HR Job Description Drafting: Replacing the procurem