Content & Documents · Integration
Files.com
Add Files.com to your product for your customers, and give your AI agents governed access to it.
Embed a Files.com integration, formerly BrickFTP, so your customers can move and manage their own files, folders, and transfers from inside your product, with governed agent access to the same content. Access runs through each customer's own site credentials, so their existing folder permissions apply and your product cannot read a path the connected account could not read itself. fastn handles per-tenant auth, pagination, and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Files.com site so your product lists and browses their folders and files.
Upload and download files programmatically so managed file transfer happens inside your product.
Read transfer and folder activity history so users can see what moved, when, and by whom.
Trigger your product when a file lands in a watched folder so the next processing step runs immediately.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a delivered file to answer a question grounded in the customer's own data.
An agent uploads a generated file to the agreed folder within governed permissions.
An agent reacts to a new inbound transfer and starts validation or ingestion.
Example prompt
List files delivered to the inbound folder today and flag any that are smaller than expected.
Set up Files.com in 4 steps
- 01Open the Files.com connector from your fastn dashboard.
- 02Have each customer authenticate their own Files.com site with a least-privilege API key.
- 03Map the folders and file metadata 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 Files.com integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Files.com integration without building it. Your customers connect their own Files.com account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Files.com update is not your on-call problem.
- One integration serves your product and your agents. The same governed Files.com connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Box
AWS Simple Storage ServiceWorks well with
Bonsai ElasticsearchOften used alongside
Tools the same teams tend to run next to Files.com, across other categories.
Shopify
Stripe
Jira
AsanaFiles.com integration FAQ
How do I add a Files.com integration to my product?
Enable the Files.com connector in your fastn dashboard, then let each customer authenticate their own Files.com account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Files.com client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Files.com account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Files.com account and only ever sees their own files, documents and versions. 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 Files.com 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 a delivered file to answer a question grounded in the customer's own data.
Who maintains the Files.com integration?
fastn does. When Files.com 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.
Whose permissions does the Files.com integration run under?
Each customer's own Files.com grant. Where Files.com holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in Files.com automatically?
Where Files.com supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the Files.com integration?
A common starting point: connect their own Files.com site so your product lists and browses their folders and files. 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 Files.com integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Files.com does not change your per-connector cost. You can start free with 3 connected accounts.
Add Files.com to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.