HumationHuman + Automation
Back to Catalog

Generate sprint review summaries from transcripts with OpenAI and Google Sheets

ArkadiuszArkadiusz
92 views
2/3/2026
ZendeskWebhookIntegrationTicket ManagementCRM
Official Page

What this workflow does

This template automates the entire process of documenting Sprint Reviews in Scrum:

  1. Input Collection – Through a friendly form, users upload the transcript file (meeting notes, sprint review transcript, or VTT captions) and specify the sprint name and domain.
  2. Transcript Parsing – A Code node formats the transcript into clean [HH:MM:SS] Speaker: text lines, supporting VTT, Zoom, or custom timestamp formats used in Scrum events.
  3. AI-Driven Summary – The AI Agent (LangChain + OpenAI) produces a well-structured AI summarization in Markdown, including:
    • A 3–5 bullet Executive Summary of sprint review highlights
    • A Presentation Recap table (Timestamp | Presenter | Topics)
    • A list of Action Items with owners (if recognizable from the transcript)
  4. Preview – The summary renders as a styled card with custom CSS for easy readability in n8n.
  5. Archive – Automatically appends a record to Google Sheets, saving the date, domain, sprint, transcript file name, and the AI-generated sprint review summary.

Why it’s useful

  • Zero manual summarizing – AI extracts key insights from transcript files into Markdown you can instantly share with your Scrum team and stakeholders.
  • Easy setup – drag-and-drop import, plus form-based input for non-technical users during sprint reviews.
  • Centralized tracking – all past sprint summaries live in one spreadsheet for retrospectives, audits, and continuous improvement.
  • Flexible and extendable – you can switch to Airtable, Slack, or Notion, or refine the summary template to match your Scrum workflow.

Ideal for

  • Scrum Masters wanting quick sprint review summaries for stakeholders
  • Agile Coaches analyzing sprint review transcripts, presentation patterns, and follow-up tasks
  • Product Owners keeping a searchable log of sprint outcomes and action items

Prerequisites / Credentials

  • OpenAI API Key — required for the AI Agent node (or any other Agent for summarization)
  • Google Sheets OAuth2 credentials — required for saving sprint review data to Sheets
  • (Optional) Ensure LangChain / AI Agent nodes are installed in your n8n instance

How to Use This Template

  1. Import the workflow JSON into your n8n instance.
  2. Set up credentials:
    • For the OpenAI LLM node, provide your OpenAI API key
    • In Google Sheets, configure OAuth2 and specify your spreadsheet ID (replace YOUR_SHEET_ID)
  3. Create a new sheet with the following columns:
    • Date
    • Domain
    • Sprint name
    • Content
    • VTT file
    • Transcript
  4. Enable and run the workflow.
  5. Fill out the form: upload transcript file, enter sprint & domain, click Create Summary.
  6. View the AI-generated Markdown sprint review summary in the preview card.
  7. Verify the new entry appears in your Google Sheet with all sprint details.

Generate Sprint Review Summaries from Transcripts with OpenAI and Google Sheets

This n8n workflow automates the process of generating concise sprint review summaries from raw meeting transcripts using OpenAI's language model and storing them in Google Sheets. It provides a user-friendly form to input the transcript and other relevant details.

What it does

  1. Triggers on Form Submission: The workflow starts when a user submits data through an n8n form.
  2. Collects Input: It captures the sprint name, date, and the full meeting transcript provided by the user.
  3. Generates Summary with AI: It sends the transcript to an OpenAI Chat Model via an AI Agent, prompting it to generate a concise summary suitable for a sprint review.
  4. Adds to Google Sheets: The generated summary, along with the sprint name and date, is then appended as a new row in a specified Google Sheet.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • OpenAI API Key: An API key for OpenAI to use their Chat Model. This should be configured as an n8n credential.
  • Google Account: A Google account with access to Google Sheets. This should be configured as an n8n credential with permissions to write to spreadsheets.
  • Google Sheet: An existing Google Sheet where the summaries will be stored. You'll need its ID and the sheet name.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON workflow.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the three dots next to the workflow name and select "Import from JSON".
    • Paste the JSON and import the workflow.
  2. Configure Credentials:
    • OpenAI Chat Model (Node ID: 1153): Select your OpenAI API credential. If you don't have one, create a new "OpenAI API" credential and enter your API key.
    • Google Sheets (Node ID: 18): Select your Google Sheets credential. If you don't have one, create a new "Google Sheets API" credential (OAuth2 recommended) and grant it access to your Google Sheets.
  3. Configure Google Sheets Node (Node ID: 18):
    • In the "Google Sheets" node, set the "Spreadsheet ID" to the ID of your target Google Sheet.
    • Set the "Sheet Name" to the specific sheet within your spreadsheet where you want to add the summaries (e.g., "Sheet1").
  4. Configure the Form Trigger (Node ID: 1225):
    • Activate the workflow.
    • The "On form submission" node will provide a unique URL. Share this URL with users who need to submit sprint review transcripts.
  5. Test the Workflow:
    • Open the form URL provided by the "On form submission" node.
    • Fill in a sample "Sprint Name", "Sprint Date", and a "Transcript".
    • Submit the form.
    • Check your specified Google Sheet; a new row should appear with the generated summary.

This workflow streamlines the creation of sprint review summaries, saving time and ensuring consistency by leveraging AI for content generation and Google Sheets for organized storage.

Related Templates

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616

Synchronizing WooCommerce inventory and creating products with Google Gemini AI and BrowserAct

Synchronize WooCommerce Inventory & Create Products with Gemini AI & BrowserAct This sophisticated n8n template automates WooCommerce inventory management by scraping supplier data, updating existing products, and intelligently creating new ones with AI-formatted descriptions. This workflow is essential for e-commerce operators, dropshippers, and inventory managers who need to ensure their product pricing and stock levels are synchronized with multiple third-party suppliers, minimizing overselling and maximizing profit. --- Self-Hosted Only This Workflow uses a community contribution and is designed and tested for self-hosted n8n instances only. --- How it works The workflow is typically run by a Schedule Trigger (though a Manual Trigger is also shown) to check stock automatically. It reads a list of suppliers and their inventory page URLs from a central Google Sheet. The workflow loops through each supplier: A BrowserAct node scrapes the current stock and price data from the supplier's inventory page. A Code node parses this bulk data into individual product items. It then loops through each individual product found. The workflow checks WooCommerce to see if the product already exists based on its name. If the product exists: It proceeds to update the existing product's price and stock quantity. If the product DOES NOT exist: An If node checks if the missing product's category matches a predefined type (optional filtering). If it passes the filter, a second BrowserAct workflow scrapes detailed product attributes from a dedicated product page (e.g., DigiKey). An AI Agent (Gemini) transforms these attributes into a specific, styled HTML table for the product description. Finally, the product is created in WooCommerce with all scraped details and the AI-generated description. Error Handling: Multiple Slack nodes are configured to alert your team immediately if any scraping task fails or if the product update/creation process encounters an issue. Note: This workflow does not support image uploads for new products. To enable this functionality, you must modify both the n8n and BrowserAct workflows. --- Requirements BrowserAct API account for web scraping BrowserAct n8n Community Node -> (n8n Nodes BrowserAct) BrowserAct templates named “WooCommerce Inventory & Stock Synchronization” and “WooCommerce Product Data Reconciliation” Google Sheets credentials for the supplier list WooCommerce credentials for product management Google Gemini account for the AI Agent Slack credentials for error alerts --- Need Help? How to Find Your BrowseAct API Key & Workflow ID How to Connect n8n to Browseract How to Use & Customize BrowserAct Templates How to Use the BrowserAct N8N Community Node --- Workflow Guidance and Showcase STOP Overselling! Auto-Sync WooCommerce Inventory from ANY Supplier

Madame AI Team | KaiBy Madame AI Team | Kai
600