Process meeting transcripts into Notion notes & tasks with AI and Google Drive

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Ingest meeting webhooks, process transcript, classify the meeting, generate structured notes with AI Agent, file the transcript to Google Drive, write rich pages to Notion, and create assigned task...

Best for

Project Management automation workflows
AI Chatbot automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.httprequest, n8n-nodes-base.if, n8n-nodes-base.scheduletrigger, n8n-nodes-base.code, @n8n/n8n-nodes-langchain.lmchatanthropic, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.wait, n8n-nodes-base.switch

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Matty Reed.

Original n8n.io source

1.1 Workflow description

Title: Process meeting transcripts into Notion notes & tasks with AI and Google Drive
Workflow name: Process meeting transcripts into Notion notes & tasks with AI and Google Drive

Who is this for?

Teams that record calls and want instant, structured notes in Notion, with transcripts archived in Google Drive and action items auto-created—without manual copy/paste.

What problem does it solve?

Manual note taking is slow and inconsistent. This flow listens for a meeting webhook, flattens the transcript, classifies the call, runs a tailored notetaker prompt, and writes a clean Notion page plus tasks—hands-free and standardized.

How it works

#	Node	Purpose
1	New Meeting Webhook	Receives meeting payload with transcript segments and metadata. (Webhook Node)
2	Flatten Transcript (Code)	Joins segments to `speaker: text` lines and extracts `title`, `meetingId`, `url`.
3	Set Title + Transcript + URL	Normalizes fields for downstream nodes.
4	Categorize Meeting	Uses OpenAI to return `{ "meetingType": "DiscoveryCall"
5	Switch	Routes to the correct notetaker branch based on `meetingType`.
6a	Discovery Call Notetaker	Anthropic model + structured parser to extract sales-specific fields. (Anthropic Docs)
6b	Misc Meeting Notetaker	General meeting notetaker with strict JSON schema.
7a	Add Discovery Meeting Notes to Notion	Writes a formatted page with overview, goals, pains, risks, and action items.
7b	Add Meeting Notes to Notion	Writes a simpler page for non-discovery meetings.
8	Set Notion Page ID	Captures created page ID and the action-items array.
9	Create File (Google Drive)	Saves raw transcript text and returns the file ID. (Drive API)
10	Link Transcript in Notion	Updates the Notion page with a viewable Drive link.
11	Split out Tasks	Expands the action-items array to one item per execution.
12	If Assigned to Me	Filters tasks where `assignee = "Matty Reed"`.
13	Add Tasks (Notion)	Creates tasks in your Notion Tasks DB, links to the meeting page. (Notion API)
*	(Optional polling path)	If webhooks aren’t available: Schedule Trigger → Get Meetings from Notion → List Meetings (HTTP Request) → Get New Meetings (Code) → Get Transcript (HTTP) → Transcript Ready? → Wait → Flatten. Disabled by default.

Setup steps

Import the JSON flow into n8n
Confirm nodes marked disabled stay off unless you need the polling path.
Docs: n8n
Credentials
- OpenAI: add API key and attach to Categorize Meeting.
- Anthropic: add API key and attach to both notetaker agents.
- Notion: create an internal integration, share your Meetings and Tasks databases with it, then attach the credential to Notion nodes.
- Google Drive: OAuth2 credential for Create File.
Map your databases and properties
Replace the placeholder Notion database IDs with your Meetings and Tasks DB IDs. Verify property names like Meeting Name|title, Summary|rich_text, Category|multi_select, Assignee|people, etc., match your schema.
Drive folder
Update the folderId in Create File to your preferred folder. Ensure link-sharing fits your privacy policy.
Webhook
Expose New Meeting Webhook via your n8n instance. Send a sample payload from your meeting recorder to verify the calendar_invitees, transcript, title, and url fields match the code node expectations.
Test
Run the flow with a recorded meeting. Confirm:
- Page created in Meetings DB with structured sections.
- Transcript file created in Drive and linked back to Notion.
- Tasks created in Tasks DB when assignee = "Matty Reed".

Notes and tips

Schemas are strict. Both notetakers output fixed JSON keys. Missing values become empty strings.
PII handling. Transcripts may include personal data. Limit access to Notion pages and Drive files per policy.
Do not hardcode secrets. Store API keys in n8n credentials. Avoid putting tokens in Code nodes.
Rate limits. Long transcripts increase token usage. Consider chunking upstream if needed.
Extensibility. Add more branches in Switch for other meeting types with custom prompts and parsers.

Resources

n8n Webhook Node – https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.webhook/
n8n HTTP Request Node – https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/
OpenAI Responses – https://platform.openai.com/docs/guides/realtime-and-responses/responses
Anthropic Docs – https://docs.anthropic.com/en/docs
Notion API – https://developers.notion.com/docs
Google Drive API – https://developers.google.com/drive/api

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - List Meetings

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 2

Block 2 - Get Transcript

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 2

Block 3 - Transcript Ready?

Type / Role: n8n-nodes-base.if - if
Config choices: Version 1

Block 4 - Schedule Trigger

Type / Role: n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices: Version 1.2

Block 5 - Flatten

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 6 - Anthropic Chat Model

Type / Role: @n8n/n8n-nodes-langchain.lmChatAnthropic - lmChatAnthropic
Config choices: Version 1.3

Block 7 - Structured Output Parser

Type / Role: @n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices: Version 1.2

Block 8 - Wait

Type / Role: n8n-nodes-base.wait - wait
Config choices: Version 1.1

Block 9 - Switch

Type / Role: n8n-nodes-base.switch - switch
Config choices: Version 3.2

Block 10 - Structured Output Parser1

Type / Role: @n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices: Version 1.2

Block 11 - Get Meetings from Notion

Type / Role: n8n-nodes-base.notion - notion
Config choices: Version 2.2

Block 12 - Get New Meetings

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 13 - Misc Meeting Notetaker

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 1.9

Block 14 - Categorize Meeting

Type / Role: @n8n/n8n-nodes-langchain.openAi - openAi
Config choices: Version 1.8

Block 15 - Discovery Call Notetaker

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 1.9

Block 16 - Add Meeting Notes to Notion

Type / Role: n8n-nodes-base.notion - notion
Config choices: Version 2

Block 17 - Set Title + Transcript + URL

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 18 - Add Discovery Meeting Notes to Notion

Type / Role: n8n-nodes-base.notion - notion
Config choices: Version 2.2

Block 19 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 20 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 21 - Sticky Note2

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 22 - Sticky Note3

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 23 - Sticky Note4

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 24 - Sticky Note5

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Showing the first 24 of 36 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	Process meeting transcripts into Notion notes & tasks with AI and Google Drive
Complexity	advanced
Nodes	36
Categories	Project Management, AI Chatbot
Author	Matty Reed
Published	20 Oct 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/9929/9929.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Project Management workflows AI Chatbot workflows

Frequently asked questions

What does Process meeting transcripts into Notion notes & tasks with AI and Google Drive do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Project Management, AI Chatbot use case.

Matty Reed

9 workflows

Nodes

n8n-nodes-base.httprequest n8n-nodes-base.if n8n-nodes-base.scheduletrigger n8n-nodes-base.code @n8n/n8n-nodes-langchain.lmchatanthropic @n8n/n8n-nodes-langchain.outputparserstructured n8n-nodes-base.wait n8n-nodes-base.switch

Complexity

advanced

Published 20 Oct 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/9929/9929.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Tag stale ClickUp tasks and escalate overdue items with assignee comments

## Quick overview This workflow runs daily on a schedule and checks ClickUp tasks in one or more lists for inactivity based on the task’s date_updated field, automatically applying “stale” tags and escalating long-idle tasks by tagging them and posting an assignee comment. ## How it works 1. Runs every day at the configured hour using the schedule trigger. 2. Loads monitoring settings (statuses, tags, stale thresholds, and tag names) and fetches matching tasks from the selected ClickUp list(s), then merges and deduplicates them. 3. Skips tasks that already have the second-level stale tag (for example, stale:14). 4. For tasks without the first-level stale tag, checks the last updated timestamp and adds either the first-level stale tag (for example, stale:7) or the second-level stale tag if they already exceed the higher threshold. 5. For tasks that already have the first-level stale tag, checks whether enough time has passed since that tag was applied and, if so, removes the first-level tag and adds the second-level stale tag. 6. When a task is escalated to the second-level stale tag, posts a warning comment on the ClickUp task and assigns the comment to the task assignee (or the creator if no assignee exists). ## Setup 1. Add a ClickUp API credential (OAuth or API token) and select it on all ClickUp nodes. 2. In the ClickUp task search node(s), choose the list(s) you want to monitor and enable/configure the second list node if you want to pull tasks from multiple lists. 3. Update the monitoring settings (monitoredStatuses, monitoredTags, daysUntilFirstStaleTag, daysUntilSecondStaleTag, and the stale tag names) to match your ClickUp workspace conventions. 4. Adjust the schedule trigger time and, if needed, set the workflow timezone in n8n settings so the run time matches your local time. ## Requirements - A ClickUp account with API access - ClickUp credential configured in n8n - At least one ClickUp list to monitor ## Customization - Change thresholds — Edit `daysUntilFirstStaleTag` and `daysUntilSecondStaleTag` in `SetContext` to any number of days - Change tag names — Update `firstStaleTagName` / `secondStaleTagName` to match your ClickUp tag naming convention - Monitor different statuses — Edit `monitoredStatuses` and `monitoredTags` in `SetContext` (e.g. add `review`, `blocked`) - Add more lists — Duplicate `GetTaskFromList1`, update the List ID, enable the node, and connect its output to a new input port on `AppendListTasks` - Change schedule — Open `TriggerRegularly` and switch from daily to weekdays-only or any custom cron interval - Disable subtasks — Open each `GetTaskFromList` node and set `subtasks` to `false` in the Filters section

View

Summarize daily Slack standups with OpenAI, Notion, and Google Sheets

## Quick overview This workflow runs every weekday, pulls standup messages from a Slack channel, uses OpenAI to generate a structured daily digest, saves the digest to a Notion database, posts a summary back to Slack, and appends an audit entry to Google Sheets. ## How it works 1. Runs every weekday morning on a cron schedule. 2. Fetches the day’s recent messages from a specified Slack standup channel and filters out bot, subtype, and join/leave system messages. 3. Checks whether any standup messages remain and posts a Slack notice if none are found. 4. Formats the remaining Slack updates into a single structured prompt with date, team name, and message count. 5. Sends the formatted standup text to OpenAI (gpt-4.1-mini) to generate a JSON digest with summary, highlights, blockers, per-user updates, and mood. 6. Parses and enriches the AI output with metadata, creates a new page in a Notion database, posts the digest to a Slack summary channel, and appends a run record to a Google Sheets “Audit Log” sheet. ## Setup 1. Add a Slack OAuth2 credential and set the standup channel ID (history source) and the summary channel ID (digest destination). 2. Add an OpenAI credential and confirm the model selection (gpt-4.1-mini) is available in your account. 3. Add a Notion credential, create/select a target database, and replace `YOUR_NOTION_DATABASE_ID` (and ensure the database has the referenced properties: Date, Team, Message Count, Mood). 4. Add a Google Sheets Service Account credential, share the target spreadsheet with the service account email, and replace `YOUR_SHEET_ID` and the sheet name (“Audit Log”) if different. 5. Adjust the schedule cron expression (`0 9 * * 1-5`) to match your team’s standup timing and timezone expectations.

View

Sync check due dates from Google Sheets to Google Calendar with Telegram alerts

## Quick overview This workflow watches a Google Sheets check inventory list and creates or updates matching all-day events in Google Calendar, then posts a creation or update notice to a Telegram group. ## How it works 1. Polls Google Sheets every hour for any updates in the “Check Inventory” sheet. 2. Checks whether the updated row already contains a Google Calendar Event ID. 3. If the Event ID is empty, searches Google Calendar for an existing event whose text matches the check number and backfills the found Event ID to Google Sheets. 4. If no matching calendar event exists, creates an all-day Google Calendar event using the check date and details from the Google Sheets row, then writes the new Event ID back to the sheet. 5. If an Event ID exists, fetches the corresponding Google Calendar event and compares its date, summary, and description to the latest Google Sheets values. 6. When differences are detected, updates the Google Calendar event to match the sheet and sends a Telegram message summarizing the created or updated events. ## Setup 1. Connect credentials for Google Sheets (including Google Sheets Trigger), Google Calendar OAuth2, and a Telegram Bot API account. 2. Replace `YOUR_CHECK_INVENTORY_SHEET_ID` in all Google Sheets nodes and ensure the “Check Inventory” sheet contains the required columns (including “Check Number” and “Event ID”). 3. Set the target Google Calendar ID (for example `[email protected]` or a shared calendar ID) in the Google Calendar nodes. 4. Replace `YOUR_TELEGRAM_GROUP_CHAT_ID` in the Telegram nodes and edit the message text to use the correct @mentions for your team.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Process meeting transcripts into Notion notes & tasks with AI and Google Drive

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Who is this for?

What problem does it solve?

How it works

Setup steps

Notes and tips

Resources

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - List Meetings

Block 2 - Get Transcript

Block 3 - Transcript Ready?

Block 4 - Schedule Trigger

Block 5 - Flatten

Block 6 - Anthropic Chat Model

Block 7 - Structured Output Parser

Block 8 - Wait

Block 9 - Switch

Block 10 - Structured Output Parser1

Block 11 - Get Meetings from Notion

Block 12 - Get New Meetings

Block 13 - Misc Meeting Notetaker

Block 14 - Categorize Meeting

Block 15 - Discovery Call Notetaker

Block 16 - Add Meeting Notes to Notion

Block 17 - Set Title + Transcript + URL

Block 18 - Add Discovery Meeting Notes to Notion

Block 19 - Sticky Note

Block 20 - Sticky Note1

Block 21 - Sticky Note2

Block 22 - Sticky Note3

Block 23 - Sticky Note4

Block 24 - Sticky Note5

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions