AI Calendar Agent banner
Sevenninetwo Sevenninetwo

AI Calendar Agent

AI community

Description

Autonomous AI agent that manages Google Calendar through natural language via Telegram. Built with Claude API, Python, and Google Calendar API - no GUI, no clicks, just conversation. Always on, reliable and secure.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

AI Calendar Agent

An autonomous AI agent that manages Google Calendar through natural language via Telegram. No GUI (graphical user interface), no clicks — just conversation!

What It Does

Message the bot in plain English and it handles the rest:

  • "What's on today?" → summarises your day
  • "Am I free tomorrow afternoon?" → checks availability
  • "Add a meeting with the team on Friday at 3pm" → creates the event and asks for confirmation
  • "Delete my 2pm tomorrow" → finds it and confirms before deleting
  • "Move my Monday standup to 4pm" → edits the event with a confirmation gate

Why I Built This

This was a deliberate exercise in end-to-end agent deployment — not a tutorial follow-along. The goal was to design, build, ship, and iterate on a fully functional AI agent in a single day, making real architectural decisions along the way.

The core challenge: build something that is fast, secure, always-on, and actually useful — without a server, without a budget, and without prior infrastructure experience.

Architecture

You (Telegram) → bot.py → Claude API (intent classification) → Google Calendar API → bot.py → Telegram

**Claude API** handles natural language understanding — parsing intent, resolving dates like "next Friday" or "tomorrow afternoon", and formatting responses conversationally.

**Google Calendar API** executes the actual read/write operations on the calendar.

**python-telegram-bot** manages the Telegram interface, conversation state, and inline confirmation buttons.

**Railway** hosts the bot in the cloud so it runs 24/7 independent of local hardware.

Key Design Decisions

**Confirmation gate for all write operations.** The agent never modifies the calendar without explicit user approval. Read operations (summaries, availability checks) are instant. Write operations (add, edit, delete) always show exactly what will happen and wait for a "yes" before proceeding. This is a deliberate safety pattern for any agent that touches real dat