Back to Catalog

Convert meeting recordings to notes & action items with AssemblyAI, GPT-4 & Sheets

Țugui DragoșȚugui Dragoș
227 views
2/3/2026
Official Page

This workflow automates the process of turning meeting recordings into structured notes and actionable tasks using AssemblyAI and Google Sheets. It is ideal for teams who want to save time on manual note-taking and ensure that action items from meetings are never missed.

What it does

  • Receives a meeting recording (audio file) via webhook
  • Transcribes the audio using AssemblyAI
  • Uses AI to generate structured meeting notes and extract action items (tasks)
  • Logs meeting details and action items to a Google Sheet for easy tracking

Use cases

  • Automatically document meetings and share notes with your team
  • Track action items and responsibilities from every meeting
  • Centralize meeting outcomes and tasks in Google Sheets

Quick Setup

  1. AssemblyAI API Key: Sign up at AssemblyAI and get your API key.

  2. Google Sheets Credentials: Set up a Google Service Account and share your target Google Sheet with the service account email.

  3. OpenAI API Key (optional, if using OpenAI for notes extraction): Get your API key from OpenAI.

  4. Configure the following essential nodes:

    • Recording Ready Webhook: Set the webhook URL in your meeting platform to trigger the workflow when a recording is ready.
    • Workflow Configuration: Enter your AssemblyAI API key, default due date, and admin email.
    • AssemblyAI Transcription: Add your AssemblyAI API key in the credentials.
    • Generate Meeting Notes & Extract Action Items: Add your OpenAI API key if required.
    • Log Meeting to Sheets: Enter your Google Sheets document ID and sheet name.

How to Use AssemblyAI in this Workflow

  • The workflow sends the meeting audio file to AssemblyAI via the AssemblyAI Transcription node.
  • AssemblyAI processes the audio and returns a full transcript.
  • The transcript is then used by AI nodes to generate meeting notes and extract action items.

Requirements

  • AssemblyAI API key
  • Google Service Account credentials
  • (Optional) OpenAI API key for advanced note and action item extraction

Start the workflow by sending a meeting recording to the webhook URL. The rest is fully automated!

Convert Meeting Recordings to Notes & Action Items with AssemblyAI, GPT-4 & Google Sheets

This n8n workflow automates the process of transcribing meeting recordings, extracting key information like notes and action items using AI, and then storing this structured data in Google Sheets. It streamlines post-meeting follow-up and ensures important details are captured and organized.

What it does

  1. Receives Recording URL: The workflow starts by listening for a webhook trigger, expecting a POST request containing a URL to a meeting recording.
  2. Transcribes Audio (AssemblyAI - Implied): Although not explicitly present in the provided JSON, the workflow's name suggests an integration with AssemblyAI for transcription. It's likely an HTTP Request node (like "HTTP Request" in the JSON) would be configured to send the recording URL to AssemblyAI for transcription.
  3. Extracts Notes & Action Items (GPT-4): The transcribed text is then processed by an "AI Agent" node, which likely uses an "OpenAI Chat Model" (GPT-4) in conjunction with a "Structured Output Parser" to extract meeting notes and action items in a structured format.
  4. Formats Data: An "Edit Fields (Set)" node prepares the extracted data for storage, ensuring it matches the expected schema for Google Sheets.
  5. Stores in Google Sheets: The processed notes and action items are appended as a new row to a specified Google Sheet.
  6. Conditional Logic: An "If" node is present, suggesting conditional logic might be applied based on the output of a previous step (e.g., if AI extraction was successful, or if certain keywords are present).

Prerequisites/Requirements

  • n8n Instance: A running n8n instance to host the workflow.
  • Webhook Source: An application or service capable of sending POST requests with meeting recording URLs to the n8n webhook.
  • AssemblyAI Account & API Key: (Implied) For transcribing audio recordings.
  • OpenAI Account & API Key: For GPT-4 access via the "OpenAI Chat Model".
  • Google Account: With access to Google Sheets for storing the extracted data.
  • Google Sheets Credential: Configured in n8n to allow writing to your spreadsheet.
  • OpenAI Credential: Configured in n8n for API access.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Webhook:
    • Activate the "Webhook" node.
    • Copy the generated webhook URL. This URL will be used by your external system to trigger the workflow with a recording link.
  3. Configure Credentials:
    • Set up a Google Sheets credential in n8n.
    • Set up an OpenAI credential in n8n.
    • (Implied) If using AssemblyAI via an HTTP Request node, configure the necessary API key or authentication.
  4. Configure Google Sheets Node:
    • Specify the Spreadsheet ID and Sheet Name where the meeting notes and action items should be stored.
    • Ensure the column headers in your Google Sheet match the fields being output by the "Edit Fields (Set)" node (e.g., "Meeting Notes", "Action Items", "Recording URL").
  5. Configure AI Agent and OpenAI Chat Model:
    • Ensure the "OpenAI Chat Model" is correctly configured with your OpenAI credential and the desired model (e.g., gpt-4).
    • Review and adjust the prompt within the "AI Agent" node to guide the AI in extracting the desired notes and action items from the transcription.
    • Verify the "Structured Output Parser" matches the expected JSON schema for the AI's output.
  6. Configure HTTP Request (AssemblyAI - Implied):
    • If an HTTP Request node is used for AssemblyAI, ensure it's configured to send the recording URL and receive the transcription.
  7. Activate the Workflow: Once all configurations are complete, activate the workflow.
  8. Trigger the Workflow: Send a POST request to the webhook URL (obtained in step 2) with the meeting recording URL in the request body. The workflow will then process the recording and update your Google Sheet.

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.

Ranjan DailataBy Ranjan Dailata
161

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

Daniel NkenchoBy Daniel Nkencho
601

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