Analyze meeting sentiment with Azure OpenAI and save insights to 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 13 nodes and runs on a schedule (every day) (plus 1 other trigger). Along the way it connects Gmail, OpenAI Chat Model, Slack and Telegram. It also calls api.twelvedata.com over HTTP.
How it runs
Trigger: On a schedule (every day) (plus 1 other trigger).
- Fetch Price & Volume Data (HTTP Request): calls api.twelvedata.com
- Fetch RSI Indicator (HTTP Request): calls api.twelvedata.com
- Send a message (Gmail): uses Gmail
- Merge: merges the data from its input branches
- Calculate Trading Signals (Code): runs custom JavaScript code
- Generate AI Summary (AI Agent): runs an AI agent, with model: OpenAI GPT-4 Model
- Assign Alert Priority (Code): runs custom JavaScript code
- Route by Priority (If): checks a condition and branches into true / false
- Send to Telegram (High Priority) (Telegram): uses Telegram
- Send to Slack (Low Priority) (Slack): uses Slack
Services it uses
HTTP calls to: api.twelvedata.com
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.
Nodes used (11)
- Error Trigger
n8n-nodes-base.errorTrigger - Gmail
n8n-nodes-base.gmail - HTTP Request
n8n-nodes-base.httpRequest - Merge
n8n-nodes-base.merge - Code
n8n-nodes-base.code - AI Agent
@n8n/n8n-nodes-langchain.agent - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack - Telegram
n8n-nodes-base.telegram - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
📊 Description This workflow analyzes meeting transcripts using AI to understand team sentiment, engagement, and morale. The results are saved in Google Sheets for easy tracking and review. It receives meeting data through a webhook, validates the input,…