Basis pengetahuan GetMyBot

Projects and channels

Create a project, connect Telegram and other channels, understand separate project and channel states, and manage freezes, tokens, and transfers.

Di halaman ini

In GetMyBot, reactions and data belong to a project. You can connect a Telegram bot using a token from @BotFather, plus a web chat and other channels. Open Projects in the left navigation; change the active project in the switcher at the top.

Connecting a bot

  1. If you do not have a project yet, open Projects and choose Add a project. On its row choose Add channel, then Telegram. For your first bot, you can use the onboarding wizard instead.
  2. Paste the token from @BotFather and choose Validate. GetMyBot displays the bot's @username so you can confirm the token is correct.
  3. Choose Connect. The token is encrypted at rest, and update reception starts immediately.

Telegram now appears on the project's row beside its other channels. The row shows the project name, bot @username, users, active reactions, and requests today. See Billing or Statistics for your request balance.

Multiple bots

A single account can manage multiple projects and bots: the number is limited by your plan (the "maximum bots" parameter). Switch projects at the top or on Projects; Reactions, Chats, and Statistics show data for the selected project.

How the bot receives messages

The platform receives updates from Telegram automatically: via webhook or long-polling depending on the instance configuration. No setup is needed on your part: a valid token is sufficient. The bot handles direct messages, group and channel messages, inline button presses, system events (joins/leaves), message reactions, and payments.

Enabling and disabling

Each bot has an enabled / disabled state (the "Bot status" card in Settings). A disabled bot does not respond to messages; the change takes effect immediately without reconnecting.

Project state and channel availability

On Projects, the project lifecycle is shown separately as Active, Paused, or Frozen. This does not measure Telegram delivery. Each channel has its own label: Online, No heartbeat, Configured, Disabled, or Project inactive. An active web-chat project without Telegram therefore should not look "stopped."

If an active project has exactly one enabled Telegram channel, Online means a serving process has checked in recently; otherwise it shows No heartbeat. With multiple enabled Telegram channels, the label is Configured because a project-wide heartbeat cannot be attributed to one of them. For enabled channels on other platforms, Configured means connected, not a guarantee that every message is delivered.

The platform runs as several equal processes rather than one. Each checks in every 30 seconds for the bot it serves. A check-in counts as fresh for a minute and a half so a single missed check-in does not make the status flicker.

What follows in practice:

  • The label lags. After connecting or restarting the platform, "Online" may take up to that window to appear.
  • "No heartbeat" lasting more than a couple of minutes on an enabled Telegram channel is worth investigating: check the token and the "Bot health" card in Settings. The project remains Active unless you pause it or the platform freezes it under your plan.
  • The heartbeat is shared across processes, regardless of which server answered your request. With several Telegram channels it does not prove each one is available separately.

What happens when a bot goes offline

Once a minute the platform checks the heartbeats. When an enabled bot has no fresh one, an incident is opened: the platform determines the cause once and then tries to bring the bot back on its own.

There are four causes, and each of them is shown in the "Bot health" card in Settings:

  • webhook: Telegram cannot deliver updates to the platform's address, so it re-registers it;
  • token revoked: getMe answers 401. Such an incident is not restarted: the token must be reissued in @BotFather and pasted via "Change token";
  • no serving process: nobody is processing updates, so the platform restarts the bot;
  • cause undetermined: Telegram did not answer the probe.

A restart does exactly what the "Sync" button does: it verifies the token with getMe and re-registers the webhook. Attempts are spaced by a growing delay, and each one is written to the incident's restart journal: the time, whether it succeeded, and the error text when it did not. The journal and the time of the next attempt are visible in the card.

When a bot stays silent longer than the threshold in the "Bot health" card (5 minutes by default), the bot's owner gets a "Bot offline" notification in the bell and by email, and the chats in the notification recipients list get a message from the bot itself. One notification per incident; when heartbeats return, "Bot back online" arrives with the length of the outage. The list of past incidents, with duration and cause, stays in the same card.

Freezing by plan

Besides enabled/disabled, a bot has a frozen state. A bot is frozen by the platform rather than by you, when the current plan stops covering the number of connected bots. There are exactly two reasons:

  • the bot limit is exceeded: you moved to a plan with fewer bots than you have connected;
  • the subscription was not renewed: the paid plan ended and the free plan's limit applies.

A frozen bot does not receive messages: update ingestion is switched off for it, not merely flagged. Data, reactions and subscribers are fully preserved: freezing is reversible.

How to unfreeze. Pay for a plan covering the number of bots you need. Unfreezing happens by itself the moment the paid plan is activated: bots return to service oldest first, until the new plan's limit is filled. You cannot choose which bot comes back; if you do not want the oldest ones, delete the surplus connections and pay for the plan afterwards.

Separately from a bot freeze there is a freeze of the whole account: then every bot and broadcast is suspended at once and the dashboard shows an "Account frozen" banner. Only support can lift it. See Payments and balance.

Profile and synchronization

The Synchronize button in Settings updates the bot's name from Telegram (if you renamed it in @BotFather). The bot's avatar is pulled in automatically.

Changing the token

If you regenerated the token in @BotFather (Bot Settings → Revoke / New token), update it in Settings → Change token. The new token must belong to the same bot (matching the internal Telegram ID): this preserves all reactions, subscribers, and data.

Transferring a bot to another account

Settings → Change owner transfers the bot to another GetMyBot account by email. This action is irreversible: after the transfer you lose access to the bot. Use this when handing a project off to a client or colleague.

Bot templates

A template is a snapshot of the bot's settings and all its reactions that can be applied to another bot:

  • Create template (in Settings) saves the current bot as a named template.
  • Apply template replaces the target bot's settings with those from the template and adds the template's reactions to the existing ones (without overwriting them).

This is convenient for rolling out a standard bot across multiple projects.

What's next