Table Export for Confluence

Get your data out of Confluence tables — a whole space at once.

Your team keeps budgets, registries and checklists in Confluence tables. Sooner or later somebody needs that data in a spreadsheet — to sum it, chart it, or send it on. Copying by hand works until a table has merged cells; then the columns drift and the numbers stop lining up.

Getting started

Edit the page, type /Table Export and pick the macro.
Publish. Every table on the page appears in a list, with its size.
Press CSV or Excel next to the table you need.

The macro can sit anywhere on the page — it finds tables above and below itself. A good spot is the very bottom, out of the way of readers.

Three ways to take a table out

Button	What you get	When
CSV	A plain `.csv` file	For importing anywhere: Excel, Google Sheets, Numbers, a database
Excel	A file Excel opens as a formatted workbook	When you want the header row and borders to survive
Copy	The table in the clipboard	When downloads are blocked by company policy — paste straight into a sheet

Comma or semicolon

Pick the separator above the list. Use the semicolon if your Excel treats the comma as a decimal mark — that is the default in most of Europe and Latin America, and it is why exported files sometimes land all in one column.

Every table in the space, in one workbook

This is the part hand-copying cannot replace. Press All tables in this space and the app walks the pages of the space, collects every table it finds, and gives you a single Excel workbook.

Each table in that workbook is labelled with its own heading and the page it came from. Without the page name, a workbook of fifty tables is unusable — you cannot tell the March budget from the April one.

What it reads. Only pages you are allowed to open. The app asks Confluence with your permissions, not its own — it can never pull out a page you could not see yourself.

Limit: 100 pages. Beyond that the scan turns into minutes of waiting and hundreds of requests. If your space is larger, the app takes the first hundred pages and says so plainly rather than hanging.

Merged cells do not break the file

A cell spanning two columns leaves a hole in every naive export, and everything after it shifts one column left. On a budget table that means numbers landing under the wrong heading — the kind of error nobody notices until it matters.

This app unrolls merged cells: the value is repeated in each position the merged cell occupied, so every row comes out the same width. Cells with several paragraphs keep their line breaks instead of running together.

Where your data goes

Nowhere. The page body is read with your own permissions, the file is built inside your browser, and the browser hands it to you. The app has no servers of its own and makes no outbound request of any kind. It carries the Runs on Atlassian badge, which means Atlassian verifies this at the platform level, not on our word.

For budgets, payroll registries and HR data this is usually the deciding argument: the data never leaves the place where it already lives.

Known limits

Whole-space scan stops at 100 pages.
The Excel file is a formatted table, not a multi-sheet .xlsx: every table in a space export lands on one sheet, one after another.
Images and macros inside cells are not exported — only their text.
Tables inside other macros (expand blocks, panels) are read; tables inside other apps' macros may not be, because their content is not part of the page.

Support

Write to support@horizonventures.app. If a table comes out wrong, send the page — or just the table — and we will tell you why. We answer within one business day.