The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Telegram Bot for D&D Session Organization — Party Polls, GM Summary, Rescheduling and Reminders
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.
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.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Just finished building a Salon Booking Management System!
The goal was simple: make appointment management easier for salon owners and reduce the manual work involved in handling bookings and reminders.
The system connects the complete workflow in one place:
1 Customer makes a booking
2 Booking gets confirmed
3 Owner sees it on the dashboard
4 Upcoming appointments are organized clearly
5 Reminders help the owner stay on top of appointments
One of the key things I focused on was making the experience simple, clean, and easy to understand, while keeping the workflow practical for a real business.
This project helped me think beyond just building screens — and focus more on the actual business problem, user flow, and overall product experience.
Excited to keep improving it and turn it into an even more polished product.
#BuildInPublic #SaaS #WebApp #BookingSystem #SalonManagement #ProductDesign #MVP #NoCode #Entrepreneurship
Good work
Marlowe Mobile Detailing
Solo-owner mobile car detailer, Austin, TX (serving Round Rock, Cedar Park, and Lakeway)
Marlowe Mobile Detailing was losing about 1 in 5 bookings to no-shows and running behind on nearly every job. This build replaces a vague "can you detail my car?" text with a fully scoped, weather-aware booking flow that sets an accurate time and price upfront, captures access instructions before he arrives, and automates rain-day rescheduling so he never has to chase a customer again.
He works alone and travels to the customer. Rain cancels outdoor jobs. Customers under-describe how dirty their cars are, so jobs run long. About 20% of bookings were no-shows because people forgot he was coming to them.
The question I ask before automating anything: "What does this look like on a Tuesday in month four?"
Not the demo. Not launch day. Month four, when the person who championed it has moved on, the data has drifted, and the model has quietly started doing something slightly different.
The automations that survive month four have three things: a human somewhere in the loop, a log a non-engineer can read, and a kill switch that doesn't need me. The PO intake agent I posted last week is built that way on purpose. It registers and notifies, people decide, and every email in and out is logged.
If yours has all three, you're fine. If it has none, I'd love to hear how it's going. I collect these stories.
the month four test is so spot on zahid. everyone designs for the launch demo, but silent prompt drift kills more workflows than actual broken APIS.