Skip to content
Amit Kumar, Senior Design Manager, UX & Product Design

// Home/// Work/// MAYA, my personal AI system

MAYA, my personal AI system

Seven n8n builds on one hub: a portfolio chat assistant, an interview-prep web app, a daily design digest, inbox triage, a morning briefing, two chat agents and a Claude to Gemini image pipeline. Results land in Discord, Telegram and Gmail, and most of them run every day.

// System case study

One n8n hub runs my site chat, my news, my inbox, my mornings and my images.

Seven builds that began as separate experiments now share one setup. n8n Cloud holds the logic, Gemini and OpenAI do the reading, and Discord and Telegram are where the results land. Below is how they fit together, with the real flow and real screens for each.

31
Days live on this site
7
Builds on one hub
1,000+
Visitors and conversations (my own count)
20+
People get the daily digest (my own count)
n8n · system map
System map: website chat, RSS, Gmail, calendar and Telegram voice notes feed one n8n hub, which sends results to Discord, Telegram, Google Sheets and the site widget
System map. Dots show data moving through the hub. Swipe sideways to see all of it.

// Inside the system

7 modules, each with its own flow and screens

LiveLive on this site: 31 days

MAYA, the front door

Answers recruiter questions on the site and logs every chat to Discord and Telegram.

A chat and voice assistant for recruiters that answers from my portfolio pages and trusted sources. Its whole setup lives in n8n.

  • n8n AI Agent
  • Gemini Flash Lite
  • OpenRouter fallback
  • Gemini text to speech
  • Google Sheets
  • Telegram
  • Discord
Full build notes
MAYA portfolio assistant workflow
The actual n8n workflow: MAYA portfolio assistant workflow

Screens from maya, the front door

MAYA welcome card on avid-designers.com
The welcome card visitors see when the site opens
MAYA chat window open on the portfolio home page
The chat window, with suggested questions
MAYA reply with portfolio links in the Discord maya-chat channel
Every chat is logged to Discord, with the links MAYA sent back
New MAYA chat notification in Discord
A new-chat alert in Discord (session id hidden)
New MAYA chat notification in Telegram
The same alert in Telegram, tagged by question type (session id hidden)
MAYA answering a text-to-speech question in Telegram
A visitor question about text to speech and MAYA's answer (session id hidden)

Usage figures are my own counts.

Industry
AI automation, personal
Timeline
Sept 2026, running daily
Technologies
n8n, Gemini, OpenAI, Discord, Telegram, Google Workspace

Project Overview

I started with separate experiments: a chat assistant for this site, an interview-prep app, a news digest, an inbox router. Within a few weeks they sat on the same n8n Cloud setup, the same Gemini and OpenAI access and the same Discord server, so I now treat them as one system.

Each automation has one job. MAYA answers recruiter questions and logs every chat. The digest reads ten sources each morning and picks five stories. The inbox router splits Gmail into channels. The briefing posts the calendar and tasks at 8 AM. The chat agents take voice notes and draft email. The interview-prep app builds a plan for designers, and the image pipeline lets Claude hand a prompt to Gemini.

My role

  • Designed the system, the prompts and the failure paths
  • Built every workflow in n8n, from the chat widget to the interview-prep web app
  • Designed the MAYA widget on this site: welcome card, suggestions and voice
  • Chose Discord and Telegram as the places where results land

Key Features

  • MAYA answers from portfolio pages and logs each chat to a sheet, Telegram and Discord
  • The digest scores each article from 1 to 10 and allows at most two from any one category
  • The inbox router sends job mail and important mail to separate Discord channels
  • Today's calendar and open tasks are posted at 8 AM
  • A Telegram voice agent reads mail, calendar and tasks
  • Interview prep builds a plan from a resume and scores each practice answer
  • Claude can send an image prompt to Gemini and get the result by email
  • The site widget's settings live in n8n, so edits go live without a redeploy

Challenges & Solutions

Challenge: Several small automations, each with its own place to check
Solution: One Discord server with a channel per job, plus Telegram for alerts. I check one place in the morning instead of five tools.

Challenge: AI that acts on tentative or unclear input
Solution: The next inbox version is written to treat "would Friday work?" as a proposal, not a booking, and does nothing below 85% confidence.

Takeaways

Usage figures on this page are my own counts. The site chat has run since 8 September 2026 and the digest since 18 September. The inbox classifier is still in progress.

Hiring a design leader for an AI product?

I'm open to design leadership roles. Send me a note and I'll reply within two working days.