FileFeed: Stop Writing CSV Parsers for Every New Client
If you're building B2B SaaS, you know the pain. Every enterprise client sends data in their own format.
One sends Worker_ID, Name. Another sends EmpID, FullName. A third sends Mitarb_Nr, Naam.
You end up writing custom parsing code for each one. It works until you have 20 clients and 20 brittle scripts.
We built FileFeed to fix this.
What is FileFeed?
FileFeed is a file processing platform for automated file ingestion. Files come in through SFTP, email, API, or cloud storage. FileFeed validates them, maps the columns to your schema, runs transformations, and delivers clean JSON to your product.
One schema. Every client mapped to it. Zero custom parsers.
How it works
- Your client drops a file to SFTP
- FileFeed detects the pipeline (client + folder match)
- Schema validation runs
- Field mappings applied
- Transformations executed
- Webhook fires to your system
- You fetch clean JSON via API
Each client gets their own SFTP credentials, isolated storage, and a pipeline with their specific field mappings. You define the schema once. FileFeed normalizes everything to it.
What you get out of the box
Multi-channel ingest : SFTP, email, API, cloud storage
Schema validation : reject bad data before it hits your system
Field mapping : Worker_ID to employee_id, per client, no code
Built-in transformations : toLowerCase, trim, formatPhoneNumber, and more
Webhook delivery : HMAC signed, fires on file received, processed, or failed
Outbound delivery : push clean data back via API, SFTP, cloud storage, or email
Dashboard : see every pipeline run, download original and processed files
What it replaces
Before FileFeed, teams used tools like Couchdrop for SFTP file routing. That handles file transfer but not file processing. Engineers still wrote all the parsing, mapping, and validation code themselves.
FileFeed handles the full pipeline from ingest to delivery.
Who is this for?
B2B SaaS companies whose enterprise clients send data files. HR-tech, fintech, healthcare, supply chain. If your engineers are writing file parsers instead of building product, FileFeed handles that layer.
Try it
Check it out at filefeed.co.
Top comments (0)