Is Automation Allowed on X? 6 Things the Rules Allow and 6 They Ban (2026)
Is automation allowed on X?
Yes, for posting. X’s automation rules (the version marked “Updated April 2026”) allow automated posts “for entertainment, informational, or novelty purposes” and automated cross-posting from outside sources such as an RSS feed, as long as the content is not duplicative or spammy. What the rules ban is automated engagement: keyword-triggered replies, automated likes, bulk following and unfollowing, auto-posting about trending topics, and any automation that scripts the X website instead of using the API. Below are the six things the rules allow, the six they ban, the two that need consent or approval, and where a Telegram scheduler fits.
The rules in one table
| Activity | Status under X’s automation rules | Condition |
|---|---|---|
| Scheduled or automated posts | Allowed | Entertainment, informational or novelty purposes; not duplicative or spammy |
| Cross-posting an RSS feed or data source | Allowed | You must be authorised to publish that information |
| Automated replies and mentions | Conditional | Recipient opted in first; one reply per interaction; easy opt-out |
| AI-generated automated replies | Conditional | Prior written and explicit approval from X |
| Automated likes | Banned | No exception listed |
| Bulk or aggressive follow/unfollow | Banned | Apps that promise more followers are also prohibited |
| Scripting the X website | Banned | “May result in the permanent suspension of your account” |
6 things the automation rules allow
- Automated posts on your own account. Provided you comply with the other rules, you may post automated posts for entertainment, informational or novelty purposes. A queue of posts you wrote and scheduled is the plainest case.
- Cross-posting outside information. Posts generated from an RSS feed, weather data or a similar source are allowed “as long as you are sufficiently authorized to publish such information.” Your own blog feed qualifies; someone else’s paywalled articles do not.
- Auto-replies to people who opted in. A campaign can reply automatically to users who replied to your post or messaged you, with one automated reply per interaction and a clear way to opt out. Following your account is not enough to count as opting in.
- Automated Direct Messages to people who asked. Allowed when the recipient requested contact first and can opt out. Being technically able to receive your DM is not the same as asking for it.
- Automated Reposts and Quote posts. Permitted for entertainment, informational or novelty purposes, but the rules warn that bulk, aggressive or spammy Reposting violates the X Rules.
- Several automated accounts with different jobs. Automating multiple accounts is fine when the use cases are related but not duplicative; X’s own example is separate accounts that post when the Hubble Space Telescope passes over different cities.
6 things the automation rules ban
- Auto-posting about trending topics, or using automation to influence or manipulate trends.
- Duplicative or substantially similar posts on one account or across accounts you operate. This is the rule a recurring post loop can break, which is why our rules for evergreen post loops scheduled from Telegram rotate the copy.
- Unsolicited automated replies and mentions, for example “sending automated replies to posts based on keyword searches alone.”
- Automated likes and hiding replies. The rules allow no automated liking at all.
- Bulk, aggressive or indiscriminate following and unfollowing, plus bulk-adding users to lists or posts to collections.
- Non-API automation, such as a script or browser extension that clicks through the X website for you.
Two general bans sit above all six: automation may not spam people with unsolicited messages, and it may not abuse the API or try to get around its rate limits. If you build your own tool, our breakdown of X API rate-limit budgets for Telegram schedulers shows how to stay inside them.
The two that need consent or approval
Acting through someone else’s account. A user authorising your app through OAuth “does not by itself constitute sufficient consent” for automated actions. You must describe the automated actions, get express consent, honour opt-outs immediately, and ask again if the app’s purpose changes substantially. For a scheduler, that means the user picks what gets posted and when; the tool does not decide on its own to post, follow or delete.
AI reply bots. Using AI to generate automated replies is allowed only with prior written and explicit approval from X. Writing a post with AI and scheduling it yourself is a different thing: it is a post, not an automated reply, and it falls under the first rule above.
Where a Telegram scheduler fits: Auto X, honestly
Auto X in one line: a Telegram bot, made by us at GSPTeck, that schedules and auto-publishes the text and media posts you send it to X. Its listed features:
- Schedule text or media posts for a date and time, and view or cancel them with /queue.
- A one-time OAuth connection to X, with tokens encrypted and refreshed automatically.
- Post loops on daily, weekly or custom intervals (Pro and above).
- AI generation of text, image or video before you schedule (Ultra).
Mapped against the rules: scheduling your own posts is allowed by rule 1 of the first list. Loops are allowed only if each run does not repeat the same or nearly the same text, so rotate variants; our guide to duplicate-content fingerprint guards shows one way to check. AI generation produces drafts you approve and schedule, not automated replies. None of the listed features like, follow, auto-reply or send DMs, so the banned engagement categories do not apply. You can see the full plan list on the Auto X homepage, where the Telegram bot is one tap away.
| Option | Uses the X API? | Fits the rules when… | Trade-off |
|---|---|---|---|
| X’s own post scheduler | Native | Always, for your own posts | Built into the X composer; no Telegram workflow, no loops |
| Auto X (Telegram bot, ours) | Yes, via OAuth | Loop copy varies; content is yours | Loops need Pro; AI needs Ultra |
| Browser-automation scripts | No | Never: scripting the website is banned | Risk of permanent suspension |
| Follow/like “growth” bots | Varies | Never: automated likes and bulk follows are banned | Suspension; follower-growth apps are prohibited |
A five-minute check before you automate anything
- Name the action. Post, reply, DM, Repost, like or follow. Likes and bulk follows stop here.
- Check the route. Official API through OAuth, or a script on the website? Only the first is allowed.
- Check the trigger. A schedule or feed you control is fine; a keyword search or a trending topic is not.
- Check repetition. Would two runs produce nearly the same text? Rotate the copy or space it out.
- Check consent. If the action reaches other people, did they opt in, and can they opt out?
If you are new to scheduling from Telegram, our step-by-step guide to scheduling X posts from Telegram covers the setup itself.
What X does when automation breaks the rules
The rules list the responses: filtering your posts from search, removing posts from Search, suspending the app or the account, and for developers, rate-limiting, suspending or terminating API access. X also states that you are “ultimately responsible for the actions taken with your account, or by applications associated with your account,” so check what a third-party tool does before you authorise it.
FAQ
Is it against X’s rules to schedule posts?
No. Automated posts for entertainment, informational or novelty purposes are allowed, and scheduling your own posts is the simplest example. The limits are duplicate content, spam and trending-topic automation.
Can I use a bot to auto-like or auto-follow on X?
No. The automation rules say you may not like posts in an automated manner, and they ban bulk, aggressive or indiscriminate following and unfollowing. Apps that claim to get you more followers are also prohibited.
Are AI-written posts allowed on X?
A post you generate with AI and then schedule yourself is treated like any other automated post. AI-powered automated reply bots are different: they need prior written and explicit approval from X.
Can I repost the same evergreen post every week?
Not word for word. The rules ban duplicative or substantially similar posts on one account, so rotate several genuinely different versions and space them out.
Sources
- X Help Center: automation rules (version marked “Updated April 2026”, checked 2026-10-19)
- X Help Center: platform manipulation and spam policy (checked 2026-10-19)
- X API documentation: create a post (checked 2026-10-19)
- X API documentation: OAuth 2.0 authorization code flow (checked 2026-10-19)