Build a voice-enabled Telegram assistant for Gmail and Calendar

See What's Earning in AI Automation Freelancing.
DigiNo helps new AI automation freelancers earn faster by tracking what clients actually pay for.

Solopreneurs are drowning in browser tabs switching between Gmail, Google Calendar, and task lists. This AI automation brings all three into a single Telegram chat with voice support, and you can build and hand it off as a productized service.

What This Automation Does

Listens for voice or text messages in Telegram and routes each to the right tool automatically
Transcribes voice notes into text using OpenAI so hands-free users get full assistant functionality
Fetches unread Gmail summaries, upcoming calendar events, and existing Google Tasks on demand
Creates new Google Tasks and replies to the user in formatted Telegram messages, all within one conversation thread

Tools Used

Telegram
OpenAI
Gmail
n8n

Where to Get Hired for This Skill

On Contra, top freelancers across this stack have earned 101 combined verified reviews from real client projects.

Source: Contra freelancer search · refreshed 26 May 2026

Start Earning as a Freelancer on Contra

Contra is a commission-free professional network for independents. Browse live AI automation work and keep what you earn.

Join Contra Free →

How To Build It

Wire Telegram to receive voice and text

Configure a Telegram bot via BotFather and connect it as the entry point so the workflow receives every incoming message, then add a conditional branch that detects whether the message contains an audio file or plain text.

Transcribe voice messages with OpenAI

For audio messages, retrieve the voice file from Telegram's servers and pass it directly to OpenAI's transcription endpoint, producing a clean text string that feeds into the same assistant pipeline as typed messages.

Connect Gmail, Calendar, and Tasks as assistant tools

Authenticate Google OAuth2 once and expose Gmail, Google Calendar, and Google Tasks as callable tools so the AI assistant can query unread emails, fetch events for a given date, retrieve task lists, or create new tasks based on what the user asks.

Configure the AI assistant with memory and context

Set up the language model via OpenRouter with a system prompt that gives the assistant a name and persona, attach a sliding window memory buffer so it retains recent conversation turns, and inject today's date so calendar queries resolve correctly.

Send formatted responses back through Telegram

Route the assistant's output back to the originating Telegram chat in Markdown format, ensuring email summaries, event lists, and task confirmations render cleanly without raw syntax leaking into the message.

Pitfalls

Google OAuth2 tokens expire silently after extended inactivity, causing Gmail and Calendar calls to fail mid-conversation with no visible error to the end user. Build a token refresh check and alert the client before they notice.
Voice messages recorded in noisy environments produce transcription drift where proper nouns, dates, and task names are garbled. Set clear expectations with clients that transcription accuracy depends on recording conditions, not the automation.
OpenRouter rate limits at the model tier the client selects can cause delayed or dropped responses during peak usage. Confirm the client's expected message volume before choosing a model tier, and add a fallback response that signals when the assistant is throttled.

FAQ

Can I build this without coding?

Yes. Every connection in this workflow uses credential forms and pre-built tool nodes rather than custom code. The only configuration that requires careful attention is the Google OAuth2 consent screen setup, which follows a documented step-by-step process.

How long does it take?

Most builders complete a working version in under two hours on their first attempt. Repeat delivery for additional clients typically takes 45 minutes once you have a documented setup checklist.

What can I charge?

Pricing is yours to set based on your positioning, the client's complexity, and any ongoing support you include. Productizing it as a one-time setup with optional monthly maintenance retainer is a common packaging approach for this type of deliverable.

Which tool is required vs optional?

Telegram and Gmail are core to the workflow's primary value. Google Calendar and Google Tasks extend it but can be scoped out for clients who only want email assistance. OpenAI is required if the client wants voice input; text-only setups can skip that credential entirely.

This is original DigiNo analysis. The underlying automation pattern is a community workflow template – view the original on n8n.