Automate 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
Automate Meeting Minutes Distribution with Google Sheets and Gmail
This n8n workflow streamlines the process of distributing meeting minutes by fetching data from Google Sheets, processing it, and sending personalized emails via Gmail. It's designed to ensure that the right attendees receive the correct meeting summaries promptly.
What it does
- Triggers Manually: The workflow is initiated manually, allowing you to control when the distribution process begins.
- Fetches Meeting Data: It connects to a specified Google Sheet to retrieve meeting minutes and attendee information.
- Processes Data (Placeholder): A "Code" node is included, likely intended for custom logic to format, filter, or transform the data fetched from Google Sheets before email distribution. Note: The current JSON does not contain specific code for this node, so it acts as a placeholder for custom processing.
- Distributes Minutes via Email: It uses Gmail to send out the processed meeting minutes to the relevant recipients.
Prerequisites/Requirements
- n8n Account/Instance: To run the workflow.
- Google Sheets Account: With a spreadsheet containing your meeting minutes and attendee details.
- Gmail Account: For sending the emails.
- Google OAuth2 Credentials: Configured in n8n for both Google Sheets and Gmail nodes to allow access to your Google services.
Setup/Usage
- Import the Workflow:
- Copy the provided JSON code.
- 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 code and click "Import".
- Configure Credentials:
- For the "Google Sheets" node, select or create your Google OAuth2 credentials to connect to your Google Sheets account.
- For the "Gmail" node, select or create your Google OAuth2 credentials to connect to your Gmail account.
- Configure Google Sheets Node:
- Specify the Spreadsheet ID and Sheet Name from which to read the meeting minutes.
- Adjust the Operation (e.g., "Read All Rows") and other settings as needed to fetch the correct data.
- Configure Code Node (Customization):
- Edit the "Code" node to add your specific JavaScript logic. This could include:
- Filtering rows based on criteria (e.g., date, status).
- Formatting the meeting minutes content for email.
- Extracting recipient email addresses from the sheet data.
- Creating personalized email subjects or bodies.
- Edit the "Code" node to add your specific JavaScript logic. This could include:
- Configure Gmail Node:
- Set the Recipient Email Address(es). This will likely come from the output of the "Code" node or directly from the Google Sheets data.
- Define the Subject and Body of the email. You will typically use expressions to dynamically insert meeting details and minutes from previous nodes (e.g.,
{{ $node["Google Sheets"].json["columnName"] }}or{{ $node["Code"].json["processedMinutes"] }}). - Choose the appropriate Operation (e.g., "Send an Email").
- Execute the Workflow:
- Click the "Execute Workflow" button on the "When clicking ‘Execute workflow’" node to run the automation.
This workflow provides a solid foundation for automating your meeting minutes distribution, with a flexible "Code" node to tailor the data processing to your exact needs.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Two-way property repair management system with Google Sheets & Drive
This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.
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