Files.com Make integrationAutomate Files.com with Make.
Tired of creating Files.com users and folder access by hand? The Files.com Make integration gives you 18 modules: 3 triggers, 12 actions and 3 searches. This guide is for admins who run Files.com and want to connect it, build a first scenario and pick the right module.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Files.com Make integration automate?
The Files.com Make integration links your Files.com account to Make, a visual tool where you chain apps together without code. Make can spot new uploads, users and groups, then create, update or delete users, groups and permissions, or push a file into Files.com, all from one connection.
Onboarding without the checklist. Watch Users notices each new account, and Create a Permission hands it the access it needs. Add Update a User when a profile needs a follow-up change.
Files that land where the team expects them. A document produced by another app (a signed contract, an export) goes to Files.com through Upload a File. On the other side, Watch File Uploads starts a scenario whenever a file reaches the folder you picked, so a partner drop can alert the right person.
Clean access reviews. Search Users, Search Groups and Search Permissions pull the current state into a sheet or a report, and Delete a Permission removes what should no longer exist.
Two limits matter. All three triggers are scheduled, so Make checks Files.com on the scenario's schedule rather than instantly. And Make flags its own Files.com documentation as AI-generated, so confirm important details with Files.com. For anything the listed modules skip, Make an API Call reaches the rest of the API. The same app often has an n8n node too; the n8n vs Make page compares both tools, and the Make review covers Make in depth. To go further on your own, see Make training.
How do you connect Files.com to Make?
- 01
Generate your API key
In Files.com, open Settings, then API Keys. Click Generate API Key if no key exists yet, and copy the key shown on screen. You need an active Files.com account for this.
- 02
Add a Files.com module
In your Make scenario, add any Files.com module and click Create a connection. A connection is your Files.com account linked to Make once, then reused by every Files.com module you add later.
- 03
Paste the key and save
Give it a clear label in Connection name if you like (optional), paste the API key you copied, and follow the on-screen instructions. Make then lists the Files.com objects it can read.
Your first scenario with Files.com
GoalWhen a new user appears in Files.com, Make creates the permission that user needs.
- 01
Create the scenario
On the Scenarios page, create a new scenario, the automation you build in Make, then click the + to place the first module, one brick of the chain.
- 02
Pick Watch Users
Search for Files.com, choose Watch Users and click Create a connection to link your account with the API key. This trigger starts the scenario when a new user shows up.
- 03
Add Create a Permission
Click the + to the right of the trigger and pick Create a Permission. Map the user coming from Watch Users into it, then fill the rest of the module fields.
- 04
Test with Run once
Create a test user in Files.com, then click Run once. Each module shows the bundles it received, one bundle per user, so you can check the permission before going live.
- 05
Schedule and switch on
Open the clock on Watch Users: a new scenario checks every 15 minutes by default. Keep it or change it, then switch the scenario on so it keeps running without you.
What can start a Files.com scenario?
3 modules start a scenario when something happens in Files.com. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Files.com as soon as it happens.
Watch File Uploads
Scheduled triggerIn Make“Triggers when a new file is uploaded to a specific folder.”
Watch File Uploads starts your scenario each time a new file arrives in the Files.com folder you choose, so whatever comes next (a notification, a copy, a log) runs on that file without anyone opening the folder.
Watch Groups
Scheduled triggerIn Make“Triggers when a new group is created.”
Watch Groups gives you a starting point whenever someone creates a new group in Files.com. Every new group becomes one bundle, the item passed to the next module, ready to be logged or completed.
Watch Users
Scheduled triggerIn Make“Triggers when a new user is created.”
Watch Users hands you each newly created Files.com account at each check Make runs, which makes it the natural first brick of any onboarding flow: welcome message, permission, entry in the HR tracker.
What can Make do in Files.com?
Files.com gives you 15 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Create a Group
ActionIn Make“Creates a new group.”
Create a Group sets up a new Files.com group from your scenario, so a team, a client or a project gets its group the moment the event behind it happens elsewhere.
Create a Permission
ActionIn Make“Creates a new permission.”
With Create a Permission, access stops being a manual ticket: the scenario writes the permission itself, right after the user or group it concerns exists in Files.com.
Create a User
ActionIn Make“Creates a new user.”
Create a User opens a Files.com account from data held in another app, so nobody retypes names and emails into the admin screen.
Delete a Group
ActionIn Make“Deletes a group by ID.”
Delete a Group removes a Files.com group by its ID, which keeps your group list short once a project or a client relationship ends.
Delete a Permission
ActionIn Make“Deletes a permission by ID.”
Delete a Permission withdraws one access by its ID, the cleanest way to close a door without touching the user or the group behind it.
Delete a User
ActionIn Make“Deletes a user by ID.”
Delete a User closes a Files.com account by its ID, so offboarding in your HR tool also shuts the file access without a separate reminder.
Get a Group
ActionIn Make“Gets a single group by ID.”
Get a Group reads the details of one Files.com group by its ID, which gives the next modules fresh information instead of whatever an older step carried.
Get a User
ActionIn Make“Gets a user's details by ID.”
Get a User fetches the full details of one Files.com account by its ID, handy when an earlier module only passed the ID along.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
Make an API Call is your way out when none of the 18 listed modules does what you need: it calls any endpoint of the Files.com API with the connection you already set up.
Update a Group
ActionIn Make“Updates a group by ID.”
Update a Group changes an existing Files.com group by its ID, so a renamed team or a reorganised department is reflected without anyone editing it by hand.
Update a User
ActionIn Make“Updates a user by ID.”
Update a User edits an existing Files.com account by its ID, keeping the profile in step with the app where people actually maintain it.
Upload a File
ActionIn Make“Uploads a file.”
Upload a File drops a file coming from another module straight into Files.com, so exports, signed contracts or generated reports end up in the folder your team already uses.
Search Groups
SearchIn Make“Searches for specific groups or lists them all.”
Search Groups finds specific Files.com groups, or lists them all, and gives you their IDs for the modules that follow.
Search Permissions
SearchIn Make“Searches for specific permissions or lists them all.”
Search Permissions lists who can access what in Files.com, or narrows it to the permissions you target, which is the raw material for any access review.
Search Users
SearchIn Make“Searches for specific users or lists them all.”
Search Users looks up Files.com accounts, one person or the whole list, and is the usual way to get the ID that the Get, Update and Delete modules require.
Need help automating Files.com with Make?
A person reads every message.
