Business Outcome

<aside> 💡

• Problem: A D&D game master runs several parties of 4-5 players, each in its own Telegram group. Every week he had to ask manually who is coming, chase people who stay silent, and renegotiate when a session falls apart.
• Before: Manual polls in every chat, answers lost in the conversation, and every reschedule or cancellation announced to each party by hand.
• What was built: A Telegram bot on n8n that creates the next session from a fixed schedule, polls the party with Yes / No buttons, sends the GM a summary with decision buttons, reschedules or cancels the session, and sends reminders.

Result: First paid project. The MVP was delivered and tested in a live test chat with the GM. The GM sets up a party with one command, and the bot runs the whole session cycle on its own: from the poll 48 hours before to the reminder 2 hours before.

</aside>

First commercial project: a session-organizer bot for a game master, built from two n8n workflows and four Data Tables, with no paid APIs.

Project Details

Context:

• Client: tabletop RPG game master (D&D 5e 2024), 2 active parties, planning to grow to 3-4.
• Format: paid project, MVP with follow-up modules.
• Requirements: everything inside Telegram, Kyiv time, bot interface in Ukrainian.

Problem:

• Weekly manual collection of answers across several chats.
• No single view of who is coming and who is silent.
• Every reschedule meant another round of messages.

Solution

<aside> 🧠

Two n8n workflows. DnD Router receives everything that reaches the bot (commands, button clicks, a new time from the GM); one Code node turns the event into a list of actions, and a Switch routes them to executor nodes. DnD Scheduler runs every 10 minutes, creates the next session from the schedule and sends whatever is due. State lives in four n8n Data Tables.

Tools: n8n (self-hosted on PikaPods), Telegram Bot API (inline keyboards, callback queries, HTML mentions), n8n Data Tables, JavaScript + Luxon.

</aside>

Solution logic: