Content & Documents · Integration
FTP/FTPS
Add FTP/FTPS to your product for your customers, and give your AI agents governed access to it.
Embed an FTP and FTPS integration so your customers can exchange files with the servers their business already runs on, without you writing a transfer client per customer. Credentials, host details, and directory paths are configuration per tenant, and FTPS keeps the transfer encrypted where the customer's server supports it. Large listings are paginated and throttled, and every transfer is logged per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers pull files from their own FTP or FTPS server into your product on a schedule or on demand.
Upload generated files to a customer's server so a downstream system picks them up as it always has.
List directories so users browse the structure they know from inside your product.
Poll a drop folder and trigger your product when a new file lands.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent lists a directory to find the file it needs before reading it.
An agent downloads a file and grounds an answer in its contents.
An agent uploads a generated file to the agreed folder within governed permissions, with the transfer logged.
Example prompt
List files added to the inbound folder today, then read the newest one and summarise its contents.
Set up FTP/FTPS in 4 steps
- 01Open the FTP/FTPS connector from your fastn dashboard.
- 02Have each customer supply their own host, credentials, and whether FTPS is required.
- 03Map the directories your product may read and write, then enable actions and polling triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the FTP/FTPS integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an FTP/FTPS integration without building it. Your customers point it at their own endpoint and credentials and work their files, documents and versions through it, 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 an FTP/FTPS update is not your on-call problem.
- One integration serves your product and your agents. The same governed FTP/FTPS 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
AWS Simple Storage Service
Box
Azure Blob StorageOften used alongside
Tools the same teams tend to run next to FTP/FTPS, across other categories.
Shopify
Stripe
Jira
AsanaFTP/FTPS integration FAQ
How do I add an FTP/FTPS integration to my product?
Enable the FTP/FTPS connector in your fastn dashboard, then let each customer authenticate their own FTP/FTPS account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no FTP/FTPS client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
How is an FTP/FTPS connection configured per customer?
FTP/FTPS is a specification rather than a service you sign up for, so there is no FTP/FTPS account. Each customer supplies their own endpoint and credentials, and that connection is scoped to them, so they only ever reach their own files, documents and versions. The per-tenant isolation works the same way it does for a vendor product.
Can AI agents use this FTP/FTPS 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 lists a directory to find the file it needs before reading it.
Who maintains the FTP/FTPS integration?
fastn does. When FTP/FTPS 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 FTP/FTPS integration run under?
Each customer's own FTP/FTPS grant. Where FTP/FTPS 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 FTP/FTPS automatically?
Where FTP/FTPS 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 FTP/FTPS integration?
A common starting point: pull files from their own FTP or FTPS server into your product on a schedule or on demand. 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 FTP/FTPS integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding FTP/FTPS does not change your per-connector cost. You can start free with 3 connected accounts.
Add FTP/FTPS to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.