How Do You Export Your LinkedIn Post Data?

Export your LinkedIn post data with Flux's one-click Export button, which downloads your full post library as a CSV or JSONL file. The export includes engagement metrics — likes, comments, shares, and total engagement — along with post text, type, and hashtags, formatted for immediate use in spreadsheets, BI tools, or scripts. It does not include impressions, since those aren't reliably available across LinkedIn.

What you'll learn

How to export your posts from the Flux dashboard
What columns and metrics the export includes
When to choose CSV versus JSONL
How to pull data programmatically with the profile-export function and MCP tools
Common export workflows for coaches, marketers, creators, and developers

How do you export your posts from Flux?

Open your dashboard and click the Export button in the header. Flux generates a file containing all of your posts — there's no row limit, so a full library exports in a single click. The download is named linkedin-posts-[name]-[date].csv so files stay organized when you export on a schedule.

The export covers your entire post library, roughly the last year of posts, which is the depth HarvestAPI collects. There is no date filter on the export itself: every post Flux has on file comes down in one file. If you only need a slice, filter the resulting CSV in your spreadsheet or use the MCP tools described below, which do accept a date range.

LinkedIn's own data download is the alternative, and it's a poor one. It hands you a messy ZIP of your entire account — connections, messages, ad history — not a clean table of post analytics, and nothing formatted to drop into a spreadsheet. Flux skips all of that and gives you just your post performance, ready to work with.

What's included in the export?

Each row is one post, with columns for Post URL, Date, Text, Likes, Comments, Shares, Total Engagement, Reactions (formatted), Post Type, Character Count, and Hashtags. That gives you the raw engagement numbers plus enough context — text, format, and length — to slice performance any way you want once the data is in a spreadsheet or BI tool.

The post text is properly escaped, so commas, quotes, and newlines inside your posts won't break the CSV structure or shift columns. You can open the file directly in Excel or Google Sheets and trust that a post containing a comma still lands in a single cell.

One thing the export does not contain is impressions or reach. Flux is built around engagement — likes, comments, and shares — because impression data isn't reliably available across LinkedIn. Engagement is the stronger signal anyway, since it reflects who actually reacted rather than who scrolled past.

Should you choose CSV or JSONL?

CSV is the default and the right choice for most people. It opens directly in Excel, Google Sheets, Looker Studio, and virtually every BI tool, so it's the format to pick when a human is going to look at the data or build a report.

JSONL — one JSON object per line — is the better fit when code is going to read the data. It preserves structure cleanly for scripts, streams row-by-row without loading the whole file into memory, and drops neatly into Clay tables, data pipelines, or LLM workflows. Choose JSONL when you're piping posts into something programmatic rather than eyeballing a sheet.

How do you export data programmatically?

Behind the Export button is the profile-export Edge Function, which you can call directly to automate exports instead of clicking through the dashboard. This is the path to take when you want a nightly backup or a recurring pull into your own pipeline rather than a manual download.

For more flexible programmatic access, Flux exposes MCP tools on the Edge tier. get_posts retrieves your posts with filters like date range and format, so you can pull just the slice you need. get_posting_insights returns aggregated analytics — your best day, best hour, format breakdown, and length sweet spot — while get_topic_insights returns performance broken down by topic. Together they let you feed either raw posts or pre-computed insights straight into your own workflows. See LinkedIn MCP Tools: Programmatic Access for the full toolset.

What can you do with exported data?

The export is a starting point for whatever lives outside Flux. A few patterns come up repeatedly across different kinds of users.

A LinkedIn coach can export a client's data and drop it into Notion or a slide deck for a review session, turning raw numbers into a narrative the client can follow. A marketer can push the CSV into a CRM or reporting pipeline so post performance sits alongside the rest of the funnel.

A creator can use the export as a backup of their post library and track trends month over month in Google Sheets, watching how formats and topics shift over time. A developer can stream the JSONL into scripts, Clay tables, or LLM workflows — for example, classifying posts by theme or generating new drafts from past winners. In every case the export gets your data out of LinkedIn's walls and into the tool where you actually do the work.

Frequently asked questions

Does the Flux export include impressions or reach?

No. The export includes engagement metrics — likes, comments, shares, and total engagement — but not impressions, because impression data isn't reliably available across LinkedIn. Engagement is the stronger signal of resonance, since it measures who actually reacted.

Is there a row limit on the export?

No. The Export button downloads your full post library in a single file with no row cap. It covers roughly the last year of posts, which is the depth HarvestAPI collects.

Can I export only posts from a specific date range?

The dashboard Export button has no date filter — it always exports your full library. To pull a specific range, either filter the resulting CSV in your spreadsheet, or use the get_posts MCP tool, which accepts a date range and format filters.

What's the difference between CSV and JSONL?

CSV opens directly in Excel, Google Sheets, and BI tools, and is the default choice for reporting and human review. JSONL gives one JSON object per line and is better for scripts, data pipelines, Clay tables, and LLM workflows where code reads the data.

Will post text with commas break my spreadsheet?

No. Flux properly escapes commas, quotes, and newlines inside post text, so each post stays in a single cell and your columns don't shift when you open the CSV in Excel or Google Sheets.

On this page