17 NOV 2026 / Written by Lukas / 2 MIN READ

I accidentally gave our Telegram bot side quests

I’ve been messing around with n8n, Telegram and Ollama, and things have escalated slightly.

On this page

The original idea was pretty sensible: send Mick a morning reminder with public transport information for his commute. Bus connections, delays, that sort of thing. We also added a daily fun fact, because a notification containing nothing but transport problems is a bit depressing.

Then I wanted meal prep suggestions.

Then the bot became a Shiba oracle.

Normal progression, really.

Jay’s Telegram Commands

The useful bit

We need lunches for two people across five workdays. Ideally stuff we can freeze, thaw overnight and reheat at work. No seafood, no soup leaking into someone’s bag.

So now /mealprep asks our local Ollama model to pick three options from a small collection of checked recipes. Each option comes with a recipe link and instructions for scaling it to ten portions.

There are vegetarian, cheap and quick options too. Although “quick” is doing some heavy lifting when you’re cooking ten lunches.

Meal-prep response

Then I started adding nonsense

The bot now also has:

  • /fact — an animal or Leipzig fact, with a source.
  • /quiz — a trivia question with answer buttons.
  • /quiz scores — a shared leaderboard, because apparently we need competitive animal knowledge.
  • /tinyquest — a small, silly mission involving household objects or imagination.
  • /fortune — wisdom from a completely unqualified Shiba oracle.

The facts and quiz answers come from a checked collection. Ollama handles the creative nonsense.

During testing, one fortune involved the moon being a confused squirrel wearing socks and a garden of glittering kibble growing inside a toaster.

I’m choosing to consider that a successful integration.

Shiba Oracle

Shiba Quests

The slightly annoying bit

My n8n instance has a private hostname, which Telegram can’t reach.

We ended up adding a little outbound listener alongside n8n. It checks Telegram for commands and passes them into the workflow over the internal Docker network. n8n gets to stay private, and the bot gets to dispense nonsense.

There’s now one general JayProtoBot workflow routing everything, with /help listing the commands. Codex helped put the whole thing together through n8n’s MCP connection, with some SSH work for the listener.

N8N Workflow

It’s still a small household bot. The recipe and trivia collections could use more entries, and it currently only answers in our group.

But it can help organise lunch and award me an imaginary golden spoon for naming clouds.

Pretty happy with that.