Data · CSV macro
Your numbers get read, because they are on the page
With the CSV macro your data stops being an attachment nobody opens. The same file renders as a table in the document, so readers get the numbers in context, on any device, without downloading anything - and you stop pasting rows into a page and maintaining them by hand.
You maintain one version of the truth, not two
Copying rows into Confluence means owning two versions and remembering to update the second one. Instead, point the macro at the data where it already sits: a page attachment, a URL, or Google Drive. For the places that need credentials - Amazon S3, SFTP, a database - an admin sets the connection up once and everyone else just picks it from a list, so no secret ever gets pasted into a page. Either way your page references the source, and the snapshot you used to maintain by hand is gone.
You show the twenty rows that make your point
A five-thousand-row export is not a table anyone reads. Out of the box the macro shows the first fifty rows; tell it where to start and how many to show, and your page carries just the excerpt that supports the argument while the full file stays whole behind it. Mark the first row as a header and the columns get their real names instead of a legend, and every row is numbered for you - so a comment can say "row 42" and mean something.
Your readers take the data with them
Anyone on the page downloads the underlying CSV from the macro itself. Your page works as the report and as the handoff at once - no second attachment to upload, and nothing that quietly drifts out of step with the table above it.
Your data reads as part of the page, not as a widget
The table takes on Confluence's own look and follows the reader's light or dark
theme, so it reads as part of your document rather than an embedded box. Writing in
Markdown? A fenced csv block renders in place, so one document holds
prose, headings and data without breaking into a stack of macros.
What the other CSV apps leave you exporting by hand
Confluence has no shortage of apps that turn a CSV into a table - Data Tables for Confluence and a row of smaller CSV-to-table macros. All of them read at most three things: a page attachment, a URL, or text pasted into the macro. When the file you actually care about sits in an S3 bucket, behind SFTP, in Google Drive or in a database, none of them can reach it, and you are back to exporting by hand - which is exactly the gap the source list above closes for you. And the connection an admin sets up once for CSV is the same one every other macro in the pack uses, so the next format your team needs is already wired to the same places, on the same licence, with nothing new to evaluate.
CSV is one of 31 macros in Macro Pack
One app to install, one licence to renew, one place your team learns - and 30 more formats it already reads, from spreadsheets and diagrams to API specs and documents.
See every macro in the pack