
Coming soon. You can’t connect X (Twitter) to Postbean or schedule a post for it here. If you’ve promised an announcement on X this week, plan to publish it directly on X. Use Postbean for the versions going to accounts you can already connect, and give the X version its own line in your editorial plan.
Where to check whether X is available
In your Postbean workspace, open Connections and look for X (Twitter). It shows a Coming soon badge instead of a connect button. That badge is the status to check when you’re deciding how to send a campaign. Seeing X listed doesn’t mean it can receive a post, and signing up doesn’t activate it.
The distinction matters if someone else will post on launch day. In a shared brief, write down who owns the X post and where they’ll publish it. A planned time in your brief is an assignment, not an entry in the Postbean publishing queue for X.
What the X code does, and what it doesn’t mean for your account
Postbean has code to authorize X accounts and send a single post. The publisher can send text on its own or upload images or a video and attach them. It has a path for waiting on video processing when X requires it. That’s more than a text-only implementation, but it isn’t evidence that you can connect an account or that a particular file will publish today.
Postbean’s platform rules set the X text limit at 280 characters and don’t enable an automatic first comment. The publisher creates a single post; it doesn’t build a thread by chaining replies. Postbean also doesn’t sync live X metrics. Treat these as descriptions of the current code, not a list of features you can turn on for X.
Write the X version for someone who hasn’t seen your other posts
Start with what changed. If you’re announcing an update to a recipe app, “You can now scale a recipe to any serving size” gives readers more to work with than “Our biggest update is here.” Add a link to the release notes if it helps them act. If you’re sharing a short clip, show the serving-size control in use rather than making viewers sit through a branded intro first.
Keep the main idea in the opening post even if you want to follow up with a reply. Use replies for a detail that can stand separately, such as the platforms where the feature is available. Leave yourself enough room to check the actual text and media in X’s composer before publishing. The X Help Center’s posting guide walks through composing a post on the web and in the app.
Run one announcement across two workflows
- Write the launch fact, the destination link, and the time in a brief. Put the X copy and its attachment there so the person posting it isn’t pulling assets from a chat at the last minute.
- Open the Postbean composer to prepare the versions for connected accounts. A Threads post might ask how people handle leftovers; a product update on LinkedIn might explain why the change took time to build. Each version should make sense on its own.
- Check those scheduled posts in the Postbean calendar. Keep a separate reminder for X, open X at the planned time, verify the account you’re posting from, and publish there. After it’s live, put the public link in the brief so teammates know what went out and can find the conversation.
If choosing an active text-first channel is part of the decision, read Threads, Bluesky, and X for brands. If X scheduling is a requirement for the tool you buy, compare Postbean and Typefully before committing to a workflow. Or create a Postbean account to schedule the other versions now, while keeping the X step separate.
Frequently asked questions
Can I connect X to Postbean today?
No. X (Twitter) appears under Connections as Coming soon, without a connect button.
Does Postbean's X publisher only handle text?
No. The code handles image and video uploads as well as text, but the integration isn't available to connect or use.
Can I schedule an X thread or sync X metrics with Postbean?
No. Postbean doesn't currently publish to X or sync its metrics. Publish any follow-up replies directly on X.