Build a Telegram Bot That Generates QR Codes
QR codes have become a daily tool in Australia, used for everything from checking in at the local café in Brunswick to scanning the menu at a pub in Surry Hills. Small business owners in Adelaide and Perth have embraced them for contactless ordering, and tradies around Brisbane now share job quotes through scannable images. Creating a Telegram bot that generates QR codes gives you a flexible tool you can pull up on your phone wherever you are, whether you're at a market stall in Fremantle or sitting in a coworking space in the Sydney CBD.
Telegram has carved out a solid niche in Australia, partly because of its strong privacy controls and partly because it handles media files and bots exceptionally well. Many Australian Telegram users rely on the platform to manage community groups, share news about the footy, or coordinate flash sales for a side hustle. A bot that lives inside the app can be reached instantly without anyone having to download a separate utility or visit a website.
Building such a bot does not require a server farm in Mascot or a fancy corporate plan. A modest cloud instance, a few lines of code, and a free Telegram API key are enough to get you up and running. Once finished, the bot will reply to plain-text commands with a square image containing the encoded URL, contact card, Wi-Fi login, or any other string you need to share.
This walkthrough covers the whole build, from registering the bot through BotFather to picking a QR generation library and handling edge cases. The same approach can also be extended to countdowns, polls, or a next lunar event guide for astronomy groups in Hobart or Melbourne. By the end you will have a working tool and a clear sense of where to take it next.
Setting Up BotFather and the API Token
The first step is to talk to BotFather, Telegram's official account for issuing bot identities. Open Telegram on your phone, search for @BotFather, and send the /newbot command. The system will ask for a friendly display name and a unique username that ends in "bot". Once accepted, BotFather returns an HTTP API token, which is effectively the password your code will use to authenticate.
Store that token somewhere safe. Treat it like the keys to your ute; if someone copies it, they can impersonate your bot and run up against rate limits. A common pattern is to keep the token in a .env file or environment variable rather than baking it into the source. This way, when you move the project from a local laptop in Collingwood to a cloud server in Singapore or Sydney, only the environment changes.
While BotFather is open, it is worth setting a profile picture, a short description, and an about line. Many Australian users will discover the bot inside public directories, so a clean avatar and a clear one-liner explaining "I turn text into QR codes" helps with click-through. Take a few minutes to wire up a /help command and a /start message so that the bot feels responsive from the very first interaction.
Choosing a Language and Runtime
Python is the path of least resistance for most Aussie developers, partly because the python-telegram-bot library is mature, and partly because every QR generator on PyPI has been tested in production somewhere. Node.js is a close second if you already maintain a JavaScript stack or you prefer asynchronous code for handling bursts of traffic during a flash sale in the Pitt Street Mall.
The choice matters less than people think. What matters is the runtime's ability to send back image data quickly. Both languages can do this in under a second on a typical home NBN connection, and both can be hosted cheaply on platforms that charge in Australian dollars. A $5 to $10 AUD instance is more than enough to handle a few thousand requests a day, which covers most small business or community use cases.
A quick comparison helps frame the library options:
| Library | Language | Strengths | Best For |
|---|---|---|---|
| qrcode | Python | Simple API, mature | Beginners, small bots |
| Segno | Python | Logo support, structured output | Branded QR codes |
| qrcode-generator | JavaScript | Pure JS, no canvas needed | Serverless functions |
| go-qrcode | Go | Fast, single binary | High-traffic deployments |
The right pick depends on the deployment target. Python with qrcode is the easiest path for someone spinning up a side project in a Brisbane garage. Segno shines when branding matters. JavaScript libraries are friendly if the rest of your infrastructure is already in the browser. Go belongs in setups that need to chew through thousands of codes per minute.
Generating the Code That Does the Work
The core logic is small. Take the text the user sends, pipe it through a QR encoder, and return the result as a PNG photo. In Python this looks like importing qrcode, calling qrcode.make(payload) on a BytesIO buffer, and passing the buffer to the bot's send_photo method. In Node, the flow is similar: build the data matrix, draw it into a canvas, export to buffer, and reply with that buffer.
Adding a few command patterns keeps things tidy. A /wifi command can take a network name and password and format them as a WIFI:T:network;S:name;P:password;; string, which scanners recognise natively. A /vcard command can produce a contact card that drops straight into someone's phone. These small touches turn a basic generator into something genuinely useful for tradies in the suburbs of Logan or baristas running pop-ups in Geelong.
Common payload formats worth supporting:
- Plain URL for menu links, ticket pages, or product details
- WIFI strings for cafés, share houses, and home networks
- vCard blocks for digital business cards shared at conferences
- Email mailto links with subject lines pre-filled
- SMS shortcuts that pre-write a message to a phone number
- Geo coordinates for trailheads, boat ramps, and lookouts
A bit of error handling prevents the bot from crashing when a user pastes a five-thousand-character essay. Cap input length, validate that the string is not empty, and respond with a friendly Aussie-style message if something goes sideways. A gentle "Looks like that string is too long, mate" keeps the tone approachable.
Hosting, Testing, and Going Live
Before pointing a real domain at the bot, test it locally with a tunnel such as ngrok, which exposes your laptop to Telegram's webhooks. Send a few test messages from your own account, check the round-trip time, and confirm the image renders correctly across both Android and iOS. Australians tend to use a mix of devices, so testing on at least one of each is wise.
When you are satisfied, deploy to a small VPS or a platform-as-a-service provider. Sydney-region servers give you the lowest latency for Australian users, and a $7 AUD tier is plenty for the load. Set the webhook URL to the endpoint provided by your hosting platform, and verify through BotFather that the bot is receiving updates. If something breaks, Telegram's getWebhookInfo command shows you the last error code and timestamp.
Do not forget the housekeeping. Rotate the API token every few months, especially if you have shared it with collaborators or contractors. Add a tiny usage log so you can see how many QR codes the bot produces per day. A flat-file log is fine for a hobby project, but if the bot is supporting a real business on Brunswick Street, a proper database becomes worthwhile.
Practical Uses Across Australian Industries
A QR-generating bot fits naturally into workflows that already live on phones. Real estate agents in Parramatta can fire off a QR code linking to a property listing while standing in front of the open home. Coffee roosters in Fitzroy can print QR codes on their bean bags that take customers to brewing guides. Event organisers in Adelaide often use bots to send ticketing links, and the same group might maintain a broadcast list of subscribers for last-minute schedule changes.
Other practical applications include generating QR codes for menus at corner pubs, sharing Wi-Fi details with guests at a B&B in the Barossa Valley, or printing tracking links on parcels sent from a small warehouse in Alexandria. Charities running sausage sizzles at Bunnings use bots to share donation pages on the spot. Each use case shares the same underlying code path, so once the bot is live, adding new features takes minutes rather than days.
Growing the Bot Beyond QR Codes
Once the core generator works, it is tempting to keep adding features. Inline queries let users summon a QR code without even opening a chat, which is handy for group conversations. Group admins in community Telegram rooms, such as those listed in an Australian Telegram group directory, can drop QR codes for polls, sign-up forms, or shared documents.
Other extensions to consider:
- A history command that recalls the last few codes generated by a user
- A custom-domain option that shortens long URLs before encoding them
- A button that emails the QR code as a PDF for printing
- An analytics hook that tracks how many times the encoded URL is opened
- A language toggle for Mandarin, Vietnamese, or Arabic, since many Australian suburbs are wonderfully multilingual
- A scheduled mode that posts a fresh QR code to a channel every morning
Marketing the bot is its own small project. Drop the link into relevant Australian Telegram groups, mention it in a Reddit thread about local SaaS tools, and ask a few small business owners around the Queen Victoria Market to try it out. Word spreads fast when a tool genuinely saves time at the counter or on the tools.
Give the bot a memorable username, keep the tone friendly, and ship the first version quickly. Australians value tools that just work without a manual, and a QR-generating bot that responds in under a second fits that brief. Build it today, send the first code to a friend in Perth, and see where the project takes you next.