Files.com is the File Orchestration Platform: partners send files in over SFTP, and every transfer is governed and logged. The official Files.com connector runs file actions from any flow, in Power Automate and Azure Logic Apps alike. A partner upload fires a Files.com webhook that starts the flow, and the connector routes the file across Microsoft 365 from there.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
Power Automate runs flows across Outlook, SharePoint, Teams, and hundreds of other connectors. What the Microsoft connectors don't give you is real file transfer: letting partners send files in over SFTP and FTPS, controlling who can reach which folders, keeping an audit trail. The files those flows act on usually come from outside Microsoft 365, dropped by a partner, vendor, or customer who has no Microsoft account at all. The official Files.com connector closes that gap.
Files.com publishes and maintains a real connector inside Power Automate, not a generic "we support SFTP" step. Search "Files.com" in the flow designer to add it, so you build on a supported connector instead of wiring up raw file transfer yourself.
The connector calls the Files.com API directly instead of tunneling SFTP inside the flow, so file steps run faster and more reliably than Power Automate’s built-in file-transfer connectors. Use it on every Microsoft 365 file flow, not a raw SFTP step.
One connector covers the platform: upload, download, copy, and move files; create folders and share links; manage users and groups; deliver to remote servers, snapshots, and child sites. So a flow runs the whole file workflow, not just the file move.
The same Files.com connector works in Power Automate and Azure Logic Apps, so a team that runs automation in both builds against one connector, not two.
Microsoft handles logins, teamwork, and flows. Files.com is the file platform underneath, so you keep your Microsoft 365 stack and partners get a real file-transfer front door.
Power Automate never gets blanket access to your files. The connector signs in with a Files.com API key, and the key carries the same access rules you apply to your people.
An admin hands out a user-scoped key to limit folder access, or a site-wide key for full access. A flow reaches exactly the folders its key allows and nothing more, so an automation can't touch files it was never meant to see.
A flow handling clinical documents, financial files, or partner data gets a full audit trail that Files.com keeps on its own, separate from Microsoft 365. When an auditor asks who touched a file and when, the answer is in the Files.com logs.
Teams alerts post through Microsoft's own Workflows app, the same channel your IT already governs. If your org restricts that app, IT allows it once and every file alert arrives through an approved path.
Lab results and imaging files come into Files.com over secure protocols; a Power Automate flow routes them into the EHR, checks them against your rules, and tells staff they've arrived. Nobody sits refreshing a folder waiting for a lab result.
Files.com handles secure delivery, audit, and retention of transaction files and regulatory filings; a flow sends them to accounting, reporting, and compliance systems on a schedule or the moment they land.
Files.com handles access, retention, and audit logs as documents come in; a flow files them in the document management system and sends a notice at each review stage.
Files.com is the secure home for product catalogs and order files; a flow keeps them in sync with commerce platforms and internal systems.
Flows post file alerts straight to a Teams channel, so the people who care see them where they already work.
Learn MoreRun file workflows on Files.com itself for the steps that belong there rather than in the Microsoft 365 flow.
Learn MoreEvery connector action lands in a tamper-proof, exportable record, separate from Microsoft 365.
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
Files.com synchronized external-facing folders with SharePoint, giving vendors and auditors governed access while employees stayed in Microsoft 365.
Read The Story
Files.com met each vendor’s existing protocol and connection behavior, taking outside development schedules out of the retirement plan.
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 Files.com connector works inside Power Automate, what your flows can reach, and how they authenticate.
Yes. The Files.com connector appears as an official connector inside Power Automate. Search “Files.com” when building a flow to add it. The same connector also works in Azure Logic Apps.
Use the Files.com connector. It calls the Files.com API directly rather than tunneling SFTP inside the flow, so file steps run faster and more reliably than the built-in file-transfer connectors. It operates on files, folders, share links, users, and groups, not just file moves. Use it on every Microsoft 365 file flow instead of a raw SFTP connector.
Yes. Files.com sends a webhook the moment a partner uploads over SFTP or FTPS, and that webhook starts the Power Automate flow. The connector's actions take it from there: download the file, route it across Microsoft 365, create share links, or notify the team.
The connector signs in with a Files.com API key. An admin hands out a user-scoped key to limit folder access, or a site-wide key for full access. Everything the connector does is written to the Files.com logs.
Yes. The Files.com connector is safe to use in production. Microsoft tags new connector versions as “Preview,” and those versions are functionally identical to released versions and fully supported.
Files.com gives you the secure protocols partners use to send files in, control over who can reach which folders, and its own audit trail. The Microsoft connectors provide none of those. The Power Automate flow still handles the Microsoft 365 side.
Files.com delivery monitoring catches the file that never arrives. A flow that never triggers makes no noise. Delivery monitoring defines when each feed is due and alerts the moment one is late, so the flow that didn't run gets noticed before its downstream deadline.
File transformation belongs on Files.com, and the flow keeps the approvals, notifications, and API steps. Format conversion, splitting, renaming, and encryption run as TransformScript and Automations on Files.com, so flows stay simple and transformations live as configuration.
Yes. Files.com syncs move partner files into SharePoint directly, and mounts write them straight into the library as they arrive, with no flow in the loop. Save the flow for the parts that genuinely need flow logic, like approvals and notifications.
Start a 7-day free trial, search “Files.com” in Power Automate, and run your first file action from a flow. No credit card required.
No credit card required • 7-day free trial • Live in minutes