Triage product UAT feedback with OpenAI, Notion, Slack and Gmail
Description
Automatically triage Product UAT feedback with AI, deduplicate it against your existing Notion backlog, create/update the right Notion item, and close the loop with the tester (Slack or email).
This workflow standardizes incoming UAT feedback, runs AI classification (type, severity, summary, suggested title, confidence), searches Notion to prevent duplicates, and upserts the roadmap entry for product review. It then confirms receipt to the tester and returns a structured webhook response.
Context
Feature requests often arrive unstructured and get lost across channels. Product teams waste time re-triaging the same ideas, creating duplicates, and manually confirming receipt.
This workflow ensures:
-
Faster feature request triage
-
Fewer duplicates in your roadmap/backlog
-
Consistent structure for every feedback item
-
Automatic tester acknowledgement
-
Full traceability via webhook response
Who is this for?
-
Product Managers running UAT or beta programs
-
Product Ops teams managing a roadmap backlog
-
Teams collecting feature requests via forms, Slack, or internal tools
-
Anyone who wants AI speed with clean backlog hygiene
Requirements
-
Webhook trigger (form / Slack / internal tool)
-
OpenAI account (AI triage)
-
Notion account (roadmap/backlog database)
-
Slack and/or Gmail (tester notification)
How it works
-
Trigger: feedback received via webhook
-
Normalize & Clean: standardizes fields and cleans message
-
AI Triage: returns structured JSON (type, severity, title, confidence…)
-
Notion Dedupe & Upsert: search by suggested title → update if found, else create
-
Closed Loop: notify tester (Slack or email) + webhook response payload
What you get
-
One workflow to capture and structure feature requests
-
Clean Notion backlog without duplicates
-
Automatic tester confirmation
-
Structured output for downstream automation
About me :
I’m Yassin a Product Manager Scaling tech products with a data-driven mindset. 📬 Feel free to connect with me on Linkedin
n8n Workflow: Triage Product UAT Feedback with OpenAI, Notion, Slack, and Gmail
This n8n workflow streamlines the process of triaging User Acceptance Testing (UAT) feedback. It acts as a central hub to receive feedback, intelligently categorize it using AI, organize it in Notion, notify relevant teams on Slack, and send confirmation emails.
What it does
This workflow automates the following steps:
- Receives Feedback: Listens for incoming UAT feedback via a webhook. This could be triggered by a form submission, an internal tool, or any system capable of sending HTTP requests.
- Processes with AI (OpenAI): Sends the received feedback to OpenAI to analyze and categorize it. This step likely extracts key information, identifies sentiment, or assigns a priority/category.
- Organizes in Notion: Creates a new item in a specified Notion database with the processed feedback, ensuring all UAT feedback is centrally logged and trackable.
- Notifies on Slack: Posts a notification to a designated Slack channel, alerting the relevant team about new UAT feedback and its AI-generated summary.
- Confirms via Email: Sends a confirmation email using Gmail, potentially to the feedback submitter or an internal team, acknowledging receipt of the feedback.
- Responds to Webhook: Sends a success response back to the originating webhook, confirming that the feedback has been received and processed.
Prerequisites/Requirements
To use this workflow, you will need the following:
- n8n Instance: A running n8n instance.
- Webhook Endpoint: A system configured to send UAT feedback to the n8n webhook URL.
- OpenAI API Key: Credentials for OpenAI to allow the workflow to process text with AI models.
- Notion Account & Database: A Notion account with a pre-configured database where UAT feedback will be stored. You'll need an integration token and the database ID.
- Slack Account & Channel: A Slack account and a channel where notifications should be posted. You'll need a Slack API token or webhook URL.
- Gmail Account: A Gmail account configured as a credential in n8n for sending emails.
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Webhook:
- Locate the "Webhook" trigger node.
- Copy the "Webhook URL" and configure your external system to send UAT feedback (e.g., as a POST request) to this URL.
- Set up Credentials:
- For the "OpenAI" node, configure your OpenAI API Key credential.
- For the "Notion" node, configure your Notion API Key credential (integration token) and specify the database ID.
- For the "Slack" node, configure your Slack credential (e.g., OAuth or API token) and specify the channel ID.
- For the "Gmail" node, configure your Google OAuth credential.
- Customize Nodes:
- Edit Fields (Set): Review and adjust the data transformation in this node to match the expected input from your webhook and the desired output for subsequent nodes.
- OpenAI: Configure the specific OpenAI model and prompt you want to use for feedback analysis. Map the incoming feedback data to the prompt.
- Notion: Map the data from the previous nodes (including OpenAI's output) to the properties of your Notion database.
- Slack: Customize the message content for the Slack notification, including details from the feedback and AI analysis.
- Gmail: Configure the recipient, subject, and body of the confirmation email.
- Activate the Workflow: Once all credentials and configurations are set, activate the workflow.
Now, whenever new UAT feedback is sent to the webhook, this workflow will automatically process, organize, notify, and confirm it.
Related Templates
Automate Google Ads copy optimization with Channable feed and Relevance AI
🧠 Google Ads Monthly Performance Optimization (Channable + Google Ads + Relevance AI) 🚀 Overview This workflow automatically analyzes your Google Ads performance every month, identifies top-performing themes and categories, and regenerates optimized ad copy using Relevance AI — powered by insights from your Channable product feed. It then saves the improved ads to Google Sheets for review and sends a detailed performance report to your Slack workspace. Ideal for marketing teams who want to automate ad optimization at scale with zero manual intervention. --- 🔗 Integrations Used Google Ads → Fetch campaign and ad performance metrics using GAQL. Relevance AI → Analyze performance data and regenerate ad copy using AI agents and tools. Channable → Pull updated product feeds for ad refresh cycles. Google Sheets → Save optimized ad copy for review and documentation. Slack → Send a 30-day performance report to your marketing team. --- 🧩 Workflow Summary | Step | Node | Description | | ---- | --------------------------------------------------- | --------------------------------------------------------------------------- | | 1 | Monthly Schedule Trigger | Runs automatically on the 1st of each month to review last 30 days of data. | | 2 | Get Google Ads Performance Data | Fetches ad metrics via GAQL query (impressions, clicks, CTR, etc.). | | 3 | Calculate Performance Metrics | Groups results by ad group and theme to find top/bottom performers. | | 4 | AI Performance Analysis (Relevance AI) | Generates human-readable insights and improvement suggestions. | | 5 | Update Knowledge Base (Relevance AI) | Saves new insights for future ad copy training. | | 6 | Get Updated Product Feed (Channable) | Retrieves the latest catalog items for ad regeneration. | | 7 | Split Into Batches | Splits the feed into groups of 50 to avoid API rate limits. | | 8 | Regenerate Ad Copy with Insights (Relevance AI) | Rewrites ad copy with the latest product and performance data. | | 9 | Save Optimized Ads to Sheets | Writes output to your “Optimized Ads” Google Sheet. | | 10 | Generate Performance Report | Summarizes the AI analysis, CTR trends, and key insights. | | 11 | Email Performance Report (Slack) | Sends report directly to your Slack channel/team. | --- 🧰 Requirements Before running the workflow, make sure you have: A Google Ads account with API access and OAuth2 credentials. A Relevance AI project (with one Agent and one Tool setup). A Channable account with API key and project feed. A Google Sheets document for saving results. A Slack webhook URL for sending performance summaries. --- ⚙️ Environment Variables Add these environment variables to your n8n instance (via .env or UI): | Variable | Description | | -------------------------------- | ------------------------------------------------------------------- | | GOOGLEADSAPI_VERSION | API version (e.g., v17). | | GOOGLEADSCUSTOMER_ID | Your Google Ads customer ID. | | RELEVANCEAIAPI_URL | Base Relevance AI API URL (e.g., https://api.relevanceai.com/v1). | | RELEVANCEAGENTPERFORMANCE_ID | ID of your Relevance AI Agent for performance analysis. | | RELEVANCEKNOWLEDGESOURCE_ID | Knowledge base or dataset ID used to store insights. | | RELEVANCETOOLADCOPYID | Relevance AI tool ID for generating ad copy. | | CHANNABLEAPIURL | Channable API endpoint (e.g., https://api.channable.com/v1). | | CHANNABLECOMPANYID | Your Channable company ID. | | CHANNABLEPROJECTID | Your Channable project ID. | | FEED_ID | The feed ID for product data. | | GOOGLESHEETID | ID of your Google Sheet to store optimized ads. | | SLACKWEBHOOKURL | Slack Incoming Webhook URL for sending reports. | --- 🔐 Credentials Setup in n8n | Credential | Type | Usage | | ----------------------------------------------- | ------- | --------------------------------------------------- | | Google Ads OAuth2 API | OAuth2 | Authenticates your Ads API queries. | | HTTP Header Auth (Relevance AI & Channable) | Header | Uses your API key as Authorization: Bearer <key>. | | Google Sheets OAuth2 API | OAuth2 | Writes optimized ads to Sheets. | | Slack Webhook | Webhook | Sends monthly reports to your team channel. | --- 🧠 Example AI Insight Output json { "insights": [ "Ad groups using 'vegan' and 'organic' messaging achieved +23% CTR.", "'Budget' keyword ads underperformed (-15% CTR).", "Campaigns featuring 'new' or 'bestseller' tags showed higher conversion rates." ], "recommendations": [ "Increase ad spend for top-performing 'vegan' and 'premium' categories.", "Revise copy for 'budget' and 'sale' ads with low CTR." ] } --- 📊 Output Example (Google Sheet) | Product | Category | Old Headline | New Headline | CTR Change | Theme | | ------------------- | -------- | ------------------------ | -------------------------------------------- | ---------- | ------- | | Organic Protein Bar | Snacks | “Healthy Energy Anytime” | “Organic Protein Bar — 100% Natural Fuel” | +12% | Organic | | Eco Face Cream | Skincare | “Gentle Hydration” | “Vegan Face Cream — Clean, Natural Moisture” | +17% | Vegan | --- 📤 Automation Flow Run Automatically on the first of every month (cron: 0 0 1 ). Fetch Ads Data → Analyze & Learn → Generate New Ads → Save & Notify. Every iteration updates the AI’s knowledge base — improving your campaigns progressively. --- ⚡ Scalability The flow is batch-optimized (50 items per request). Works for large ad accounts with up to 10,000 ad records. AI analysis & regeneration steps are asynchronous-safe (timeouts extended). Perfect for agencies managing multiple ad accounts — simply duplicate and update the environment variables per client. --- 🧩 Best Use Cases Monthly ad creative optimization for eCommerce stores. Marketing automation for Google Ads campaign scaling. Continuous learning ad systems powered by Relevance AI insights. Agencies automating ad copy refresh cycles across clients. --- 💬 Slack Report Example 30-Day Performance Optimization Report Date: 2025-10-01 Analysis Period: Last 30 days Ads Analyzed: 842 Top Performing Themes Vegan: 5.2% CTR (34 ads) Premium: 4.9% CTR (28 ads) Underperforming Themes Budget: 1.8% CTR (12 ads) AI Insights “Vegan” and “Premium” themes outperform baseline by +22% CTR. “Budget” ads underperform due to lack of value framing. Next Optimization Cycle: 2025-11-01 --- 🛠️ Maintenance Tips Update your GAQL query occasionally to include new metrics or segments. Refresh Relevance AI tokens every 90 days (if required). Review generated ads in Google Sheets before pushing them live. Test webhook and OAuth connections after major n8n updates. --- 🧩 Import Instructions Open n8n → Workflows → Import from File / JSON. Paste this workflow JSON or upload it. Add all required environment variables and credentials. Execute the first run manually to validate connections. Once verified, enable scheduling for automatic monthly runs. --- 🧾 Credits Developed for AI-driven marketing teams leveraging Google Ads, Channable, and Relevance AI to achieve continuous ad improvement — fully automated via n8n.
GPT-4.1-mini Powered Invoice Processing from Gmail to Google Sheets with Slack
AI-Powered Invoice Processing from Gmail to Google Sheets with Slack Approval This workflow completely automates your invoice processing pipeline. It triggers when a new invoice email arrives in Gmail, uses AI to extract key data from the PDF attachment, logs it in a Google Sheet, and sends a request to Slack with simple links for one-click approval or rejection. Who's it for? This template is perfect for small business owners, finance teams, freelancers, and anyone looking to eliminate the manual work of processing invoices. It saves hours of data entry, reduces human error, and streamlines the approval process. How it works Trigger: The workflow starts when an email with a specific subject (e.g., "Invoice") arrives in Gmail. Extraction: It automatically downloads the first PDF attachment from the email and extracts all its text content. AI Processing: The extracted text is sent to an AI model, which intelligently identifies and pulls out key details: invoice number, issue date, company name, total amount, and due date. Logging: This structured data is appended as a new row in your Google Sheet. The status is automatically set to "pending". The full, raw text from the PDF is also saved for easy verification. Approval Request: A formatted message is sent to a designated Slack channel. This message includes the key invoice details and two unique links: one to approve and one to reject the invoice. Handle Response: When a user clicks either the "Approve" or "Reject" link, the corresponding Webhook in the workflow is triggered. Update Sheet: The workflow finds the correct row in the Google Sheet using the invoice number and updates its status to "approved" or "rejected". Confirmation: A final confirmation message is sent to the Slack channel, closing the loop and informing the team of the action taken. How to set up Credentials: Add your credentials for Gmail, OpenAI, Google Sheets, and Slack in the designated nodes. Gmail Trigger: In the "1. New Invoice Email Received" node, change the search query q from "incoice" to the keyword you use for invoice emails (e.g., "invoice"). Google Sheets: In the three Google Sheets nodes ("6. Log Invoice...", "9a. Update Status to Approved", and "9b. Update Status to Rejected"), enter your Google Sheet ID and the name of the sheet. Slack: In the three Slack nodes ("7. Send Approval Request...", "10a. Send Approval Confirmation", and "10b. Send Rejection Confirmation"), enter your Slack Channel ID. Webhook URLs: First, activate the workflow using the toggle in the top-right corner. Open the "Webhook (Approve)" node, go to the Production URL tab, and copy the URL. Paste this URL into the "7. Send Approval Request to Slack" node, replacing the https://YOURWEBHOOKBASE_URL/webhook/approval part of the approval link. Repeat this process for the "Webhook (Reject)" node and the rejection link. Activate Workflow: Ensure the workflow is active for the Webhooks to work continuously. How to customize AI Prompt: You can modify the prompt in the "5. Extract Invoice Data with AI" node to extract different or additional fields to match your specific invoice formats. Slack Messages: Feel free to customize the text in all three Slack nodes to better fit your team's tone and communication style.
Automate X-ray analysis with VLM Orion and distribute to Gmail, Telegram & Drive
📌 Overview This workflow provides an automated pipeline for processing medical X-ray images using VLM Run (model: vlmrun-orion-1:auto), and distributing the AI-generated analysis to multiple channels—email, Telegram, and Google Drive. --- ⚙️ How It Works Upload X-Ray Image A Form Trigger allows the user to upload an X-ray file. Once the image is submitted, the workflow immediately starts processing. --- Automated X-Ray Analysis The uploaded X-ray image is sent to VLM Run (vlmrun-orion-1:auto) via an OpenAI-compatible endpoint. The model returns: A text-based interpretation or description A disease-highlighted output image (if detected) A URL reference pointing to the annotated result image stored in Google Cloud --- Extract Artifact From artifact reference, download file using artifact node. --- Generate Report File The Convert to File node transforms the analysis text into a shareable .txt report. This file is used both for email and Drive storage. --- Send Notifications to Gmail & Telegram The workflow automatically: 📧 Emails the doctor (or configured staff email): The diagnostic description The generated report file The annotated X-ray image 📨 Sends a Telegram message containing: The same report The disease-highlighted X-ray image This ensures instant notification and cross-platform availability. --- Upload to Google Drive The final step uses Google Drive OAuth2 to store: The report file The annotated medical image These files are uploaded to a designated Drive folder for archiving and future reference. --- 🧩 Key Features ✔️ Automated X-ray processing using VLM Run ✔️ Structured extraction of annotated medical images ✔️ Multi-channel notification (Email + Telegram) ✔️ Centralized archive via Google Drive ✔️ Zero manual intervention after upload ✔️ Works with OpenAI-compatible VLM endpoints --- 🔧 Requirements VLM Run API Credentials Required to call vlm-agent-1 for image analysis. Gmail OAuth2 Credentials Needed to automatically email the diagnostic report. Telegram Bot Token Sends analysis results to a Telegram chat or group. Google Drive OAuth2 Stores reports and annotated images in Google Drive. --- 📎 Notes This workflow automates image handling and communication. All AI-generated content must be reviewed by a qualified medical professional before any clinical use.