Data & Storage · Integration
Flat File Database
Add Flat File Database to your product for your customers, and give your AI agents governed access to it.
Embed a flat file database integration so your customers can bring records that live in delimited or fixed-width files into your product without you writing a parser per customer. Column layouts, delimiters, and encodings differ per customer, so parsing and field mapping are configuration per tenant rather than code, and large files are read in pages so a big import does not stall your product. fastn maintains per-customer access and upkeep, so onboarding another file source is configuration rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own flat files so legacy records are usable inside your product.
Map columns to your product's own fields per customer, so an unusual layout does not need a code change.
Write records back out in the format a customer's downstream system already expects.
Read on a schedule so refreshed files are picked up without anyone re-uploading them.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads records from a file to answer a question grounded in the customer's own data.
An agent writes a generated record set within governed permissions, with the action logged.
An agent reacts to an updated file and starts the next processing step.
Example prompt
Read this file and list the rows whose identifier does not match any record we already hold.
Set up Flat File Database in 4 steps
- 01Open the flat file database connector from your fastn dashboard.
- 02Have each customer connect the location where their files live.
- 03Map the delimiters, columns, and field types your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Flat File Database integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Flat File Database integration without building it. Your customers connect their own Flat File Database account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Flat File Database update is not your on-call problem.
- One integration serves your product and your agents. The same governed Flat File Database connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
PostgreSQL
SnowflakeWorks well with
AWS Simple Storage ServiceOften used alongside
Tools the same teams tend to run next to Flat File Database, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceFlat File Database integration FAQ
How do I add a Flat File Database integration to my product?
Enable the Flat File Database connector in your fastn dashboard, then let each customer authenticate their own Flat File Database account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Flat File Database client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Flat File Database account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Flat File Database account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Flat File Database integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads records from a file to answer a question grounded in the customer's own data.
Who maintains the Flat File Database integration?
fastn does. When Flat File Database changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Flat File Database integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Flat File Database reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Flat File Database integration?
A common starting point: connect their own flat files so legacy records are usable inside your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Flat File Database integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Flat File Database does not change your per-connector cost. You can start free with 3 connected accounts.
Add Flat File Database to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.