In this categoryAutomation · 38
- How to Self-Host n8n with Docker for AI WorkflowsStart
- How to Extract Structured Data from PDFs with n8n
- How to Add OpenAI Credentials to n8n
- How to Connect Anthropic Claude as the Model in n8n Workflows
- How to Build an AI Messaging / Chatbot Automation (No Code)
- How to Build an AI Agent with Tools in n8n
- How to Build an n8n Workflow That Summarizes New Emails with AI
- How to Build a RAG Chatbot Over Your Docs in n8n
- How to Auto-Classify and Route Support Tickets with AI in n8n
- How to Schedule Daily AI Content Generation in n8n
- How to Extract Structured Data from PDFs with AI in n8n
- How to Add Error Handling and Retries to n8n AI Workflows
- How to Transcribe and Summarize Audio with AI in n8n
- How to Summarize Incoming Emails with AI in Make.com
- How to Auto-Classify Support Tickets with AI in Make.com
- How to Turn RSS Headlines into AI Blog Drafts in Make.com
- How to Build an AI Telegram Chatbot in Make.com
- How to Answer Questions from Your Docs with AI in Make.com
- How to Auto-Transcribe Audio Files with Whisper in Make.com
- How to Extract Invoice Data from PDFs with AI Vision in Make.com
- How to Generate Images from a Spreadsheet with AI in Make.com
- How to Run AI Sentiment Analysis on New Reviews in Make.com
- How to Auto-Translate Content into Multiple Languages in Make.com
- How to Handle AI Errors and Rate Limits in Make.com Scenarios
- How to Build Your First Zap with an AI Step
- How to Use Your Own OpenAI API Key in Zapier
- How to Auto-Summarize Form Submissions and Post Them to Slack
- How to Auto-Generate Social Media Captions From New Blog Posts
- How to Extract Structured Data From Emails Using a Zapier AI Step
- How to Call the Claude API From Zapier Using Webhooks
- How to Build a Simple AI Chatbot with Zapier Interfaces and Tables
- How to Build a Multi-Step AI Research Agent in Zapier
- How to Auto-Categorize and Route Support Tickets with AI and Paths
- How to Cut AI Task Usage in Zapier With Filters and Formatter
- How to Debug AI Steps in Zapier Using Zap History
How to Transcribe and Summarize Audio with AI in n8n
Send an audio file to a speech-to-text model, then summarize the transcript with an LLM to turn meetings and voice notes into action items.
Voice notes and meeting recordings are full of decisions nobody writes down. This workflow takes an audio file, transcribes it with a speech-to-text model, and summarizes the transcript into key points and action items. Drop a file in and get notes out.
What you need
- A running n8n instance with an OpenAI credential
- An audio file (mp3, m4a, or wav) under the model's size limit
- A destination such as Notion, a doc, or email for the notes
Step 1: Bring the audio into the workflow
Use a trigger that supplies the file as binary data: a webhook upload, a Google Drive Trigger watching a folder, or a Read Files from Disk node for testing. The audio should arrive as a binary property on the item.
Step 2: Transcribe with the OpenAI node
Add an OpenAI node, set Resource to Audio and Operation to Transcribe a Recording. Choose the binary property holding the audio (for example data). The node returns the spoken words as plain text.
Step 3: Summarize into notes and actions
Feed the transcript into a second OpenAI node set to Message a Model. Ask for a structured summary so the output is consistent and easy to scan.
Summarize this transcript into:
- TL;DR (2 sentences)
- Key decisions (bullets)
- Action items (owner -> task)
Transcript:
{{ $json.text }}Step 4: Deliver the notes
Add a destination node such as Notion (Create Page) or Gmail (Send) and map the summary into it. Run the workflow on a real recording and confirm the notes arrive with decisions and action items separated.
Result
Any recording you drop in comes back as a clean summary with decisions and owned action items. Meetings and voice memos turn into searchable notes without anyone taking minutes.
Watch related tutorials
32:08
21:45
34:10
26:40
32:15
40:20New guides in your inbox
Fresh step-by-step how-to guides as we publish them. One email a week, no more.