Skip to content
Widgram

How to use the builder

A widget in Widgram is built from a ready-made template: you change the texts and the behavior, and we take care of the code, the server and the delivery. Below is the path from a template to a link.

1. Pick a template

The gallery has nine templates. You can try each one without signing up: it runs right on the page.

  • Poll — A question with two to six options. Everyone sees the results, and they update live.
  • Quiz — One to eight questions with answer options. The server checks the answers; at the end comes a level by score and, optionally, a promo code.
  • Promo code — A button reveals a promo code, and a tap on the code copies it. Unique codes from your list or one shared code, with a limit and an expiry.
  • Countdown — A countdown to an event. When the time is up, the widget shows another text and a link button. The date can be moved after sending.
  • Giveaway — A “Join” button and a live count of participants. At the set time the server picks the winners and the bot messages them.
  • Wheel of fortune — A wheel of 4–8 sectors with prizes. The server picks the outcome by your weights; people spin once or once a day.
  • Rating — A rating from one to five stars or on the NPS scale from 0 to 10. After the rating you can ask for a reason.
  • Order status — Order steps with the current stage. The stage, a note and the expected time are updated through the API without resending.
  • One-tap lead — An offer card with a request button. The name and username come from Telegram, and you get a notification.

2. Set it up

The editor opens in the cabinet; you sign in through the bot in Telegram, with no passwords. The settings are split into the “Content”, “Behavior”, “Look” and “Message” tabs. Changes are saved automatically.

  • The “N of 4,096 bytes” meter shows how much room the widget takes after compression.
  • Setting errors appear next to the field: a text that is too long, a required field left empty.
  • The message caption is required: people see it in the chat list and wherever widgets are not supported.

3. Check it in the emulator

Next to the settings the widget runs in a message bubble. You can switch the theme, the bubble width, the text size and the “viewer”, to see the widget as another person does. Taps go to the real engine, but into a sandbox: votes and issued codes there are not real and are cleared with a button.

The emulator is approximate. The Telegram app is the reference.

4. Send it to yourself and publish

  • “Send to myself in Telegram”: the bot sends the widget to your private chat so you can see it in the real app.
  • “Publish” creates a version of the widget and a link like t.me/<bot>?start=<widget code> with a QR code. A person opens the link, taps “Start” and gets the widget in the private chat with the bot.

The code of messages already sent cannot be changed: that is Telegram's rule. A new version reaches new messages only; votes and issued codes are kept.

5. Watch the results

  • Statistics: sends, views, actions and the number of different people by day; the spread of answers.
  • Leads: a list with the name and username from Telegram, with CSV export.
  • Promo codes: your own list of codes for the “Promo code” and “Wheel of fortune” templates; one code is never issued twice.

Views are counted only for widgets that send requests to the bot: for the rest there is technically no way to learn about a view.

Your own HTML

If you write a widget yourself, the code check works without signing up: it shows what the app will remove, compresses the code, counts the size and runs the widget in the emulator. The same compiler is available through the API without a key: POST /api/v1/compile, up to 10 requests a minute from one address.

In the dashboard your own code has a separate editor: the “Write your own code” button in the widget list. The code compiles by itself while you type: findings are shown line by line, the meter shows the size after compression, and the widget runs in the emulator on the right.

  • On any plan: the editor, the emulator, compilation and copying the ready code — you can send it with your own bot using sendWidget.
  • “Send to myself in Telegram” — after the automatic code check: no wallet calls, no links to outside hosts and no signs of phishing.
  • Publishing by link — from the Start plan.
  • The manifest — a tab next to the code: allow the widget to make requests and describe what the server does in response with ready actions (a vote, a counter, a promo code, a random outcome, an answer check, a lead). An empty manifest is a static widget.
  • AI — the “AI” tab: describe the widget in words, the model writes the code, and the compiler checks it and asks for fixes. Generations are counted per plan. The feature is built but has not been checked on the real model yet.

The other API methods — sending widgets, state, statistics, leads, outgoing webhooks — are described on the API page; they work on paid plans.

Your own bot

By default a widget link leads to a chat with the Widgram bot. From the Start plan you can send widgets on behalf of your own bot, so the person stays in your chat. In the dashboard this is the Bots section; the bot for a link is chosen on the Share page of a widget.

  • Create a new one. In the chat with our bot the /bot command shows a “Create a bot” button: Telegram creates the bot and hands it over to the service. There is no token to enter.
  • Full mode. For a bot that has no other server: you paste the token and the webhook becomes ours. The bot answers /start with a greeting you set yourself.
  • Proxy (from the Pro plan). For a bot that already runs on another service: we handle the queries of our widgets and the links to them, everything else goes to your server unchanged, and its response is returned to Telegram as is.
  • Send only. We do not touch the webhook. Widgets are sent from the dashboard and the API; there are no widget links and no broadcasts in this mode.

Before changing anything the dashboard shows which webhook the bot has now, and it never silently overwrites someone else's webhook. When you disconnect the bot, the previous webhook is restored and the token is deleted.

Broadcasts

From the Pro plan you can send a widget to the people who have already used your bot: everyone, those who came in the last few days, or those who tapped in another widget. A broadcast only goes through your own bot, right away or on a schedule, and no faster than Telegram allows. Before it starts the dashboard shows the number of recipients and checks that they fit the MAU limit; a broadcast can be paused and resumed.

What is not there yet

We do not promise what is not built. Planned:

  • Paid subscription. Paid plans. Payment in Telegram Stars is built; card payments are planned.
  • A widget from a description. Describe a widget in words; the model writes the code, and the compiler checks it and asks for fixes. Built into the custom HTML editor; the quality on the real model has not been measured yet.