Create project summaries from meeting transcripts with GPT-4 and Google Docs
🧾 Generate Project Summary from meeting transcript
Who’s it for 🤝
- Project managers looking to automate client meeting summaries
- Client success teams needing structured deliverables from transcripts
- Agencies and consultants who want consistent, repeatable documentation
How it works / What it does ⚙️
- Trigger: Manual or webhook trigger kicks off the workflow.
- Get meeting transcript: Reads the raw transcript from a specified Google Docs file.
- Generate summary: Sends transcript + instructions to OpenAI (gpt-4.1-mini) to produce a structured project summary.
- Convert to HTML: Transforms the LLM-generated Markdown into styled HTML.
- Prepare request: Wraps HTML and metadata into a multipart request body.
- Create Google Doc: Uploads the new “Project Summary” document into your Drive folder.
How to set up 🛠️
- Credentials
- Google Docs & Drive OAuth2 credentials
- OpenAI API key (gpt-4.1-mini)
- Nodes configuration
- Manual Trigger / webhook node
- Google Docs “Get meeting transcript” node: set
documentURL - AI Chat Model node: select
gpt-4.1-mini - Markdown node: enable tables & emoji
- Google Drive “CreateGoogleDoc” node: set target folder ID
- Paste in your IDs
- Update
documentURLto your transcript doc - Update
google_drive_folder_idin the Set node
- Update
- Execute
- Click “Execute Workflow” or call via webhook
Requirements 📋
- n8n
- Google OAuth2 scopes for Docs & Drive
- OpenAI account with GPT-4.1-mini access
- A Google Drive folder to store summaries
How to customize ✨
- Output format: Edit the Markdown prompt in the ChainLlm node to adjust headings or tone
- Timeline section: Extend LLM prompt template with your own phase table
- Styling: Tweak inline CSS in the Code node (
Prepare_Request) for fonts or margins - Trigger: Swap Manual Trigger for HTTP/Webhook trigger to integrate with other tools
- Language model: Upgrade to a different model by changing
model.valuein the AI node
Create Project Summaries from Meeting Transcripts with GPT-4 and Google Docs
This n8n workflow automates the process of generating concise project summaries from meeting transcripts using an OpenAI GPT-4 chat model and then storing these summaries in a Google Docs document. It's ideal for teams looking to streamline their meeting follow-ups and keep project documentation organized and easily accessible.
What it does
This workflow performs the following key steps:
- Manual Trigger: The workflow is initiated manually, allowing you to control when a summary is generated.
- Edit Fields (Set): Prepares the input data by setting a
meetingTranscriptvariable, which will contain the raw text of the meeting. - Basic LLM Chain: Utilizes a LangChain "Basic LLM Chain" to process the meeting transcript.
- OpenAI Chat Model: Employs an OpenAI Chat Model (likely GPT-4 or similar) to analyze the transcript and generate a project summary.
- Markdown: Formats the generated project summary into Markdown.
- Google Docs: Creates a new Google Docs document and inserts the Markdown-formatted project summary.
- HTTP Request: This node is present in the workflow but not connected to the main flow, suggesting it might be a remnant or intended for future expansion (e.g., posting the summary to another service).
- No Operation, do nothing: This node is also present but not connected, serving as a placeholder or unused element.
- Sticky Note: A sticky note is included for documentation purposes within the workflow itself.
- Code: This node is present but not connected, suggesting it might be a remnant or intended for future expansion.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- OpenAI Account & API Key: An OpenAI API key with access to chat models (e.g., GPT-4). This will need to be configured as an n8n credential for the "OpenAI Chat Model" node.
- Google Account: A Google account with access to Google Docs. This will need to be configured as an n8n credential for the "Google Docs" node.
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Set up your OpenAI API Key credential for the "OpenAI Chat Model" node.
- Set up your Google Account credential for the "Google Docs" node.
- Provide Meeting Transcript: In the "Edit Fields (Set)" node, update the
meetingTranscriptvariable with the actual text of the meeting you want to summarize. - Execute Workflow: Click the "Execute Workflow" button to run the workflow. It will generate a project summary and create a new Google Docs document with the summary.
- Review Output: Check your Google Docs for the newly created summary document.
Related Templates
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review
This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.
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