FileCloud Make integrationAutomate FileCloud with Make.
Can Make keep your FileCloud folders tidy without you touching them? The FileCloud Make integration gives you 1 trigger and 3 actions. This page is for teams who already store files in FileCloud and want Make to spot new ones, create folders and upload documents on its own.
Verified Trustpilot reviews · AI, automation & growth agency
What does the FileCloud Make integration let you automate?
The FileCloud Make integration links your FileCloud account to Make, so a scenario (the automation you build in Make, a chain of steps) can notice a file that lands in a folder, create a new folder at a path you choose, or upload a file from another app. You set it up in the visual editor, without writing code.
A client folder that builds itself. When a deal is signed in your CRM, Create a Folder opens a folder named after the client, and Upload a File drops the signed contract inside it. Nobody on the sales team has to remember the folder structure.
An alert when a document arrives. Watch Files keeps an eye on a shared folder and starts the scenario for every new file, so you can post a message to your team chat or log the file name in a spreadsheet.
Attachments that stop living in inboxes. An email or a form submission brings a PDF; Upload a File sends it straight to the right FileCloud folder, For the form side, the 123FormBuilder Make integration covers that first half.
Know the limits before you start. Make's own documentation for FileCloud is marked as limited: it lists the modules but gives no connection steps, no field reference and no troubleshooting notes. For anything the three actions do not cover, Make an API Call reaches other endpoints of the FileCloud API with the same account link. If you are still weighing tools, the n8n vs Make comparison and the Make pricing guide help you decide before you build.
How do you connect your FileCloud account to Make?
- 01
Add a FileCloud module
In a scenario, click the +, search for FileCloud and pick any of its modules. Then click Create a connection. A connection is your FileCloud account linked to Make once, and every FileCloud module in your scenarios reuses it.
- 02
Name it and authorize Make
Give the connection a name if you like, such as the workspace it points to. Then follow what the window asks: either sign in on FileCloud's page to let Make in, or paste the key FileCloud gives you.
- 03
Save and check the folder list
Click Save. Back in the module, Make should now offer your FileCloud folders to pick from. If the list shows up, the connection works and you can move on to the next field.
Your first scenario with FileCloud: a client folder with its first document
GoalWhen a file arrives from another app, Make creates a folder in FileCloud and uploads the file into it.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the +. Pick the app that receives your files first, for example your email or form tool, as the starting module.
- 02
Add Create a Folder
Click the + on the right of that first module, search for FileCloud and choose Create a Folder. Create your connection, then set the path and map the client name from the previous module.
- 03
Add Upload a File
Add one more module: Upload a File. Point it at the folder you just created and map the file coming from the first app. Each file travels as a bundle, one item passed from module to module.
- 04
Test with Run once
Click Run once, then send a real test file through the first app. Open the bubbles above each module to read the bundles they received and check the new folder in FileCloud.
- 05
Schedule and switch it on
Click the clock on the first module to set the schedule, which is every 15 minutes by default. Then switch the scenario on so it keeps running without you.
What starts a FileCloud scenario
1 module starts a scenario when something happens in FileCloud. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by FileCloud as soon as it happens.
Watch Files
Scheduled triggerIn Make“Triggers when a file is created in a selected folder.”
Watch Files gives you one bundle per new file that appears in the folder you pick, so a scenario can react to fresh documents without anyone forwarding them. Everything after it (a message, a log line, a copy elsewhere) runs once per file.
What Make can do in FileCloud
FileCloud gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Create a Folder
ActionIn Make“Creates a folder in a particular path.”
You get a ready folder at the path you set, created the moment the scenario runs, so each new project or client starts with its own place in FileCloud. Map the folder name from an earlier module and the structure stays consistent.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
This module lets you reach any endpoint of the FileCloud API from your scenario, using the connection you already created. It is your way around the short module list when you need something the other two actions do not offer.
Upload a File
ActionIn Make“Uploads a file to the selected folder. Files with the same name have "upsert" logic.”
Upload a File puts a file coming from another module into the FileCloud folder you choose, so attachments, exports or generated PDFs end up stored where your team looks for them. It is the module most scenarios with FileCloud finish on.
Need help automating FileCloud with Make?
A person reads every message.
