Contact Telegram Automation with a build brief
To contact Telegram Automation, send a build brief on Telegram. State the event that should start the workflow, the result you expect, and the bot, channel, or group involved. The reply names the mechanism, the rights required, a price, and a timeframe. Never include a password, a login code, or a session file.
What should a build brief contain?
Five items allow the workflow to be assessed. Plain sentences are enough.
- The trigger: the command, message, new member, payment, time, or outside event that starts the workflow
- The action: what should be sent, deleted, restricted, recorded, or forwarded
- The place: a bot, a channel, or a group, and whether you own it or administer it
- The connected systems, if any: a sheet, a CRM, a store, or a pipeline tool
- The expected volume in words, such as a few messages a day or a broadcast to all bot subscribers
What must stay with you?
No stage of a build requires the following, and the service does not request them.
- The password of your Telegram account or of its two-step verification
- A login code that Telegram sent to you
- A session file or an exported session string from any client
- A bot token in the first message. The token is handed over only after you accept the quote, and you can revoke it in BotFather afterward.
What does the reply state?
-
The mechanism
The reply says whether the workflow runs on a bot, on a built-in admin setting, or on a user-account client, and why.
-
The rights and limits
It lists the admin rights the bot would need and the Telegram limit that constrains the workflow.
-
The quote
It gives a price and a timeframe for that build. If the request falls outside Telegram's rules, the reply says so and no quote is given.
Which requests are declined?
The service declines unsolicited bulk messaging, adding people to chats without their agreement, inflated member or view counts, and any design that depends on getting past a flood limit. Telegram's Terms of Service prohibit spam, and a faster sender does not alter that. The full list is in the boundary section of the home page.
How is the bot token handled?
You create the bot in BotFather under your own account, so the bot and its token belong to you from the first minute. Telegram's bot documentation states that everyone who has the token has full control over the bot. For that reason the token is used only in the deployed configuration, is kept out of chat history where possible, and can be replaced by you at handover.
Telegram Automation is an independent service. A message sent through this page reaches the service and not Telegram or its support team.