Google Calendar đź“… reminder system with GPT-4o and Telegram
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: AI Agent v1 (old agent modes). 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 6 nodes and runs on a schedule (every minute). Along the way it connects OpenAI Chat Model, Google Calendar and Telegram.
How it runs
Trigger: On a schedule (every minute).
- Get upcoming event (Google Calendar): get many
- Already sent? (Remove Duplicates): removes duplicate items
- Secretary Agent (AI Agent): runs an AI agent, with model: OpenAI Chat Model
- Send reminder (Telegram): uses Telegram
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- AI Agent v1 (old agent modes) in Secretary Agent (v1.8): replace with Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| AI Agent v1 (old agent modes) Secretary Agent (v1.8) | Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent. |
Nodes used (6)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Google Calendar
n8n-nodes-base.googleCalendar - Remove Duplicates
n8n-nodes-base.removeDuplicates - AI Agent
@n8n/n8n-nodes-langchain.agent - Telegram
n8n-nodes-base.telegram
From the author
How many times have you missed a meeting or forgotten an appointment because a calendar reminder got lost in the noise? Traditional notifications are often dry, easy to ignore, or scattered across different apps—leaving you scrambling at the last minute. This…