Appearance
X (Twitter) integration
Studio generates X variants from your articles and holds them in the distribution queue alongside every other channel. Automatic publishing to X is not wired up today. The post is written for you and you publish it.
We would rather say that here than let you discover it after wiring up a queue.
What the X integration supports today
| Capability | Status |
|---|---|
| Generated post variant | Yes |
| Approval queue | Yes |
| Scheduling | Yes, as a reminder rather than a publish |
| Automatic publishing | No, manual |
| Image generation | Yes, and the image is attached to the queued item |
What the X integration can be used for
X can be used for consistent post drafting, so the copy is written whether or not anyone has time to write it.
X can be used as part of one editorial queue, reviewed in the same place as the channels that do publish automatically.
X can be used with tracked links, so the traffic it does bring is attributed properly even though the publish is manual.
X combined with other integrations
| Combination | What it gives you |
|---|---|
| X + content pipeline | The post is written on publish, ready to paste |
| X + Bluesky | The same short-form idea, published automatically on the channel that supports it |
| X + first-party tracker | Attribution for the traffic, regardless of how the post got there |
Want automatic publishing?
X is on the integration roadmap. If it is blocking you, tell us and it moves up the list. You can also publish to X yourself today through webhooks or an n8n workflow triggered by a playbook step.