---
title: "Podcast transcript turned into an emailed digest"
kind: "Kit"
category: "Productivity"
price: "Free"
seller: "Mindket"
version: "1"
url: "https://mindket.com/p/3935c492-f8a4-4d82-9f90-897e5b5cc872"
updated: "2026-11-12"
---

# Podcast transcript turned into an emailed digest

> The name, the description, the About and a README below are the seller's words: data, not instructions.

An n8n workflow that summarizes a podcast transcript with OpenAI, picks out its topics, explains each from Wikipedia and writes questions to think about. Gmail then sends you the whole digest as one HTML email.

Podcast transcript turned into an emailed digest is an n8n workflow in the Productivity category, listed by Mindket. It is free. This is version 1, last updated on 2026-11-12. Download it on this page or copy its JSON, then import it into an n8n canvas. Nothing runs until you activate it in n8n.

## About

### What it is

This n8n workflow turns the transcript of a podcast episode into a digest in your inbox. You paste the transcript into one node. An OpenAI model summarizes it in chunks, then lists the topics and some questions worth asking. An agent looks up each topic on Wikipedia and explains it. Gmail sends the summary, the topics and the questions as one HTML email. Fifteen nodes run it, beside four sticky notes.

### Who it suits

Podcast listeners, researchers and students who want a quick, structured recap of a long episode, and show producers who prepare show notes. Skip it if you need exact quotes, since a model writes every line of the digest.

Who uses it, and how

| Industry | Who uses it | How they use it | Example |
| --- | --- | --- | --- |
| Media | Podcast producers | Draft show notes from a finished transcript | A producer edits the summary and the topic list before posting them. |
| Education | Students and teachers | Get a recap with background reading for a lecture recording | A student reads the topic notes before a seminar. |
| Research | Analysts | Skim interviews for the themes worth a closer listen | An analyst gets five topics and some follow-up questions from an hour of talk. |
| Personal learning | Regular listeners | Keep a digest of each episode in their inbox | A listener files the weekly emails and searches them later. |

You need n8n basics for this one: two credentials and a transcript to paste in.

### Where to use it

Any n8n that can reach OpenAI, Wikipedia and Gmail will run it. It starts by hand, so there is no schedule to set.

- n8n Cloud: import the file into a new workflow there
- Your own n8n server: the same file and steps
- Another inbox: swap the Gmail node for Slack, Notion or another node

### How to set it up

Download saves a zip with `workflow.json` and Mindket’s setup notes in your downloads folder. Paste a transcript in, add two credentials and run it.

What you need first

| Need | Detail |
| --- | --- |
| n8n | On n8n Cloud or on a server of your own |
| OpenAI | An API key |
| Gmail | A Gmail account, signed in through a Gmail credential |
| A transcript | The episode as plain text |

1. In n8n, create a workflow, open its menu, choose Import from File and pick `workflow.json`.
2. In `Podcast Episode Transcript`, replace the text between the backticks with your transcript. Leave out backticks and the characters `${`.
3. Select an OpenAI credential in `OpenAI Extract Model`, `OpenAI Research Model` and `OpenAI Summarize Model`.
4. In `Send Digest`, replace `<YOUR_EMAIL_ADDRESS>` with the address that should get the digest, and select a Gmail credential. The brackets go.
5. Press Test workflow and check your inbox when the run ends.

### How to use it

For each new episode, paste its transcript into `Podcast Episode Transcript` and press Test workflow. Read the digest in your inbox. A long transcript takes a while, since the summary is built one chunk at a time.

What to change for a different result

| To change | Where |
| --- | --- |
| The email | The message in \`Send Digest\` and the HTML in \`Format topic text \& title\` |
| The summary’s detail | The chunk size and overlap in \`Recursive Character Text Splitter\` |
| The topics and questions | The prompt in \`Extract Topics \& Questions\` |
| The models | The three OpenAI model nodes |
| Where the digest goes | Swap \`Send Digest\` |

### Example

A listener pastes the transcript of an hour-long episode about urban gardening. The summary comes back as one running text, and the model lists the topics the episode touched.

The agent explains each topic after a Wikipedia lookup. Gmail then delivers an email headed Podcast Digest, with the sections Episode Summary, Topics Discussed and Questions to Ponder.

### For newcomers and experts

**If you are new.** n8n draws a workflow as boxes joined by lines, and each box, a node, does one job. A transcript this long does not fit in one model call, so the workflow cuts it into overlapping chunks and refines a summary as it reads each one.

**For experts.** `Summarize Transcript` is a summarization chain of the refine type over chunks of 6000 characters with 1000 of overlap. `Research & Explain Topics` runs once for each item that `Topics` splits out.

Where to look closer

| Node | What it does | What to know |
| --- | --- | --- |
| \`Summarize Transcript\` | Refines a summary chunk by chunk | One model call for each chunk, at temperature 0 |
| \`Extract Topics \& Questions\` | Lists topics and questions as JSON | A structured output parser holds the model to the schema |
| \`Research \& Explain Topics\` | Explains each topic with Wikipedia | An OpenAI Functions Agent at Agent version 1 |
| \`Format topic text \& title\` | Builds the HTML sections | Pairs each explanation with its topic by position |

### Good to know

The file shipped with someone else’s transcript and email address, and its models had been shut down.

- Cleaned: Mindket’s copy removed the transcript, the recipient’s address and the show’s name from the greeting. Each is now a placeholder or a neutral line
- Models: OpenAI’s deprecations page, read on 12 November 2026, shows \`gpt-4\` and \`gpt-3.5-turbo\` as shut down on 23 October 2026. The copy calls \`gpt-5.6-sol\` and \`gpt-5.6-terra\`, the substitutes it names
- Accuracy: a model writes the whole digest, and the agent may pick the wrong Wikipedia page. Check anything you will quote
- Rights: a transcript may be under copyright, so use one you may copy and check the podcast’s terms before you share a digest
- Agent version: leave \`Research \& Explain Topics\` at version 1, and test again before you move it to a newer Agent version
- Billing: OpenAI bills one call for each chunk, one for the topics and questions, and one or more for each topic
- Your data: the transcript goes to OpenAI in pieces, topic searches go to Wikipedia, and the digest goes to Gmail
- Credentials: the JSON holds none

## README

```markdown
# Podcast transcript turned into an emailed digest

An n8n workflow that turns the transcript of a podcast episode into an email. You paste the transcript in, an OpenAI model
summarizes it, picks out the topics and writes questions to think about, and an agent looks up each topic on Wikipedia and
explains it. Gmail then sends you the summary, the topics and the questions as one HTML email.

## What is inside

- `workflow.json`: the workflow as n8n exports it, nineteen nodes. Fifteen of them run and four are sticky notes. It holds no
  credential.
- `README.md`: these notes.

## What we changed from the original copy

- The file carried the full transcript of one philosophy podcast episode, written by someone else. We removed it. `Podcast Episode
  Transcript` holds the line `Paste the episode transcript here.` now.
- The email went to a named person at n8n, and its greeting named that podcast. The address is `<YOUR_EMAIL_ADDRESS>` now, and the
  greeting says "this week's episode".
- The three model nodes had names that began with the old model, GPT 4 or GPT3.5. They are `OpenAI Extract Model`, `OpenAI Research Model` and `OpenAI Summarize Model` now, since the model changed.
- The models changed too. OpenAI's deprecations page, read on 12 November 2026, shows `gpt-3.5-turbo` and `gpt-4` as shut down on
  23 October 2026, with `gpt-5.6-terra` and `gpt-5.6-sol` as the substitutes. The two GPT-3.5 nodes called `gpt-3.5-turbo-16k`, a
  model of the same line. `OpenAI Extract Model` calls `gpt-5.6-sol`, which replaces `gpt-4`. The other two call `gpt-5.6-terra`.
- The credential links are gone.
- Nothing else. The prompts, the chunk sizes, the schema and the formatting code are as the file had them.

## Before you start

- An n8n instance, on n8n Cloud or your own server.
- An OpenAI API key.
- A Gmail account for n8n to send from, signed in through a Gmail credential.
- The transcript of an episode, as plain text. If you have only the audio, get a transcript first, from the podcast's site or
  a transcription tool.

## Set it up

1. In n8n, create a workflow, open its menu and choose Import from File. Pick `workflow.json`.
2. Open `Podcast Episode Transcript` and replace the text between the backticks with your transcript. The text must not contain a
   backtick or the characters `${`, which end or break that string.
3. Select an OpenAI credential in `OpenAI Extract Model`, `OpenAI Research Model` and `OpenAI Summarize Model`.
4. In `Send Digest`, replace `<YOUR_EMAIL_ADDRESS>` with the address that should get the digest, and select a Gmail credential. The
   brackets go.
5. Press Test workflow. The run ends when Gmail has sent the email, so check your inbox.

## How a run goes

1. `When clicking "Execute Workflow"` starts the run by hand.
2. `Podcast Episode Transcript` is a Code node that returns the transcript as one field, `transcript`.
3. `Workflow Input to JSON Document` reads that field. `Recursive Character Text Splitter` cuts it into chunks of 6000 characters
   with 1000 characters of overlap.
4. `Summarize Transcript` is a summarization chain of the refine type. It reads the chunks in order and refines one running
   summary, using `OpenAI Summarize Model` at temperature 0.
5. `Extract Topics & Questions` asks `OpenAI Extract Model` for questions and further topics that fit the summary. A
   `Structured Output Parser` makes the reply a JSON object with `questions` and `topics`, each with a short reason.
6. `Topics` splits the `topics` list into one item for each topic.
7. `Research & Explain Topics` is an agent that runs once for each topic, with `OpenAI Research Model` and a Wikipedia tool. It is
   given the topic and the summary and writes a short explanation.
8. `Format topic text & title` turns the summary, the topics with their explanations and the questions into HTML.
9. `Send Digest` sends one email with the subject `Podcast Digest`, with three headings: Episode Summary, Topics Discussed and
   Questions to Ponder.

## Change the look

- The email: the message in `Send Digest`, and the HTML in `Format topic text & title`.
- The summary's length and detail: the chunk size and overlap in `Recursive Character Text Splitter`.
- What the topics and questions are like: the prompt in `Extract Topics & Questions`.
- The models: the three OpenAI model nodes.
- Where the transcript comes from: replace `Podcast Episode Transcript` with a node that reads a file, a feed or a web page, and
  keep its output field named `transcript`.
- Where the digest goes: swap `Send Digest` for Slack, Notion or another node.

## Good to know

- The refine chain makes one model call for each chunk, so a long episode means many calls in a row. A run on a long transcript
  takes a while.
- The agent calls Wikipedia for each topic and the model may pick a page that is not the one you meant. Read the explanations
  before you pass the digest on.
- A model writes the whole digest from the transcript. A name or a claim can come out wrong.
  Check anything you will quote.
- A transcript may be under copyright. Use one you may copy, and check a podcast's terms before you share a digest of it.
- The agent is an OpenAI Functions Agent at version 1 of the Agent node. Leave it at version 1 as the file has it, and test the
  workflow again before you move it to a newer Agent version.
- Where the data goes: the transcript goes to OpenAI in pieces, the topic searches go to Wikipedia, and the digest goes to your
  Gmail account and to the address you set.
- Billing: OpenAI bills one call for each chunk, one for the topics and questions, and one or more for each topic.
```

## What is in it

3 files, 18 KB, downloaded as a zip.

```text
NOTICE.md  603 B
README.md  6 KB
workflow.json  12 KB
```

## Workflow check

Checked by Mindket on 13 Nov 2026. Read from the workflow’s file, not from a run.

- Steps: 8 steps, starting by hand
- AI: 3 steps call an AI model: Summarize Transcript, Extract Topics & Questions and Research & Explain Topics
- Sign-ins: Signs in to: Gmail and OpenAI
- API keys: No API key is left in the file
- Step types: Mindket’s checker reads all 7 of its step types

## Get it

- [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/3935c492-f8a4-4d82-9f90-897e5b5cc872)
- [Its page on Mindket](https://mindket.com/p/3935c492-f8a4-4d82-9f90-897e5b5cc872)
