Make (formerly Integromat)

Use Files.com modules in a Make scenario when application data needs to become a file, or a received file needs to enter an application workflow. The scenario coordinates the modules and application processing; Files.com holds or exposes the files and controls access for the people and systems exchanging them.

Make's integration is supported entirely by Make, in contrast to our Zapier integration and other first-party integrations that Files.com builds and maintains. We are happy to assist with Make issues where we can.

When creating a scenario in Make, select Files.com from the supported modules and connect with a Files.com API key. For file and folder operations, use a dedicated non-administrator user with the required folder permissions and a Files Only key. User-management actions require a Full Access key and the corresponding administrative permissions.

Make supports Files.com actions such as uploading files and creating and updating users. The full list of supported triggers, actions, and searches is available on the Files.com integration page of the Make web site.

An upload module publishes file contents to the chosen Files.com path; it does not establish that a partner retrieved them or an application accepted them. Check the scenario's execution result and Files.com API Logs for the module's operation, then verify the next system's result where required. The iPaaS guidance explains mounted storage, buffered delivery, and recovery when only part of a workflow completed.