Parse CSV to JSON in Power Automate with PDF4me

PDF4me CSV - Parse to JSON is a Power Automate action that converts a CSV file into a structured JSON array with a three-tier header priority system and configurable delimiter. Use it to feed CSV exports into databases, REST APIs, or Excel without writing a custom parser in your flow.

What this action does

PDF4me CSV - Parse to JSON reads a CSV file and returns a Base64-encoded JSON array of objects, with Column Headers, Skip First Line, and Culture Name controlling how rows and headers are interpreted. Any delimiter works, and malformed rows are handled gracefully instead of failing the flow.

How Do I Authenticate My Power Automate Flow?

Every PDF4me action in Power Automate requires a valid connection. Create or select one that holds your PDF4me API key so the flow can authenticate CSV parsing requests securely.

Get your API Key

Important Facts You Should Not Miss

Header handling has a strict 3-tier priority

Column Headers wins if provided (every CSV line becomes data). Otherwise Skip First Line set to true uses the first CSV line as headers. If both are empty, headers auto-generate as Column1, Column2, and so on.

Culture Name is an easy-to-miss advanced parameter

Hidden under Advanced parameters alongside Column Headers and Skip First Line, Culture Name sets the locale used to interpret region-specific number and date formats in the CSV.

Parsing is permissive, not strict

Rows with fewer values than headers get empty strings, rows with more values have the extras ignored, and malformed data returns an empty array instead of throwing an error.

Parameters

Required: File Content, File Name, and CSV Delimiter must be provided. Column Headers, Skip First Line, and Culture Name are optional advanced parameters.

Parameter	Required	What it does	Example
File Content	Required	Base64 content of the source CSV file, mapped from SharePoint, OneDrive, or an email attachment.	`[File Content from Get File]`
File Name	Required	CSV filename including extension, used for processing and output identification.	`data.csv`
CSV Delimiter	Required	Character or short string separating columns. Comma, semicolon, tab, and pipe are all supported, as are multi-character delimiters.	`,`
Column Headers	Optional	Comma-separated custom header names. When provided, every CSV line including the first is treated as data and Skip First Line is ignored.	`FullName,Age,Email`
Skip First Line	Optional	When true and Column Headers is empty, uses the first CSV line as headers and starts data from the second line. Default false.	`true`
Culture Name	Optional	Locale used to interpret region-specific number and date formats in the CSV content.	`en-US`

Output Fields

Field	Type	What it contains
`document`	Base64	The parsed JSON array, UTF-8 encoded and Base64 wrapped.
`FileName`	String	Fixed output filename, "parsed_data.json".
`Success`	Boolean	true if parsing completed, false if the action failed.
`ErrorMessage`	String	Error description, null when Success is true.
`Errors`	Array	Detailed error objects with Code and Message, empty when Success is true.

What Do the Common Error Messages Mean?

Error Message	Cause	Solution
Request is empty	Request object is null.	Provide a valid request object.
Document is empty	Document object is null or CSV content is null.	Provide valid CSV file content.
Encoding exceptions	CSV content is not UTF-8 encoded.	Re-save or export the CSV file as UTF-8.
Empty array output	CSV content is empty or contains only a header row.	Provide a CSV file with at least one data row.

How Do I Set Up Parse CSV in Power Automate?

Add PDF4me → CSV - Parse to JSON to your Power Automate flow.
Map File Content and File Name from a previous action (SharePoint, OneDrive, or email attachment).
Set CSV Delimiter to match your source file (comma, semicolon, tab, or pipe).
Expand Advanced parameters and set Column Headers for custom names, or Skip First Line to use the file's own header row.
Run the flow, decode the document Base64 output, and loop through the resulting JSON array with Apply to each.

Typical Setups

Workflow ExamplesCommon Power Automate flow patterns using Parse CSV.

CSV-to-database import

A CSV file lands in a SharePoint "Imports" folder, triggering the flow.
Parse CSV converts it to JSON with CSV Delimiter set to a comma and Skip First Line enabled.
The document output is decoded and parsed into individual JSON objects.
Apply to each loops through the records and inserts them via a SQL connector.
The processed CSV is moved to an "Archive" folder.

European export to REST API

A source system emails a semicolon-delimited CSV export.
Parse CSV runs with CSV Delimiter set to a semicolon and Skip First Line enabled.
Each parsed record is posted to a REST API endpoint with HTTP.
Response codes are collected to flag any failed records.
A summary is emailed once the loop completes.

CSV to Excel with custom headers

A legacy report arrives as a tab-delimited CSV with no header row.
Parse CSV runs with CSV Delimiter set to a tab and Column Headers set explicitly.
The resulting JSON array feeds a PDF4me Add Rows action to populate an Excel template.
The formatted Excel workbook is emailed to stakeholders.

Practical Tips

Column Headers overrides Skip First Line completely

If you set Column Headers, Skip First Line is ignored and every CSV row, including what looks like a header row, is treated as data. Do not set both expecting them to combine.

Match the delimiter exactly to the export locale

European CSV exports commonly use a semicolon instead of a comma, especially when the source system uses comma as the decimal separator. Check a sample row before hardcoding the delimiter.

Decode document before parsing further

The document output is Base64-encoded JSON text, not a ready-to-use object. Decode it first, then use Parse JSON to expose individual fields for Apply to each.

Set Culture Name for non-US number formats

If the CSV uses comma as a decimal separator or day-first dates, set Culture Name to match (for example de-DE or en-GB) so downstream conversions do not misread values.

Treat empty output as a signal, not a crash

An empty array back from Parse CSV usually means the file only had a header row or was empty, not that the flow failed. Check Success and Errors before assuming the source file is fine.

Cheat Sheet

Field	Value
Action	`CSV - Parse to JSON`
Header priority	`Column Headers > Skip First Line > auto-generated`
Common delimiters	`, (comma) / ; (semicolon) / \t (tab) / \| (pipe)`
Output filename	`parsed_data.json (fixed)`
Output format	`document (Base64 JSON array)`
Malformed data behavior	`Returns empty array, does not error`

Common Questions

How do I parse a CSV file to JSON in Power Automate?+

Add the PDF4me CSV - Parse to JSON action, map File Content and File Name from a prior action, set the CSV Delimiter, then choose Column Headers or Skip First Line for header handling. The action returns document, a Base64 JSON array you can decode and loop through.

What is the header priority order?+

Column Headers takes priority if provided, every CSV line including the first is treated as data. If Column Headers is empty and Skip First Line is true, the first CSV line becomes the headers. If both are empty, headers are auto-generated as Column1, Column2, and so on.

What happens with malformed or empty CSV data?+

CSV parsing is permissive. Rows with fewer values than headers are filled with empty strings, rows with more values than headers have the extras ignored, and empty or header-only CSV content returns an empty JSON array rather than an error.

What does the Culture Name parameter do?+

Culture Name is an advanced parameter that sets the locale used when interpreting the CSV content, useful when the source file uses region-specific number or date conventions that differ from the default parsing culture.

Can I parse semicolon or tab-delimited CSV files?+

Yes. CSV Delimiter accepts any character or short string, including semicolon for European exports, tab for TSV files, or pipe for database exports. Multi-character delimiters are also supported. See <a href="https://www.rfc-editor.org/rfc/rfc4180" target="_blank" rel="noopener noreferrer">RFC 4180, the common CSV format specification</a> and <a href="https://learn.microsoft.com/en-us/connectors/pdf4meconnect/" target="_blank" rel="noopener noreferrer">the PDF4me Power Automate connector reference</a> for background.