An Official, First-Class Connector
Files.com publishes and maintains a real connector inside Azure Logic Apps, not a generic “we support SFTP” step.
Files.com publishes an official connector in Azure Logic Apps. It is the same one that works in Power Automate. A workflow can start on a file event and run file actions as steps. The connector calls the Files.com API directly instead of tunneling over SFTP, so transfers run faster and fail less than the built-in file-transfer connectors.
No credit card required · 7-day free trial · Live in minutes



Real companies. Real file flows. Real results.





















Logic Apps runs processes across Azure services, on-prem systems, and applications. What it doesn’t do on its own is secure file transfer. It can’t let partners send files in over SFTP and FTPS, control who reaches which folders, or keep an audit trail. And those processes usually involve trading partners, suppliers, and counterparties, not just your own Azure services. The official Files.com connector closes that gap, right where the files come in.
Files.com publishes and maintains a real connector inside Azure Logic Apps, not a generic “we support SFTP” step.
The connector is built for the job. It calls the Files.com API directly, so it is faster and more reliable than Logic Apps’ built-in file-transfer connectors. Use it on every Azure file workflow, not a raw SFTP connector.
A workflow can manage files, folders, share links, users, and groups. Dedicated actions also deliver files straight to a Remote Server, a Snapshot, or a Child Site, so you build deep workflows, not just move a file around.
The same Files.com connector works in both Azure Logic Apps and Power Automate. Search “Files.com” in either one to add it.
Logic Apps connects to hundreds of systems, and the alternative to a connector is code. Without Files.com, the partner-facing file endpoint becomes Azure Functions your platform team writes and babysits. With it, that whole layer is a product someone else runs.
The connector signs in with a Files.com API key, and that key is the whole security story: what the workflow can reach, and what gets recorded when it does. That is the access control and audit trail Logic Apps doesn’t give you for file work.
A user-scoped key limits a workflow to certain folders. A site-wide key grants full access. A workflow reaches exactly the folders its key allows and nothing more, so an automated flow can never touch files it has no business reading.
Every connector operation is written to the Files.com logs, giving your platform team a full record of the file part of a workflow. That is exactly the proof a regulatory or supply-chain integration has to show.
The connector reaches Files.com over HTTPS like any normal outbound connection, so the point where files come in fits inside your existing Azure network setup.
Files.com is the one place vendors send inventory updates, purchase orders, and shipment notices. A Logic Apps workflow routes them into ERP and supply-chain planning.
Files.com moves large files at volume; a workflow handles approvals, metadata updates, and delivery to Azure Blob, S3, and SharePoint.
Files.com takes in machine output and inspection files from the plant floor or edge devices; a workflow processes them, stores them, and feeds them into manufacturing systems.
Files.com keeps compliance reports secure and auditable in one place; a workflow handles the schedule, the approvals, and delivery to regulatory systems.
Files.com posts to a Teams channel the moment a file lands, so the workflow doesn’t need its own alerting steps.
Learn MoreRun the file-shaped steps on Files.com itself: scheduled sweeps, moves, renames. The Logic App stays short and does the orchestration.
Learn MoreThe activity record behind the workflow is retained for 7+ years in tamper-proof WORM storage and streams to your SIEM.
Learn MoreNovember 17–20, 2026 · San Francisco, CA
Files.com builds deeply on SharePoint, OneDrive, Azure, and Microsoft Entra ID, so of course we’ll be on the floor at Microsoft Ignite telling our File Orchestration story. The legacy MFT vendors won’t be there.
See Files.com At Microsoft Ignite
With Files.com beside the legacy server, internal teams could move in phases while business-critical EDI traffic kept flowing.
Read The Story
The partner-mandated FTPS endpoint stayed in place while two-way X12 traffic moved from hand-driven scripts into an unattended, folder-based workflow.
Read The Story
“Files.com's strengths are simplicity, ease of use, and the cloud connectors. We don't have to invent custom infrastructure for every partner.”

“Files.com is versatile — it can manage many different situations from a single platform. We've consolidated multiple tools onto it.”

“Files.com is robust and scales to a large enterprise. We get multiple files per minute, per second — and we're a 24/7 organization, so everything has to always be up.”

How the connector authenticates, which folders your workflows can reach, and where the file work belongs between Logic Apps and Files.com.
Yes. The Files.com connector appears as an official connector inside Azure Logic Apps. Search “Files.com” in the Logic Apps designer to add it. The same connector also works in Power Automate.
Use the Files.com connector on every Azure file workflow. It calls the Files.com API directly instead of tunneling over SFTP, so it is faster and more reliable than the built-in file-transfer connectors. It also manages files, folders, share links, users, and groups, not just file moves.
Yes. One Files.com connector serves both Microsoft Power Automate and Azure Logic Apps. Search “Files.com” in either platform when building a flow.
The Files.com connector authenticates with a Files.com API key, scoped to one user to limit folder access or site-wide for full access. Everything the connector does is written to the Files.com logs.
Yes. The Files.com connector is production-ready and fully supported. Microsoft tags new connector versions as “Preview,” and those versions are functionally identical to released versions.
Files.com is a finished file-transfer product for the point where files come in. It brings partner protocols, folder-by-folder access control, and its own audit trail. So your platform team builds the workflow in Logic Apps instead of writing and maintaining all that file-transfer logic in Azure Functions.
Yes. Files.com webhooks call a Logic App’s HTTP trigger on upload events, so the workflow starts the moment a file lands instead of polling on a recurrence.
File-shaped transformation runs on Files.com as TransformScript and Automations: format conversion, splitting, renaming, per-recipient encryption. Keep the Logic App for orchestration and API work, so the workflow stays short.
Yes. Files.com lands mandated AS2 with MDN receipts, plain FTP, and browser uploads in the same governed folders the workflow reads. The partner’s protocol never becomes the Logic App’s problem.
Start a 7-day free trial, search “Files.com” in the Logic Apps designer, and run your first workflow on a real file event. No credit card required.
No credit card required • 7-day free trial • Live in minutes