EasyCSV

Queue CSV, XLSX, and Google Sheets imports with EasyCSV by posting a public file URL to an import page. Agents turn a spreadsheet that landed in a mailbox into rows in the destination system.

1 trigger 2 actions API key available

Platform Documentation ↗ Capability data verified 2026-07-31

A partner's account spreadsheet lands in the shared folder

Agent reads the header row and the row count without opening the file to anyone else

Agent lists the columns and identifies which carry personal or financial values

Agent confirms the columns match the mapping the target import page expects

Agent stages the file and prepares the POST to the import page, including the import code and any static columns

Agent posts the column list, the row count, and the destination the import page writes to in the revenue operations channel

The operations owner approves exposing the file at a publicly reachable URL, and the agent calls Import Spreadsheet From URL

What This Integration Enables

EasyCSV is not a file converter, and reading it as one leads to the wrong architecture. It is an import pipeline. You configure an import page in EasyCSV that knows where rows should go, whether that is your own webhook, Google Sheets, Salesforce, FTP, or something else, and then you feed that page spreadsheets. Import Spreadsheet From URL posts a CSV, XLSX, or Google Sheet export URL to one of those pages and queues it. Generate CSV File runs the same idea backwards, taking structured data and handing it to a CSV Generator that delivers a finished file to email, FTP or SFTP, Google Drive, or Dropbox. Two actions is the whole surface, and that is a statement about what the product is rather than a gap in the connector.

The real payoff is the trigger. On New Import Record fires once per row, in real time, as EasyCSV parses the spreadsheet. Each event carries the import metadata EasyCSV sends on every request, including importId, importName, importerEmail, sheetName, and importCode, the row itself keyed by spreadsheet column title, and any configured virtual output fields. Bulk chunk uploads are fanned out into one event per row, and the untouched payload is always available so nothing is lost in translation. That shape is what turns "a spreadsheet arrived" into something a workflow can actually reason about: a bad row becomes one automation exception with its own context, rather than a batch that failed somewhere in the middle. One caveat is worth knowing up front. EasyCSV publishes no API for registering webhooks, so the trigger's callback URL and the import page's POST URL are both copied by hand from the EasyCSV interface once, at setup.

Without FlowRunner

Spreadsheets handled by hand A partner file arrives by email and someone opens it, checks it, and pastes it into the destination system

Errors found row by row A malformed row halts the paste, and the person restarts from wherever they think they got to

No record of what was loaded Which file produced which records, and who loaded it, lives in a sent-items folder

With FlowRunner

Imports queued by the flow The file is submitted to the import page and parsed without anyone opening it

Rows arrive as events Each parsed row reaches the flow individually, so a bad row is one exception rather than a stalled batch

Provenance carried on every row Import id, import name, importer email, and the sheet it came from travel with each record

Use Case Scenarios

A partner file becomes rows in the CRM

A reseller emails their monthly account list. Rather than someone opening the attachment, the agent stages the file and submits it to the configured import page with Import Spreadsheet From URL. Static Extra Columns stamp the partner id, the tenant, and the source onto every row, and an Import Code lets the receiving flow confirm the submission came from a trusted source. EasyCSV parses the file and On New Import Record fires per row. Each row arrives with its own provenance attached and is matched against existing accounts in Salesforce before anything is written, so the flow can decide per record whether this is a new account or an update to one that already exists.

Customer self-service upload feeding a live workflow

An EasyCSV import page is embedded in the product so customers can bulk-upload their own data. When a customer completes an upload, On New Import Record delivers every parsed row to FlowRunner as it is read, tagged with the importer's email and the sheet slug. The flow validates each row against the account's own rules, writes the clean ones, and collects the rejects with the reason each one failed. When the import finishes, the customer receives one message listing exactly which rows did not load and why, rather than a generic failure. The trigger can be restricted to a single import page with Sheet Slug so one flow serves one upload surface.

Sending a file back out

The reverse direction matters as much as the inbound one. A reporting flow assembles query results as an array of row objects and calls Generate CSV File against a configured CSV Generator, where the keys of the first object become the header row. The generator's own filename setting decides the format, so a filename ending in .xlsx produces an XLSX rather than a CSV, and the generator's configured destination decides delivery, whether that is email, FTP or SFTP, Google Drive, or Dropbox. When the generator has public temp files enabled, EasyCSV returns a temp file URL valid for up to 24 hours, which is enough for a flow to pick the file up and store it durably.

Human-in-Loop Highlight

Import Spreadsheet From URL has a requirement that deserves to be said out loud rather than buried in a field description: the URL must be publicly accessible. EasyCSV fetches the file itself, so for the duration of the import the spreadsheet has to sit somewhere on the open internet with no authentication in front of it. For a product catalogue that is nothing. For a partner's account list with contact names and contract values, or an HR file with salary bands, publishing it at an unauthenticated URL is a disclosure decision. It is also one that gets made by accident, because the field is labelled File URL and does not look like a decision at all.

So the agent treats it as one. It reads the header row and the row count first, without exposing anything, identifies which columns carry personal or financial values, and posts to the revenue operations channel: "Partner file NLF-accounts-Q3.xlsx, 1,842 rows. Columns include contact_email, contact_phone, and annual_contract_value. Importing requires publishing this file at a public URL that EasyCSV will fetch. Approve the import, or route the file for manual handling?" Nothing is published and no import is queued until someone answers. If the answer is no, the file is handled another way. If the answer is yes, the exposure was a choice a named person made with the column list in front of them. That is the whole argument for human-in-the-loop on this connector: the agent can do everything except decide what is safe to make public, and the field that decides it is one line in a form.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

2 actions

Imports

Import Spreadsheet From URL Starts an import by posting a publicly accessible CSV, XLSX, or Google Sheet export URL to one of your import pages. Enable it first in EasyCSV under Sheet Details by ticking "Import sheets posted to API Webhook" and copying the POST URL. EasyCSV fetches and parses the file asynchronously and delivers the rows to whatever destination the import page is configured for, so this action queues the import rather than returning the parsed rows. Use the On New Import Record trigger to receive them. Extra Columns staples up to 50 static columns onto every row, and Import Code passes a token back so your own system can validate the import's origin.

File Generation

Generate CSV File Builds a spreadsheet from structured data using an EasyCSV CSV Generator. Create the generator first under All CSV Generators and configure where finished files should go. Supply the generator id or its full webhook URL along with an array of row objects: the keys of the first object become the header row, so every object should carry the same keys. The generator's filename setting decides the output format, and a filename ending in .xlsx produces an XLSX instead of a CSV. When public temp files are enabled the response carries a temp file URL valid for up to 24 hours. Recipient Email can override the delivery address per call.

Triggers

1 triggers

Event Triggers

On New Import Record Fires in real time for every row EasyCSV parses out of an imported spreadsheet. Setup is manual because EasyCSV publishes no API for registering webhooks: open your import page, tick "Post imports to Webhook" under the webhook and API destination settings, and paste the callback URL FlowRunner generates. Each row arrives with the import metadata EasyCSV sends on every request, including importId, importName, importDatetime, importerEmail, sheetName, sheetSlug, sheetId, and importCode, the row itself in recordData keyed by spreadsheet column title, and any configured virtual output fields. Bulk chunk uploading is supported, with an array of rows fanned out into one event per row, and the untouched payload is always available in raw, which is where the file URL appears when the import page is set to post all data as a new CSV file URL. The trigger can be restricted to one import page with Sheet Slug, or to a single trusted import token with Import Code.

Frequently Asked Questions

What can FlowRunner do with EasyCSV?

FlowRunner agents can run Import Spreadsheet From URL and Generate CSV File in EasyCSV.

Does connecting EasyCSV to FlowRunner require OAuth?

No. EasyCSV connects to FlowRunner with an API key, no OAuth flow required.

Can EasyCSV trigger a FlowRunner workflow automatically?

Yes. EasyCSV supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with EasyCSV

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us