Telegram Bot Templates

Start from a bot that already works. Import it, send its command, then take it apart and make it yours.

A template is a finished flow you can drop into your bot and pull apart. Import one, send its command in Telegram, watch what happens, then change it into something of your own.

The Welcome starterFree

You do not import this one — it appears by itself when you connect a bot that has no flows yet.

1. The Trigger listens for /start.
2. A Text block greets the person: “Hi {{first_name}}! 👋 Welcome, and thanks for stopping by.”
3. A Buttons block asks what they would like to do, offering About us and Contact.
4. Each button leads to its own Text reply.

Five blocks, all free, deliberately inside the free limits so the flow keeps replying whatever plan you end up on.

Fun FactPro

The smallest possible example of talking to the outside world: /funfact fires an API Call block at a free public facts endpoint, and the block sends the fact it gets back. There is no Text block after it on purpose — the API block already sends the text from the response, and a second block would post the fact twice.

Blocks: Trigger, API Call. Collections: none. Copy this one when you want your bot to answer with live data from somewhere else.

Demo StorePro

/shop shows a menu of three products. Tapping one looks it up in a table and replies with its price and description.

1. Trigger on /shop.
2. A Menu block offers Coffee, Tea and Cake.
3. Every option leads to the same Find Data block, which searches the Products collection for a row whose name equals the label that was tapped.
4. The Found branch replies with {{product_name}}, {{product_price}} and the description; the Not found branch apologises.

Creates: a shared Products collection with columns name, price and description, seeded with Coffee ($3.50), Tea ($2.50) and Cake ($4.00). Swap those rows for your own catalogue and the flow keeps working — the menu labels and the name column need to match exactly.

Demo SupportPro

/help turns a table of answers into a small support desk.

1. Trigger on /help.
2. A Text block asks for one word — shipping, refund or hours — and waits for the reply.
3. Find Data searches the FAQ collection for a row whose keywords column contains what they typed.
4. Found replies with the question and its answer; Not found suggests trying another word.

Creates: a shared FAQ collection with keywords, question and answer, seeded with three entries covering delivery times, refunds and opening hours. Because the match is “contains”, one row can answer several phrasings: the delivery row lists shipping, delivery, deliver and arrive.

What importing actually does

Importing adds a new flow to the bot you have selected. It never overwrites or edits a flow you already built.

• Command already taken? Commands are matched without regard to capitalisation and the oldest flow wins, so a duplicate would never run. The import picks the next free variant of the command instead and tells you which one it used.
• Collection name already used? The new collection is given a free variant of the name, and the notice says so.
• Pro blocks? You are warned that the flow stops replying if the plan returns to Free.

Making it yours

After importing, open the flow in the builder and treat it like anything you built by hand: rewrite the messages, change the command on the Trigger, add branches, or point a storage block at a different collection. The seeded rows are ordinary rows — edit them on the Data tab, delete the demo entries, and paste your own in.

Questions

More guides