Connect X (Twitter) to SiteOps
The honest part first, because it changes how X used to work: you no longer buy your own X developer plan. X closed its self-serve Basic tier to new signups and moved posting to pay-per-use, so SiteOps runs X through one shared, approved app and meters what you actually publish. There is no $200 monthly bill, no developer portal, and no keys to copy — just a sign-in.
Connecting is a single click. Press Connect on the X row, sign in as your brand on X's own window, and allow posting. That is the whole setup — SiteOps holds the approval, and you can revoke it any time from your X account's connected apps.
What it costs is metered and small: each post SiteOps publishes for you carries a few cents of X usage — about $0.20 per post that includes a link — billed through your SiteOps plan, so you pay only for what goes out. Reads (views and likes on those posts) come back at no extra charge.
Once connected, SiteOps publishes the posts you approve — trimmed to X's real 280-character limit automatically — and reads back how each one did. Drafts wait in the Posts tab, including the ones your calendar events and routines order; approved ones take a Calendar slot and go out without you opening X.
What an X post carries
The 280-character cap is the whole mental model. Every draft is trimmed to fit before it reaches your review, with the meter showing exactly how much room is left, and an image or video can ride along.
Set it up, step by step
0 of 5 done
- Settings
- X (Twitter)
- Connect
Let an agent do it
There is nothing fiddly for an agent to do here any more — connecting X is a single sign-in you do yourself, with no developer portal, keys or billing to set up.
Connecting X is a one-click sign-in inside SiteOps — there is no developer-portal work for an agent to automate. In SiteOps Settings, press Connect on the X row, sign in as your brand in X's window, and press Authorize app. That is the whole setup.Signing in to X and authorizing SiteOps to post are yours alone — an agent cannot accept X's terms or sign in as your brand for you. The good news is there is nothing else: no keys, no tier, no portal.
If something does not work
- Do I still need to pay $200 a month or set up a developer app?
- No — that changed. X closed its self-serve Basic tier to new signups and moved posting to pay-per-use, so SiteOps runs X through one shared, approved app. You connect with a single sign-in, and instead of a monthly bill you pay a few cents per post (about $0.20 for a post with a link) on your SiteOps plan.
- How much does posting to X actually cost me?
- It is metered per post, not monthly. A post that includes a link runs about $0.20; you only pay when something publishes, and reading back views and likes is included. If your X budget is zero, Threads and Bluesky do the same job for free.
- Posts fail with a permission error even though the connection is green
- The authorization was likely issued without posting permission, or the token expired. In SiteOps Settings, disconnect X and press Connect again, then make sure you press Authorize app (not just sign in) in X's window — that is the step that grants posting.
- Why does SiteOps handle the X app instead of me?
- Because X no longer sells the self-serve tier a per-tenant app needed, and pay-per-use runs cleanly through one approved app. You still own the account and the approval — revoke SiteOps at x.com under connected apps at any time and posting simply stops.