Skip to content
Tala Safadi
All work

Automation · Personal assistant

AI Personal Assistant (Telegram)

My own assistant on Telegram. I message it like a friend, and a main agent hands the work to Tasks and Calendar agents, keeps Supabase and Google Tasks in sync, and sends me a morning brief, an evening plan and a weekly report.

Built for my own daily use, so it has one user: me.

Problem

Tasks and meetings live in separate apps, and adding one means stopping what you're doing to open them. Most bots don't help much, because they make you learn commands and reply like a menu.

Solution

An assistant I simply message in Palestinian Arabic. A main agent understands the request and delegates it, so one message can add a task and book a meeting. It also comes to me: a morning brief, an evening plan and a Friday report arrive on their own.

Architecture

taskeventTelegramtriggerAI Agentagenttasks_agentagentcalendar_agentagentcreate_task_rowdbgoogle_tasktoolsave_task_iddbget_eventstoolcreate_eventtoolSend Replyoutput

Live replay

A task and a meeting in one message

What it does

  • Conversational, with slash commands kept as optional shortcuts
  • Lists, adds, completes and renames tasks, and tracks a weekly goal
  • Every task change is written to Supabase and synced to Google Tasks
  • Checks Google Calendar for overlaps before booking, and shows the conflict instead of double-booking
  • Morning brief at 7:30, evening plan at 21:00 and a weekly report on Fridays at 18:00
  • Replies like a close friend in Palestinian Arabic, and matches my mood
  • Works only for my Telegram account, and always replies when something fails

Challenges and fixes

  • The first plan used slash commands and a Switch node, so I'd have had to remember the commands.

    A main AI agent now understands plain messages and delegates. The commands stayed as optional shortcuts.

  • The first agent version had a separate sub-agent for each action: list, add, complete, rename and delete.

    Merged into one Tasks agent that follows clear step-by-step recipes for each action.

  • A misunderstood message shouldn't be able to delete a task.

    Deleting needs an explicit /del with the task name, and rows are soft-deleted rather than removed.

  • Tasks with a date but no time were stored at 23:59, which looked wrong in messages.

    The agent records that no specific time was set, and shows a time only when I gave one.

  • Google Tasks can fail after the database write has already succeeded.

    The database step still finishes, and the reply says what didn't sync.

In action

[[TALA: screenshots, demo video]]

Stack

  • n8n
  • OpenAI (gpt-5, gpt-5-mini)
  • Supabase
  • Google Tasks
  • Google Calendar
  • Telegram Bot API

My role

Designed, built and use it myself: agents, prompts, database and integrations.

Want this for your business?

Next projectAI Rank