X scheduler for products publishing on every other channel too

X publishing happens in bursts around an announcement rather than on a steady weekly rhythm, which is how SaaS products, technical teams, and the agencies and brands behind them actually plan it: short posts, media, reply controls, launch timing, and follow-up content.

bundle.social plans X in the same calendar as every other channel. Draft posts, attach media from the library, set reply controls where the account supports them, schedule around a launch window, and see delivery status without switching tools.

X is the one channel where publishing volume has a direct cost, because X charges per post through its API and a post containing a link is priced differently. Character and video limits also depend on the connected account's subscription level, so the same draft can be valid for one account and too long for another.

bundle.social meters X posting at X's own rate from a prepaid balance and validates each caption against the limit the connected account actually allows. If the balance runs out, X posts pause while every other channel keeps publishing, so a funding gap never becomes a campaign outage.

The same message usually needs a longer LinkedIn version, a Threads post, and a Bluesky post, and the team wants one view of what went out and how it performed.

One calendar holds those channels with per-channel copy, approvals, delivery status, and analytics where the account exposes them. The same workflow is available through the API when X publishing has to be automated inside a product.

X is the one connected account that also needs a balance: posting is metered at X's own per-post rate, so a scheduled X post waits when the credit balance is empty while every other channel keeps publishing.

You generate a hosted portal link, your user connects their own X account through it, and bundle.social stores and refreshes the token. The link carries your branding, expires on a window you set between 5 minutes and 48 hours, and means you never implement X API v2 OAuth yourself. Publishing from your own code instead of the dashboard uses the same connected accounts.