Resources · Make integration

Zoho WorkDrive Make integrationAutomate Zoho WorkDrive with Make.

What if new files in WorkDrive sorted themselves into the right folder? The Zoho WorkDrive Make integration gives you 19 modules: 2 triggers, 14 actions and 3 searches. This guide is for ops and admin teams, and walks you from the connection to a first working scenario.

Try the Zoho WorkDrive integration on MakeSee the 19 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Zoho WorkDrive Make integration do for you?

The Zoho WorkDrive Make integration links your WorkDrive account to Make, a no-code tool where you chain apps together in a scenario, the automation you build. Make spots new files or folders in WorkDrive, then creates, moves, renames or uploads content for you, with no script to write.

A client space that builds itself. When someone adds a folder for a new client, Watch folders in a folder picks it up and Create a folder adds the sub-folders your team always needs, like Contracts and Invoices. Nobody forgets one again.

An inbox folder that empties on its own. Watch files in a folder sees each upload to a drop folder, and Move a file or folder sends it to the right place. Rename file or folder can fix the name on the way, so the archive stays readable.

Files that travel between tools. Download a file hands a WorkDrive document to another app in the scenario, for example to attach it to an email, and Upload a file does the reverse for documents coming from elsewhere. If you log projects in a base, the Airtable Make integration pairs well here.

What the integration does not do: both triggers are scheduled, so Make checks WorkDrive on a timer instead of hearing about changes the moment they happen. Zoho WorkDrive also has an n8n node; if you are weighing the two tools, read n8n vs Make. To check which plan fits, see Make pricing.

Connect

How do you connect Zoho WorkDrive to Make?

  1. 01

    Add a WorkDrive module

    In a scenario, add any Zoho WorkDrive module and click Create a connection. A connection is your WorkDrive account linked to Make once, then reused by every WorkDrive module you add later. You need an active WorkDrive account first.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name helps when several people or accounts share the same Make organization. Something like "WorkDrive, finance team" tells everyone which account a scenario really uses.

  3. 03

    Sign in and authorize

    Follow the on-screen instructions to sign in to Zoho and allow access. If you prefer your own OAuth client, open the Zoho API console, create a client, set the callback URI below, then paste the Client ID and Client secret into Make.

First scenario

Your first scenario: a client folder with its sub-folders

GoalWhen a new folder appears in your Clients folder in Zoho WorkDrive, Make creates the sub-folders your team expects inside it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Search for Zoho WorkDrive and pick Watch folders in a folder as the first module.

  2. 02

    Pick the folder to watch

    Select your connection, then choose the parent folder where client folders are created. No need to type a path: once the connection exists, Make lists the folders it can read.

  3. 03

    Add the sub-folder action

    Click the + on the right of the trigger and add Create a folder. For the parent folder, map the new client folder from the trigger, then type the sub-folder name, for example Contracts.

  4. 04

    Test with Run once

    Create a test client folder in WorkDrive, then click Run once. Open the bubble above each module to read the bundle it received, one bundle per folder, and check the sub-folder appeared.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Add more Create a folder modules if you need several sub-folders.

Triggers

What starts a Zoho WorkDrive scenario

2 modules start a scenario when something happens in Zoho WorkDrive. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Zoho WorkDrive as soon as it happens.

Zoho WorkDrive1Watch files in a folder

Watch files in a folder

Scheduled trigger

In Make“Triggers when a new file in folder has been created.”

This trigger hands your scenario every file newly created in the folder you pick, one bundle per file, so each upload can be filed, renamed or copied elsewhere without anyone touching it.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and at least 15 minutes apart on the Free plan.
When to use it
a shared drop folder where colleagues or clients put scans and invoices that need sorting.
Watch out
if a later module uploads or moves files back into this same folder, they count as new files at the next check; send them to another folder.
Zoho WorkDrive2Watch folders in a folder

Watch folders in a folder

Scheduled trigger

In Make“Triggers when folder in a folder has been created.”

Here the scenario starts whenever a new folder shows up inside a parent folder, which makes it the natural starting point for anything tied to a new project, client or case.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a folder created right after a check waits for the next one.
When to use it
a Projects folder where each new sub-folder should get the same structure, a tracking row in another tool and a message to the team.
Watch out
files arriving in that parent folder do not trigger it; pair it with Watch files in a folder if you need both.
Modules

Everything Zoho WorkDrive can do in Make

Zoho WorkDrive gives you 17 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Zoho WorkDrive1

Create a folder

Action

In Make“Creates a folder.”

You get a brand new folder, created where you say, and its ID ready for the next modules to drop files into it.

When to use it
a signed quote or a new hire should open a dedicated space, so documents never land loose at the root.
Watch out
map the parent folder from the previous module rather than picking one by hand, or every run writes to the same place.
Zoho WorkDrive2

Create a team folder

Action

In Make“Creates a team folder.”

This module sets up a whole team folder, the shared space a group of people works in, instead of a simple sub-folder inside an existing one.

When to use it
each new department, agency client or long project deserves its own shared space with its own members.
Watch out
pick Create a folder when a sub-folder is enough; team folders are heavier to manage and clean up later.
Zoho WorkDrive3

Delete a team folder

Action

In Make“Deletes a team folder.”

Removes an entire team folder, which keeps the list of shared spaces short once a project or engagement is closed for good.

When to use it
at the end of an archived project, after its files have been copied or exported elsewhere.
Watch out
a delete step is hard to undo, so add a filter before it and run it with Run once on a test team folder first.
Zoho WorkDrive4

Download a file

Action

In Make“Downloads a selected file.”

Brings the content of a WorkDrive file into the scenario, so another app can use the file itself and not just its name or link.

When to use it
attaching a contract to an email, sending a PDF to an e-signature tool or copying a document to another storage.
Watch out
on the Free plan Make handles files up to 5 MB, so check your plan before handling large videos or archives.
Zoho WorkDrive5

Empty a team folder trash

Action

In Make“Clears the files and folders in the team folder trash permanently.”

Clears out everything sitting in a team folder's trash, permanently, which frees space and removes old drafts nobody should restore.

When to use it
as the last step of a cleanup scenario, once files have already been moved to trash by an earlier module.
Watch out
there is no way back after this step, so keep it off test scenarios and check which team folder is mapped.
Zoho WorkDrive6

Get a file or folder

Action

In Make“Retrieves file or folder data.”

Fetches the details of one file or folder you already know, so the following modules can read its name, location or other data.

When to use it
another app sends you a WorkDrive ID, for example from a form or a CRM, and you need the item behind it.
Watch out
it needs the exact item; if you only know part of a name, use Search files and folders in a folder instead.
Zoho WorkDrive7

Get a team folder

Action

In Make“Retrieves a team folder.”

Returns the information of a single team folder, handy when a scenario must check a shared space before touching it.

When to use it
before renaming or deleting a team folder, to confirm it is the right one and read its current details.
Watch out
this reads one known team folder; to browse all of them, Search team folders is the module to add.
Zoho WorkDrive8

Make an API call

Action

In Make“Perform an arbitrary authorized API call.”

Lets you call any endpoint of the WorkDrive API with the connection you already set up, which covers what the listed modules do not.

When to use it
you need a WorkDrive feature that none of the 19 modules offers and do not want a second connection.
Watch out
you write the request yourself from the Zoho WorkDrive API documentation, so test it with Run once before relying on it.
Zoho WorkDrive9

Move a file or folder

Action

In Make“Moves a file or folder to a new destination folder in WorkDrive.”

Sends a file or folder to another WorkDrive folder, which is how an intake folder gets sorted without anyone dragging items around.

When to use it
right after Watch files in a folder, to route each new document to its client or project folder.
Watch out
never move files into the folder your trigger watches, or the same items could come back into the scenario.
Zoho WorkDrive10

Move a file or folder to trash

Action

In Make“Trashes a file or a folder and moves it to the trash folder.”

Puts an item in the trash rather than erasing it, so a mistake can still be recovered by hand from WorkDrive.

When to use it
removing temporary exports or duplicates once another module has copied what matters.
Watch out
prefer this over Empty a team folder trash whenever you want a safety net, and filter carefully before it runs.
Zoho WorkDrive11

Rename file or folder

Action

In Make“Changes name of a file or folder.”

Gives a file or folder a new name built from data in the scenario, so everyone finds documents under the same convention.

When to use it
scans arrive as IMG names and should read as client, document type and date instead.
Watch out
map the new name from earlier modules; a fixed text would give every file in the run the same name.
Zoho WorkDrive12

Update a team folder description

Action

In Make“Updates a team folder description.”

Rewrites the description of a team folder, a small detail that tells members what the space is for and what state it is in.

When to use it
a project changes stage in your CRM or tracker and the team folder should show it, for instance Closed or On hold.
Watch out
the new text replaces the old one, so include anything from the previous description you want to keep.
Zoho WorkDrive13

Update a team folder name

Action

In Make“Updates a team folder name.”

Changes the name of a team folder so it keeps matching the client, project or department it belongs to.

When to use it
a client renames its company or a project gets its final title, and the shared space should follow.
Watch out
people and other tools may know the folder by its old name; Get a team folder first helps confirm you target the right one.
Zoho WorkDrive14

Upload a file

Action

In Make“Uploads a file in your WorkDrive folder.”

Stores a file coming from another app in the WorkDrive folder of your choice, so attachments and exports stop living in inboxes.

When to use it
invoices received by email, generated PDFs or form attachments that belong in a shared folder.
Watch out
the module needs the file content, not a link; on the Free plan files are limited to 5 MB.
Zoho WorkDrive15

List file comments

Search

In Make“Retrives list of a file comments.”

Pulls the comments left on a file, one bundle per comment, so feedback written in WorkDrive can reach the people or tools that act on it.

When to use it
reviewers comment on a draft and you want those remarks gathered in a task or a message.
Watch out
a file with no comment returns zero bundles, so later modules simply do not run for it.
Zoho WorkDrive16

Search files and folders in a folder

Search

In Make“Searches for files and folders in a specified folder.”

Looks inside a folder and returns the matching files and folders, useful when a scenario must find an item it does not have an ID for.

When to use it
before creating a client folder, to check it is not already there.
Watch out
a search can return zero, one or several items; add a filter before acting on the results.
Zoho WorkDrive17

Search team folders

Search

In Make“Retrieves all team folders in a team.”

Lists the team folders of a team, one bundle each, which gives a scenario the full picture of your shared spaces.

When to use it
an audit sheet of every team folder, or a loop that updates descriptions across all of them.
Watch out
each returned team folder counts as a bundle, and every module after it runs once per bundle, which adds operations.
Need help

Need help automating Zoho WorkDrive with Make?

A person reads every message.

FAQ

Zoho WorkDrive and Make: common questions

01Is the Zoho WorkDrive Make integration free?
Yes, Zoho WorkDrive is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, runs at most every 15 minutes, stops a run after 5 minutes and handles files up to 5 MB, with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and count usage in credits, meaning operations, per month. You still need your own active WorkDrive subscription on the Zoho side.
02What do you need to connect Zoho WorkDrive to Make?
An active Zoho WorkDrive account and the right to authorize API access on it. In Make, add a WorkDrive module, click Create a connection, give it a name if you like and follow the Zoho sign-in. If you want your own OAuth client, create it in the Zoho API console with the callback URI shown by Make's documentation, then paste the Client ID and Client secret into the connection. The connection is then shared by every WorkDrive module.
03Does the Zoho WorkDrive trigger in Make run in real time?
No. Both Watch files in a folder and Watch folders in a folder are scheduled triggers: Make checks WorkDrive on the scenario's schedule and picks up whatever appeared since the last check. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans let you go down to 1 minute if new files must be handled sooner. A file added right after a check simply waits for the next one.
04What if a Zoho WorkDrive action is missing in Make?
Use the Make an API call module. It calls any endpoint of the WorkDrive API with the connection you already created, so you are not limited to the 19 listed modules. You build the request from the Zoho WorkDrive API documentation and test it with Run once. For large files, remember the Free plan caps them at 5 MB, so check the file limit of your plan before you switch the scenario on.
05Should you use Make or n8n for Zoho WorkDrive?
It depends on the tool your team already works in. Make offers 19 ready modules for WorkDrive, with two scheduled triggers and an API call module for the rest, all in a visual editor. Zoho WorkDrive also has an n8n node, so both tools can handle files and folders. Compare the modules each one offers against your actual scenario rather than picking on reputation. A good test is to build your first scenario in each and see which one your team reads more easily.
Same platform

Other docs you might need on this stack.

Browse all integrations