Automated FileFeeds
Client file feeds that run themselves
Five stations, one afternoon. Set up a connection, schema, pipeline, and webhook in one flow, then every file your clients send rides the same rail: picked up, validated, mapped, delivered.
Start free, no credit card. See pricing
Connection
Open the door for their files
A connection is how files reach you. Hosted SFTP with per-connection folders and IP allow-lists, a dedicated email address with sender whitelists, or your own server with key auth. Set it up once, then reuse it on every pipeline that partner ever needs.
Managed SFTP · your own server · email ingestion · sender whitelists · IP allow-lists
Drop files into a folder.
Send as attachment.
POST file payloads.
Isolated folders, credentials, and IP allow-lists per connection
Schema
Define the structure files map to
Fields, types, formats, required flags. Build the schema by hand or upload a sample CSV and let FileFeed generate the fields for you. This is the one shape your product accepts, no matter what arrives on the other side.
JSON Schema · types and formats · required fields · generate from a CSV
employees_v1
Upload a CSV to auto-generate fieldsPipeline & Mappings
Map their columns to your fields
Auto-map pairs source columns with schema fields, transforms like trim, formatEmail, and toNumber clean values on the way through, and the pipeline won't ship until every required field is mapped. The same model works inbound and outbound.
Auto-map · built-in transforms · required-field enforcement · inbound and outbound
Pipeline & Mappings
Map source columns to schema fields.
Map every required schema field: start_date.
Webhook
Tell your system the moment data is ready
HMAC-signed events with automatic retries and a full delivery history. Prefer pulling? Fetch clean JSON from the REST API instead. Or skip this station entirely and add webhooks later; the pipeline runs either way.
HMAC signed · automatic retries · delivery history · REST API
Webhook
POST https://api.yourapp.com/webhooks/filefeed
HMAC signed · automatic retries
Notify an external system about pipeline events. You can always add webhooks later.
Runs
Watch it run, search everything, reprocess anything
Every file becomes a tracked run with the original and the processed output side by side. Search across all of them by any word in any file. When a mapping was wrong, fix it and reprocess; nobody has to resend a thing. Scheduled exports push processed files back out as CSV, XLSX, JSON, or XML.
Full-text document search · one-click reprocessing · scheduled exports to SFTP, S3, or email
Runs
Search files by any word…Reprocess any run after fixing a mapping. No re-upload needed.
Clean data in your product
No engineer rode along.
Why this exists
Most teams handle client files with a folder watcher, a pile of mapping scripts, and an engineer who gets pulled into every onboarding call. It works, right up until the third client.
FileFeed replaces that stack with one pipeline per feed, configured from a dashboard in an afternoon, and run automatically from then on. Connections, schemas, and webhooks live in a library, so the second pipeline is faster than the first.
Everything in the box
The full list, without the brochure
Running in HR tech, financial services, supply chain, and health tech.
Case studyEQORefer runs every client onboarding on this rail
Every new enterprise client sent employee data in a different format, and every onboarding needed a developer on the call. Now their CS team onboards clients on their own, and processed files go back to clients over the same SFTP.
Read the full case studyFAQ
Frequently asked questions
What ingestion channels are supported?
Automated FileFeeds supports SFTP (managed or bring-your-own with password or SSH key auth) and email attachments with sender whitelists. API upload is coming soon. All channels feed into the same validation and transformation pipeline.
Can I receive files via email?
Yes. Each connection can be assigned a unique email address. Clients send files as attachments, and FileFeed automatically extracts and processes them. You control allowed senders, accepted file formats, and optional subject filters.
Do you support outbound file exports?
Yes. FileFeed can generate processed files in CSV, XLSX, JSON, or XML and deliver them to SFTP servers, S3 buckets, email recipients, or webhooks. Exports can be scheduled, event-driven after a pipeline run, or triggered on demand via API.
What file formats are supported?
FileFeed processes CSV, Excel (XLSX/XLS), JSON, XML, and TSV natively. We also support PDF table extraction and EDI parsing for X12 and EDIFACT documents commonly used in supply chain and healthcare.
How does auto-mapping work?
When a file arrives, FileFeed analyzes the column headers and sample data to suggest mappings to your target schema. You review the suggestions, adjust anything that's off, attach transforms where values need cleaning, and approve. The pipeline remembers from then on.
How is this different from ETL tools?
Generic ETL platforms are built for connecting databases and SaaS APIs. Automated FileFeeds is built for the messier problem of recurring files from external partners: multi-channel ingestion, per-connection isolation, schema validation, mapping, and two-way delivery, without writing integration code per client.
Can I automate SFTP file ingestion?
Yes. FileFeed provides managed SFTP with per-connection folders, credentials, and IP allow-listing. Files are automatically picked up, validated, transformed, and delivered to your system via webhooks or the REST API.
Can I keep my own SFTP server and still use FileFeed?
Yes. Connect your existing server with password or SSH key auth and point FileFeed at the remote path. The same validation, transformation, and delivery pipeline runs either way.
How do I get the processed data?
Receive HMAC-signed webhook events and fetch JSON via the REST API, pull presigned downloads, or configure outbound delivery to SFTP, S3, or email. Whatever fits your stack.
Is this a Flatfile or OneSchema alternative for recurring feeds?
Yes. FileFeed focuses on recurring file feeds with managed multi-channel ingestion, auto-mapping, schema validation, outbound exports, and automation out of the box, rather than one-time imports.
Can my clients manage their own connection?
Yes. Invite a client into your workspace with access scoped to their connections only. They can configure and test their own integration and never see the rest of your workspace.
How much does Automated FileFeeds cost?
You can start free to validate your setup. The Professional plan is $299/month for teams actively onboarding clients, and Enterprise is custom for higher volume and compliance needs. Full details are on the pricing page.
Comparing options? See how FileFeed stacks up against Flatfile and OneSchema.
Ride it with your own file
Bring a real client file to the demo and we'll take it through all five stations live, from connection to clean JSON.
Start free, upgrade when you onboard real clients. See pricing