Schedule tweets: write X posts once, approve them, post on time

What you can post to X through overads

overads posts to X as the account you connect. Connecting X in the app sends you to X's own sign-in, so you approve overads on X and never type your X password into overads. The account then appears in Publish beside your other channels.

These are the rules overads applies to an X post. Limits are checked when you create or edit the post, so an over-limit post is refused at once with a sentence naming the cap, not at the scheduled minute:

• Characters: 280, counted the way X counts: Chinese, Japanese and Korean characters and every emoji count 2, and every link counts 23 whatever its length.
• Up to 4 images, or 1 video up to 512 MB and 140 seconds.
• Media is optional.

That weighting is X's own: most characters count 1, emoji and Chinese, Japanese and Korean characters count 2, and every link is wrapped in t.co and counts 23 (Counting characters). X's composer takes up to 4 media items and lets photos, a GIF and a video mix in one post (How to Post); a post through overads carries images or one video.

Replies and quote posts are settings on the post over the API: replyTo takes the id of the post to reply to, and quoteTweet the id of the post to quote. Those are the only two X settings, so overads schedules one post at a time rather than a thread. The X platform page lists both keys.

How approval works on a scheduled X post

An approval step holds a scheduled X post until a teammate says yes. There are two ways to turn it on, and either one holds the post the same way:

• Per post: switch on approval in the composer when you schedule it. Use this when one post needs a second pair of eyes.
• For the whole workspace: an owner or admin turns on Settings > Rules > Require approval. Every scheduled post then waits, whether you wrote it in the app, the assistant drafted it or a workflow made it, and the composer shows the switch on and locked.

A held post stays scheduled in the approval queue; the scheduler does not deliver it until a member approves it in the app, and it cannot be published early to skip the step. You can edit it while it waits. A member approves in the app; the API and MCP server can create a held post but cannot approve one. Posts that overads workflows draft wait for approval by default. The full rules, including the webhooks that fire when a post enters the queue and when it is approved, are in Scheduling and approvals.

X's own scheduling options and their limits

X documents scheduling in three places, and which you have depends on your X Premium tier and whether you run ads. X Help's How to Post article, which covers the standard composer, describes no scheduling step.

Sources: About X Premium, About advanced X Pro features, Media Studio Library and Scheduled Posts in X Help. X Premium subscribers can write longer posts of up to 25,000 characters, and X says longer posts cannot yet be scheduled (X Premium how to). overads holds every X post to the 280 cap, counted the way X counts it.

Two differences matter most. Each of X's schedulers comes with a subscription tier or an ads account, and overads does not ask which X tier the account is on. X Help describes no review step before a scheduled post goes out, which is the gap the approval step in overads fills.

How to schedule a tweet in overads

1. Connect X from the app and approve overads on X's sign-in page.
2. Write the post in Publish, attach images or one video within the limits above if you want them, and check the X preview.
3. Pick the date and time, and switch on approval if a teammate should read it first.
4. Once it is approved, overads publishes it at that time and the post's delivery log shows the result for each account.

Developers can do the same over the REST API or the MCP server: create the post with scheduledAt and the X connection id, and use twitter, the API id for X, as the key in platformSettings. A member approves it in the app. Bluesky works the same way, with an app password (Bluesky scheduler).

When another X scheduling tool fits better

Choose X's own scheduler or another tool when:

• You want to schedule a thread. overads sends one post at a time, and a reply can only point at a post that already exists on X.
• You post alone, only to X, and already have X Pro, Media Studio or an X Ads account. Those cover it.
• You want analytics on your X post history. overads cannot read a person's post history from X.
• You also need to post to Threads, YouTube and TikTok. Those channels are built in overads but still in each platform's review, and do not publish for customers yet.

overads fits a small team that schedules X posts, wants a teammate to approve them, and posts the same work to its other channels. Plans are on pricing; neither plan caps publishing channels.