Bring X timelines, posts, and buttons to your Confluence pages
Paste an X link into Confluence and you get a bare card, a title and a favicon. Add the macro and the page renders the content itself: your profile or List timeline, a post with its media, a follow or message button.
- Hosting
- Cloud & Data Center
- Pricing
- Free to 10 users on Cloud
- Support
- EU-based, CET hours
- Vendor
- On the Marketplace since 2016
A timeline that is still there tomorrow
Store an X API key once, and the app fetches your profile or public List itself and caches the result, so every reader sees recent posts. Confluence’s own Widget Connector and any HTML macro leave that fetch to each reader’s browser, which is where X’s limits break it.
The post, not a picture of it
Paste a link and the macro detects what it is. Readers get the post itself, text they can read and links they can click, laid out the way you set it in the editor and previewed before you save. A screenshot freezes the moment you took it. The embed does not.
One click to follow, share, or message
Add follow, share, hashtag, and message buttons inline. They render as Confluence-styled links and open X only when a reader clicks.
What runs where, and who sets it up
Who has to do what, and what the app handles on its own.
The app is a Confluence macro
There is no second tool to adopt and no extra tab. An author adds it to a page the way they add any other macro, then picks what to embed from the app's own list.
Only an admin holds the X credentials
The token sits on a Configure page that page authors and readers cannot open. The app tests it against X before it saves, and one entry covers the whole site.
Timelines are fetched by the app, not by the reader's browser
The app calls X from its own backend, stores what comes back, and serves later readers from that copy. An admin chooses how long a copy lasts, from one hour up to a week. A day is the default.
A reader never gets an unexplained blank
When X returns nothing, the app keeps showing the copy it already has. With no token it falls back to X's own widget, and if that fails too it shows a card that says what happened and links to the post on X.
Keys, cost, privacy, and hosting
Do we need an X developer account, and what will X charge us?
Only timelines use the X API. An admin creates an app-only token in X's developer portal and pastes it in once. Nobody connects a personal X account, and readers never sign in. X bills that account directly, per post read, and reading the same post again inside a day usually counts once. You can cap the spend in X's own console. Posts and the buttons never call the API, so they add nothing to that bill. See X's published API rates.
What leaves our Confluence when an embed renders?
No Confluence identity. The app stores no personal data and holds no reference to an Atlassian account. The domains it may reach are fixed in the app itself, and your admin approves that list when they install it. Widening it later takes a new major version and a fresh approval. Every widget the app builds carries X's Do Not Track attribute, so X does not use the embed for personalized ads or suggestions. That does not stop X seeing the request: a post or a clicked button still loads from X, with the reader's IP address. On a page whose only X content is a timeline served through the API, no X script runs in the reader's browser at all.
If we remove the X token later, do the pages go blank?
No. Timelines the app has already stored keep showing until that copy expires. After that they load the way any other X embed does, in each reader's browser, and that path is best effort: a profile timeline usually renders, a List usually does not. The token is what makes both dependable. Anything that never used the token is unaffected.
Do we have to take on a new supplier to buy this?
No. Atlassian sells and bills the app, so it lands on the Confluence invoice and the purchase order you already have. There is no separate contract and nothing for procurement to open. Atlassian licenses apps at your whole Confluence user tier, so budget for every licensed seat, not only the people who post. The one bill that does not come from Atlassian is X's, and only if you switch timelines on.
We used to embed a Collection or a liked-posts timeline. Can we get those back?
No, and no app can. X retired the embedded grid, Collections and liked-posts timelines on its own side, so there is nothing left for an app to render. A profile timeline and a public List timeline are what remain. The List has to be public, because a private one cannot be read without signing in.
Is the Data Center app the same app?
No. They are two builds under one name, and everything on this page describes the Cloud one. The Data Center build has had no release since 2023 and declares support up to Confluence 8.6.2, well short of Data Center 9 and 10. If your site runs a current Data Center, check the app's Data Center listing on the Marketplace before you plan around it.
Put your X posts where your team already reads
Install X Connector for Confluence from the Atlassian Marketplace. Free to 10 users on Cloud.