Skip to main content

Power Automate / Azure Logic Apps

Use Files.com actions in an existing Power Automate or Azure Logic Apps workflow to exchange files with people, partners, and other systems. The Microsoft workflow owns the application calls, approvals, and sequence; Files.com provides the file locations and access around that work.

The same Files.com connector works with both Power Automate and Logic Apps. Search for "Files.com" inside either platform when building a flow.

File Exchange in a Flow

Use the connector when file exchange is part of a workflow that also needs application logic, approvals, or other services. The flow starts with a schedule or a trigger from another connector. Files.com actions handle file operations, while the flow coordinates application processing and business decisions. For one-way replication between supported storage locations, a Files.com Sync may be simpler.

Application Output for a Partner

An application produces a report for a partner who collects files from Files.com. The flow uses Upload File after report generation to save the report's contents in the partner's folder.

The application generates the report; the flow chooses when and where to publish it. The partner retrieves the output through their Files.com access, without needing access to the reporting application.

Incoming Files for Application Processing

A partner submits files to Files.com, and an application needs to process them. A scheduled flow can use List Folders by Path to list an incoming folder, select files, and download their contents for the application's connector to process.

The flow must track which files the application has accepted so later runs do not process them again. For example, move accepted files to a processed folder. Downloading a file establishes that the flow received its contents; the application's result determines whether processing succeeded.

Document Delivery Without a User Account

An approval workflow can deliver documents stored on Files.com through a Share Link when a contact only needs browser access. After approval, the flow uses Create Share Link for the selected files, sets its expiration, and uses Create Share Link Recipient to send an email invitation.

The contact accesses the files without becoming a user on your site. The connector's API key needs permission to share those files, and the link follows your site's sharing controls.

Getting Started

The Files.com connector appears as an official connector inside both Power AutomateExternal LinkThis link leads to an external website and will open in a new tab and Azure Logic AppsExternal LinkThis link leads to an external website and will open in a new tab. Search for "Files.com" when adding it to a flow.

If Microsoft labels the connector Preview, review the connector listing for its available actions and current limitations before using it in a production flow.

Authentication

The connector requires a Files.com API Key to authenticateExternal LinkThis link leads to an external website and will open in a new tab and authorize actions.

For flows that only work with files and folders, use a dedicated non-administrator user with the required folder permissions and a Files Only key. Share Link, user, group, and other management actions require a Full Access key and the appropriate account permissions. Choose the key's path and Workspace scope for the locations the flow needs.

Connector Actions

The full list of connector actionsExternal LinkThis link leads to an external website and will open in a new tab lives on our Developer Portal pages for the Power Automate / Azure Logic Apps connectorExternal LinkThis link leads to an external website and will open in a new tab. Actions appear in the Power Automate and Azure Logic Apps catalogs.

Available actions include:

  • Files: upload, download, copy, move, and delete files.
  • Folders: create, list, copy, move, and delete folders.
  • Remote Servers, Snapshots, and Child Sites: upload, copy, and move files to these destinations.
  • Share Links: create, list, update, and delete secure share links to files and folders.
  • Users: create, list, update, and delete user accounts.
  • Groups: create, list, update, and delete groups.

Verifying a Run

Compare the flow's run history with Files.com API Logs to identify the action and path that completed or failed. If the path is mounted to a Remote Server with Buffered Uploads, upload completion can precede onward delivery. Before retrying a partial flow, check whether the destination already has the file or the application already processed it. The iPaaS guidance explains these completion and recovery boundaries.