An X automation watches one X account or phrase and posts what it finds into one authorized Telegram group, using its own message preset. A bot holds up to 10 at once.
Beta
X automations are currently in beta.
Each automation has its own settings, image and message text, even when two point at the same group.
The "Which automation?" picker
| Card | What it watches |
|---|---|
| Posts from Feed | Every new post from one account |
| Phrase Filter | Every new post on X containing a phrase |
| Follow Tracker | Every new account one account follows |
Deleting an automation removes it permanently, along with its image and message preset.
The master switch pauses and resumes every automation on the bot together. Default: off. A paused automation keeps its settings and comes back as configured.
Two ways to flip it
| Where | Effect |
|---|---|
| Dashboard → Beta → Automations — the Automations on / Automations off toggle | Restarts the bot |
/menu → Extra Bot Features → Automations → On / Off | Takes effect within 5 seconds, no restart |
Note
Flipping the switch from the dashboard restarts the whole bot — a brief interruption for everything it does. The Telegram menu path does not.
Turning automations on, changing an automation's source, or restarting the bot all mean from this moment. Older posts are never replayed.
There is no per-automation switch — only the master switch. While it is off nothing is checked; when it comes back on, posts published while it was off are not announced.
What counts as the source
| Type | Source |
|---|---|
| Feed, Follow tracker | The tracked handle |
| Phrase | The phrase, the minimum-follower gate, or the check-mark gate |
Changing anything else — message, image, link, buttons, rules, recap or topic — does not reset it.
No Telegram command creates or edits an automation — that is done on the dashboard. The only automation control in /menu (also /options, /help) is the master switch above, for the bot's owner or a Memescale admin. Anyone else who presses it gets Owner / admins only.
An automation's destination group must already be authorized for the bot before it can be picked.
Warning
Deauthorizing the group stops every automation posting into it, with no message in the group.
Reauthorizing the group resumes its automations from that moment; nothing from the gap is announced.
The bot must be fully set up before an automation can be created; otherwise the dashboard answers Bot webhook server not configured.