Route meeting action items to Slack using Gmail, OpenAI, and Google Sheets
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 17 nodes and runs on Gmail events. Along the way it connects Gmail, Google Sheets, OpenAI and Slack.
How it runs
Trigger: On Gmail events.
- Setup Meeting Configuration (Code): runs custom JavaScript code
- Extract Email Transcript (Code): runs custom JavaScript code
- Read Log from Google Sheets (Google Sheets): uses Google Sheets
- Identify Duplicate Meetings (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- OpenAI: uses OpenAI
- Parse Analysis Results (Code): runs custom JavaScript code
- Route Based on Priority (Switch): routes items into branches
- Prepare Slack Notification (Code): runs custom JavaScript code
- Generate FYI Log Entry (Code): runs custom JavaScript code
…plus 6 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
- Still check Gmail Trigger below v1.4 runs as v1.4 (drafts skipped, max emails per poll) (When Email with Transcript Arrives).
Nodes used (7)
- Gmail Trigger
n8n-nodes-base.gmailTrigger - Code
n8n-nodes-base.code - Google Sheets
n8n-nodes-base.googleSheets - If
n8n-nodes-base.if - OpenAI
@n8n/n8n-nodes-langchain.openAi - Switch
n8n-nodes-base.switch - Slack
n8n-nodes-base.slack
From the author
Quick overview This workflow watches a Gmail label for new meeting transcript emails, extracts the transcript, uses OpenAI to generate a summary and action items, routes urgent items to the right Slack channel, and logs the meeting and action items to Google…