Yassin Zehar
Product Manager | Data-oriented | Agile certified (PSM I, PSPO I) | Paris
Categories
Templates by Yassin Zehar
Daily calendar summary notifications via Telegram from Google Calendar
Context: This workflow automatically sends you a daily message on Telegram summarizing all your meetings and events for the day, straight from your Google Calendar. For who ? Perfect for anyone who: Uses Google Calendar to manage their schedule. Wants Telegram reminders for daily events. Loves automation and productivity tools. Requirements: Telegram. Google account. Google Calendar. Steps: 🗒️ Use the sticky notes in the n8n canvas to: Add your Telegram and Google credentials. Execute and test the workflow. Check if you receive your daily summary on Telegram. You'll get this: Tutorial video: Watch the Youtube Tutorial video How does it work? ⏰ The trigger runs every day at 7AM. 📅 Your Google Calendar is checked. 🔢 If there are events or meetings, a number > 0 is returned. Otherwise, it's 0. 📝 A text message is generated with a summary of all your events, including all relevant details. ❌ If no events are found, a "no event" message is sent. About me : I’m Yassin a Project & Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin
By Yassin ZeharInstant Gmail notifications for Google Form submissions
Description Get a single Gmail notification immediately whenever someone submits your Google Forms. The workflow watches the Form-linked Google Sheets for new rows and sends a clean, readable email within about a minute—perfect for time-sensitive workflows. Context Stay responsive to urgent requests without inbox overload. Get notified immediately when new submissions arrive, with all key details in one clean email. Who is this for? Teams collecting support requests, project inputs, or approvals. Anyone who needs to respond quickly to new form submissions. Perfect for time-sensitive workflows. Requirements Google account A Google Forms linked to a Google Sheets (Responses → “Link to Sheet”) Gmail account connected to n8n (OAuth) Steps 🗒️ Use the sticky notes in the n8n canvas to: Create a Google Forms and link it to a Google Sheets. Credentials: Add/verify Google (Sheets) and Gmail credentials in n8n. Add Google Sheets Trigger node. Spreadsheet: your Form-linked sheet. Polling interval: every 1 minute (or adjust as needed). Send Gmail: Add Gmail node and set up recipient team inbox or on-call email. Test & Activate: Submit a sample form, wait 1 minute, confirm the email. Make sure the workflow is always activated You’ll get this: A Gmail message with key details (requester, summary, priority, link to the sheet), easy to scan and act on. Tutorial video Watch the Youtube Tutorial video How it works ⏰ Trigger: workflow runs every time you get a request from the form (trigger checks every minute) 📝 Prepare: Format the submission into a concise message. 📨 Notify: Sends one Gmail email per submission About me : I’m Yassin a Project & Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin
By Yassin ZeharAutomate meeting minutes distribution with Google Sheets and Gmail
Description This workflow sends a summary of your meeting minutes via Gmail, directly from the notes stored in your Google Sheet. Context Taking notes during meetings is important, but sharing them with the team can be time-consuming. This workflow makes it simple: just write down your meeting minutes in a Google Sheets, and n8n will automatically send them by email after each meeting. Who is this for? Perfect for anyone who: Uses Google Sheets to keep track of meeting notes. Wants to automatically share minutes with teammates or stakeholders. Values speed, productivity, and automation. Requirements Google account. Google Sheets (with your meeting minutes). You will need to setup the required columns first : Topic, Status, Owner, Next Step. Gmail. How it works ⏰ Trigger starts after a new row is added in your Google Sheet. 📑 The meeting minutes are retrieved from the sheet. 📨 Gmail automatically sends the minutes to the configured recipients. Steps 🗒️ Use the sticky notes in the n8n canvas to: Add your Google credentials (Sheets + Gmail). Define your sheet and recipient email addresses. Test the workflow to check if the minutes are sent. You’ll get this: An email containing your full meeting minutes, straight from your notes. Tutorial video Watch the Youtube Tutorial video About me : I’m Yassin a Project & Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin
By Yassin ZeharAutomated sprint reports from Jira to stakeholders via Gmail
Description Automated workflow that generates a Sprint Report from Jira and delivers it by Gmail. The flow fetches sprint issues from Jira, validates and normalizes the data, calculates metrics (tickets, story points, blockers, completion rate), generates an HTML report, and sends it by email. Context This template helps teams keep stakeholders updated automatically of the current sprint. Instead of manually compiling Jira data, the report is generated and sent on schedule (e.g., every Friday at 17:00). It’s production-friendly, reusable, and works across Jira projects. Target Users Scrum Masters and Agile Coaches who need sprint reports for retrospectives. Product Owners who want a weekly overview of sprint progress. Project Managers tracking Jira delivery KPIs. Engineering teams wanting automated status reporting without extra overhead. Technical Requirements Jira Cloud project + API email + API token + permission to read issues. Gmail credential for notifications. Workflow Steps Trigger – Schedule (e.g., Friday at 17:00). Edit Fields – Configure Jira base URL, project key, email recipients. Get Many Issues – Fetch sprint issues with JQL (project = <KEY> AND sprint in openSprints()). Validation & Normalization – Clean/validate fields (status, assignee, priority, story points, sprint info). Metrics Calculation – Aggregate KPIs (done, in progress, blockers, story points, completion %). HTML Report Generation – Build a styled email-friendly HTML summary + detailed table. Send Gmail – Deliver report to stakeholders. Key Features Automated Sprint Reports: No manual copy-paste. Metrics overview: Tickets done vs total, blockers, story points. Detailed table: Issue key, summary, status, assignee, priority, SP. Email delivery: HTML report with Jira links sent to stakeholders. Fully customizable: Adjust fields, KPIs, and recipients easily. Expected Output 📊 HTML Sprint Report with KPIs and issue table. ✅ Email delivered to stakeholders via Gmail. 🔗 Jira links embedded for easy navigation. How it works ⏰ Trigger – Runs on schedule (e.g., every Friday at 17:00). 🧾 Fetch Issues – JQL filters sprint tickets. 📊 Metrics – Done vs total, SP progress, blockers. 💻 Generate HTML – Clean, styled table and summary. ✉️ Notify – Send Gmail with full sprint report to stakeholders. Tutorial video: Watch the Youtube Tutorial video About me : I’m Yassin a Project & Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin
By Yassin ZeharJira ticket creation from Google Forms with sheet updates and email notifications
Description Automated workflow that creates Jira issues directly from Google Forms. The flow validates and normalizes the data, creates the Jira issue, writes the key back to the Google Sheet, and sends a Gmail notification. Context This template bridges lightweight Google Forms with enterprise Jira. It enables instant ticket creation while keeping Jira the single source of truth. The flow is idempotent (no duplicates) and production-friendly, with clean field normalization and safe mappings. Target Users Product / Ops teams running request portals on Google Forms Engineering managers who need quick Jira integration without custom UI Project managers who track intake in Google Sheets but want Jira as the system of record Orgs that want controlled ticket creation without exposing Jira directly Technical Requirements Jira Cloud project + API email + API token + “Create issues” permission Google Form + response Sheet Gmail credential for notifications Workflow Steps Trigger when a row is added Normalize Fields – Trim/clean text Create Jira Issue – POST to Jira REST; safe mappings Update Google Sheet – Match by Horodateur or rowNumber; write jirakey, issueurl, status, updated_at. Send Gmail – HTML email with key, title, link, priority, requester. Key Features Real-time (no polling): Forms → trigger→ n8n Idempotent updates using the Form timestamp (“Horodateur”) Clean normalization: summary/description/labels all standardized once Safe Jira mappings: priority via ID Notification: branded HTML email with all key fields Expected Output Google Form to create the issue Sheet updated with jirakey, issueurl, status, updated_at A valid Jira issue in the configured project Email sent to stakeholders / requester How it works ⏰ Trigger – As soon as a row is added, the workflow is triggered 🧱 Normalize – Clean summary/description/labels; pick reporter_email 🧾 Create – POST to /rest/api/3/issue, capture { id, key, self } 📗 Update – Write jirakey, issueurl, status, updated_at back to the Sheet ✉️ Notify – Send Gmail HTML confirmation to stakeholders/requester Tutorial video: Watch the Youtube Tutorial video About me : I'm Yassin, IT Project Manager, Agile & Data specialist. Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin
By Yassin ZeharConsolidate daily Google Form submissions into one Gmail recap
Description Receive one clean Gmail recap each day with all Google Forms submissions. The workflow reads your Form-linked Google Sheets, compiles every request submitted today, and sends a single, structured email at your chosen time—keeping your inbox tidy. Context Instead of receiving dozens of individual notifications, consolidate all daily form submissions into one organized email recap. Who is this for? Teams managing multiple incoming requests per day. Managers who want a daily summary instead of real-time alerts. Anyone who prefers to avoid notification spam. Requirements Google account with Forms & Sheets access Google Forms linked to Google Sheets Gmail account with n8n OAuth configured Steps 🗒️ Use the sticky notes in the n8n canvas to: Credentials : Add/verify Google (Sheets) and Gmail credentials in n8n. Schedule : Add a Cron/Schedule Trigger (default: 17:00/ 5PM, your local time). Add Google Sheets node → Read mode. Spreadsheet: select your Form-linked sheet. Build the Recap Body Use a Code (Function) node to assemble a simple HTML list or table from the filtered rows. Send Gmail : Add Gmail node and setup your team inbox / distribution list. For the body, paste the HTML body from step 5 and enable HTML. Test & Activate : Submit a few sample responses, run once, confirm the email looks right. Turn the workflow ON. You’ll get this: A structured Gmail message listing all daily submissions with: submitter name, timestamp, request details, and any custom fields from your form. Tutorial video Watch the Youtube Tutorial video How it works ⏰ Trigger: workflow runs once a day at your chosen time (default 5 PM). 📑 Collects all requests from that day in the Google Sheet. 📝 Compile: Generates a recap list/table. 📝 Generates a recap list with all submissions. 📨 Sends one Gmail email summarizing all requests of the day. About me : I’m Yassin a Project & Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin
By Yassin ZeharCreate Jira tickets from Streamlit forms with webhook & REST API
Description Automated workflow that creates Jira issues directly from Streamlit form submissions. Receives webhook data, validates and transforms it to Jira's API schema, creates the issue, and returns the ticket details to the frontend application. Context Bridges the gap between lightweight Streamlit prototypes and enterprise Jira workflows. Enables rapid ticket creation while maintaining Jira as the authoritative source of truth. Includes safety mechanisms to prevent duplicate submissions and malformed requests. Target Users Product Managers building internal request portals. Engineering Managers creating demo applications. Teams requiring instant Jira integration without complex UI development. Project Manager using Jira pour mangement and reporting. Organizations wanting controlled ticket creation without exposing Jira directly. Technical Requirements n8n instance (cloud or self-hosted) with webhook capabilities Jira Cloud project with API token and issue creation permissions Streamlit application configured to POST to n8n webhook endpoint Optional: Custom field IDs for Story Points (typically customfield_10016) Workflow Steps Webhook Trigger - Receives POST from Streamlit with ticket payload. Deduplication Guard - Filters out ping requests and rapid duplicate submissions. Data Validation - Ensures required fields are present and properly formatted. Schema Transformation - Maps Streamlit fields to Jira API structure. Jira API Call - Creates issue via REST API with error handling. Response Formation - Returns success status with issue key and URL. Key Features Duplicate submission prevention. Rich text description formatting for Jira. Configurable priority and issue type mapping. Story points integration for agile workflows. Comprehensive error handling and logging. Clean JSON response for frontend feedback. Validation Testing Ping/test requests are ignored without creating issues. First submission creates Jira ticket with proper formatting. Rapid resubmission is blocked to prevent duplicates. All field types (priority, labels, due dates, story points) map correctly. Error responses are handled gracefully. Expected Output Valid Jira issue created in specified project JSON response: {ok: true, jiraKey: "PROJ-123", url: "https://domain.atlassian.net/browse/PROJ-123"} No orphaned or duplicate tickets. Audit trail in n8n execution logs. Implementation Notes Jira Cloud requires accountId for assignee (not username). Date format must be YYYY-MM-DD for due dates. Story Points field ID varies by Jira configuration. Enable response output in HTTP node for debugging. Consider rate limiting for high-volume scenarios. Tutorial video: Watch the Youtube Tutorial video How it works ⏰ Trigger: Webhook fires when the app submits. 🧹 Guard: Ignore pings/invalid, deduplicate rapid repeats. 🧱 Prepare: Normalize to Jira’s field model (incl. Atlassian doc description). 🧾 Create: POST to /rest/api/3/issue and capture the key. 🔁 Respond: Send { ok, jiraKey, url } back to Streamlit for instant UI feedback. About me : I’m Yassin a Project & Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin
By Yassin ZeharAutomate B2B SaaS renewal risk management with CRM, support & usage data
Description This workflow is designed for B2B/SaaS teams who want to secure renewals before it’s too late. It runs every day, identifies all accounts whose licenses are up for renewal in J–30, enriches them with CRM, product usage and support data, computes an internal churn risk level, and then triggers the appropriate playbook: HIGH risk → full escalation (tasks, alerts, emails) MEDIUM risk → proactive follow-up by Customer Success LOW risk → light renewal touchpoint / monitoring Everything is logged into a database table so that you can build dashboards, run analysis, or plug additional automations on top. --- How it works Daily detection (J–30 renewals) A scheduled trigger runs every morning and queries your database (Postgres / Supabase) to fetch all active subscriptions expiring in 30 days. Each row includes the account identifier, name, renewal date and basic commercial data. Data enrichment across tools For each account, the workflow calls several business systems to collect context: HubSpot → engagement history Salesforce → account profile and segment Pipedrive → deal activities and associated products Analytics API → product feature usage and activity trends Zendesk → recent support tickets and potential friction signals All of this is merged into a single, unified item. Churn scoring & routing An internal scoring step evaluates the risk for each account based on multiple signals (engagement, usage, support, timing). The workflow then categorizes each account into one of three risk levels: HIGH – strong churn signals → needs immediate attention MEDIUM – some warning signs → needs proactive follow-up LOW – looks healthy → light renewal reminder A Switch node routes each account to the relevant playbook. Automated playbooks 🔴 HIGH risk Create a Trello card on a dedicated “High-Risk Renewals” board/list Create a Jira ticket for the CS / AM team Send a Slack alert in a designated channel Send a detailed email to the CSM and/or account manager 🟠 MEDIUM risk Create a Trello card in a “Renewals – Follow-up” list Send a contextual email to the CSM to recommend a proactive check-in 🟢 LOW risk Send a soft renewal email / internal note to keep the account on the radar Logging & daily reporting For every processed account, the workflow prepares a structured log record (account, renewal date, risk level, basic context). A Postgres node is used to insert the data into a churn_logs table. At the end of each run, all processed accounts are aggregated and a daily summary email is sent (for example to the Customer Success leadership team), listing the renewals and their risk levels. --- Requirements Database A table named churn_logs (or equivalent) to store workflow decisions and history. Example fields: accountid, accountname, enddate, riskScore, riskLevel, playbook, trellolink, jira_link, timestamp. External APIs HubSpot (engagement data) Salesforce (account profile) Pipedrive (deals & products) Zendesk (support tickets) Optional: product analytics API for usage metrics Communication & task tools Gmail (emails to CSM / AM / summary recipients) Slack (alert channel for high-risk cases) Trello (task creation for CS follow-up) Jira (escalation tickets for high-risk renewals) Configuration variables Thresholds are configured in the Init config & thresholds node: daysbeforerenewal churnthresholdhigh churnthresholdmedium These parameters let you adapt the detection window and risk sensitivity to your own business rules. --- Typical use cases Customer Success teams who want a daily churn watchlist without exporting spreadsheets. RevOps teams looking to standardize renewal playbooks across tools. SaaS companies who need to prioritize renewals based on real risk signals rather than gut feeling. Product-led organizations that want to combine usage data + CRM + support into one automated process. Tutorial video Watch the Youtube Tutorial video About me : I’m Yassin a Project & Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin
By Yassin ZeharTask escalation system with Google Sheets, Gmail, Telegram & Jira automation
Description This workflow sends an instant email alert when a task in a Google Sheet is marked as Urgent, and then sends a Telegram reminder notification after 2 hours if the task still hasn’t been updated. Then a Jira ticket is created so the task enters in the formal workflow and another Telegram message is sent with the details of the issue created. It helps teams avoid missed deadlines and ensures urgent tasks get attention — without requiring anyone to refresh or monitor the sheet manually. Context In shared task lists, urgent items can be overlooked if team members aren't actively checking the spreadsheet. This workflow solves that by: Sending an email as soon as a task becomes Urgent Waiting 2 hours Checking if the task is still open Sending a Telegram reminder only if action has not been taken Creating a Jira issue Sending a Telegram message with the details of the issue created This prevents both silence and spam, creating a smart and reliable alert system. Target Users Project Managers using Google Sheets Team leads managing shared task boards Remote teams needing lightweight coordination Anyone who wants escalation notifications without complex systems Technical Requirements Google Sheets credential Gmail credential Telegram Bot + Chat ID Google Sheet with a column named Priority Jira credential Workflow Steps Trigger: Google Sheets Trigger (on update in the “Priority” column) IF Node – Checks if Priority = Urgent Send Email – Sends alert email with task name, owner, status, deadline Mark Notified = Yes in the sheet Wait 2 hours IF Status is still not resolved Send Telegram reminder create an Issue on Jira based on the information provided Send Telegram message with the details of the ticket Key Features Real-time alerts on critical tasks Simple logic (no code required) Custom email body with dynamic fields Works on any Google Sheet with a “Priority” column Telegram notification ensures the task doesn’t get forgotten Expected Output Personalized email alert when a task is marked as "Urgent" Email includes task info: title, owner, deadline, status, next step Telegram message after 2 hours if the task is still open Automatic creation of a Jira issue with the higgest priority Telegram message to notify about the new Jira ticket How it works Trigger: Watches for “Priority” updates 🔍 Check: If Priority = Urgent AND Notified is empty 📧 Email: Sends a personalized alert ✏️ Sheet Update: Marks the task as already notified ⏳ Wait: 2-hour delay 🤖 Check Again: If Status hasn’t changed → send Telegram reminder, create Jira ticket and send the details. Tutorial video: Watch the Youtube Tutorial video About me : I’m Yassin a Project & Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin
By Yassin ZeharSend one-time email alerts for urgent tasks with Google Sheets and Gmail
Description This workflow sends a personalized email when a task in a Google Sheet is marked as Urgent, but only once per task. It prevents duplicate notifications by updating the sheet after the email is sent. Ideal for collaborative task tracking where multiple people edit the same spreadsheet. Context When working with shared task lists in Google Sheets, it’s easy to miss critical updates — or worse, trigger multiple alerts for the same task. This workflow ensures that each "Urgent" task only sends one email notification, and then marks it as “Notified” to avoid duplicates. Target Users Project Managers using Google Sheets Operations or support teams managing collaborative task boards Anyone who needs alert automation with built-in anti-spam logic Technical Requirements Google Sheets account with edit access Gmail account for sending notifications Google Sheet with columns: Priority Notified Task Owner Deadline Status Next Step Workflow Steps Trigger: Watches for changes in Google Sheets (e.g., edits to the "Priority" column) IF Node – Checks that: Priority = Urgent Notified is empty row exists (required for update) Send Email: Sends a personalized message with task details Update Row: Writes “Yes” in the Notified column to avoid duplicate alerts Setup Instructions To set up this workflow: Connect your Google Sheets and Gmail credentials in n8n. Copy the spreadsheet structure or use your own Import the workflow, select your Sheet (and the column to check if you use a different Google Sheets template), and test by marking a task as “Urgent”. Check that an email is sent and the “Notified” column updates to “Yes”.- Key Features ✅ One email per urgent task — prevents duplicates 📧 Dynamic email content with task info 🧠 Built-in anti-spam logic 📋 Simple to configure and reuse 💬 Customizable for any team’s needs Expected Output An email alert is sent only once per task marked as Urgent The Notified field is updated in the Google Sheet A clean and scalable alert system with no duplicates Tutorial video: Watch the Youtube Tutorial video About me : I’m Yassin a Project & Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin
By Yassin ZeharAutomated product health monitor with anomaly detection & AI root cause analysis
Description This workflow transforms raw SaaS metrics into a fully automated Product Health Monitoring & Incident Management system. It checks key revenue and usage metrics every day (such as churn MRR and feature adoption), detects anomalies using a statistical baseline, and automatically creates structured incidents when something unusual happens. When an anomaly is found, the workflow logs it into a central incident database, alerts the product team on Slack and by email, enriches the incident with context and AI-generated root-cause analysis, and produces a daily health report for leadership. It helps teams move from passive dashboard monitoring to a proactive, automated system that surfaces real issues with clear explanations and recommended next steps. Context Most SaaS teams struggle with consistent product health monitoring: Metrics live in dashboards that people rarely check proactively Spikes in churn or drops in usage are noticed days later There is no unified system to track, investigate, and report on incidents Post-mortems rely on memory rather than structured data Leadership often receives anecdotal updates instead of reliable daily reporting This workflow solves that by: Tracking core health metrics daily (revenue and usage) Detecting anomalies based on recent baselines, not arbitrary thresholds Logging all incidents in a consistent format Notifying teams only when action is needed Generating automated root-cause insights using AI + underlying database context Producing a daily “Product Health Report” for decision-makers The result: Faster detection, clearer understanding, and better communication across product, growth, and leadership teams. Target Users This template is ideal for: Product Managers & Product Owners SaaS founders and early-stage teams Growth, Analytics, and Revenue Ops teams PMO / Operations teams managing product performance Any organization wanting a lightweight incident monitoring system without building internal tooling Technical Requirements You will need: A Postgres / Supabase database containing your product metrics Slack credentials for alerts Gmail credentials for email notifications (Optional) Notion credentials for incident documentation and daily reports An OpenAI / Anthropic API key for AI-based root cause analysis Workflow Steps The workflow is structured into four main sections: 1) Daily Revenue Health Runs once per day, retrieves recent revenue metrics, identifies unusual spikes in churn MRR, and creates incidents when needed. If an anomaly is detected, a Slack alert and email notification are sent immediately. 2) Daily Usage Health Monitors feature usage metrics to detect sudden drops in adoption or engagement. Incidents are logged with severity, context, and alerts to the product team. 3) Root Cause & Summary For every open incident, the workflow: Collects additional context from the database (e.g., churn by country or plan) Uses AI to generate a clear root cause hypothesis and suggested next steps Sends a summarized report to Slack and email Updates the incident status accordingly 4) Daily Product Health Report Every morning, the workflow compiles all incidents from the previous day into: A daily summary email for leadership A Notion page for documentation and historical tracking This ensures stakeholders have clear visibility into product performance trends. Key Features Automated anomaly detection across revenue and usage metrics Centralized incident logging with metadata and raw context Severity scoring based on deviation from historical baselines Slack and email alerts for fast response AI-generated root cause analysis with recommended actions Daily product health reporting for leadership and PM teams Optional Notion integration for incident documentation System logging for observability and auditability Fully modular: you can add more metrics, alert channels, or analysis steps easily Expected Output When running, the workflow will generate: Structured incident records in your database Slack alerts for revenue or usage anomalies Email notifications with severity, baseline vs actual, and context AI-generated root cause summaries A daily health report summarizing all incidents (Optional) Notion pages for both incidents and daily reports System logs recording successful executions Tutorial video: Watch the Youtube Tutorial video About me I’m Yassin a Project & Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin
By Yassin ZeharTriage 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
By Yassin Zehar