Zoho WorkDrive files linked to CRM records, set up so your team keeps using it

Zoho WorkDrive files linked to CRM: the short answer

Zoho WorkDrive files linked to CRM means each deal, account or contact gets its own WorkDrive folder. You open that folder from the CRM record itself. There are two no-code routes. One is the Zoho WorkDrive for Zoho CRM extension from the Zoho Marketplace. The other is Zoho Flow, which can create the folder automatically when a record appears.

The connection is the easy part. Two other choices decide whether your team keeps using the folders after the first month. The first is a fixed folder structure that every record follows. The second is a set of permissions that match how people actually work on a deal.

This guide covers both routes and compares them in a table. It then sets out the folder and permission decisions and walks through a worked example in Zoho Flow. Finally, it lists the failure points to check before rollout. Still deciding whether WorkDrive is the right file store for your business? Start with our overview of Zoho WorkDrive implementation for UK teams.

What a CRM-linked WorkDrive folder is, and the parts involved

A CRM-linked folder is a Zoho WorkDrive folder tied to one CRM record. Files saved in it belong to that deal, account or contact, and anyone with access finds them from the record. Four parts make this work.

• Zoho WorkDrive is an online file management platform for teams. You use it to share files with colleagues and stakeholders, keep track of usage reports and secure folders with restricted access.
• Zoho CRM is Zoho's on-demand customer relationship management application. It holds your leads, contacts, accounts and deals.
• The WorkDrive section on the record is the area on a CRM record where linked folders and files appear once the extension is installed. Users describe it as the WorkDrive related list or related module.
• Zoho Flow is Zoho's integration tool. It sends information between Zoho WorkDrive and Zoho CRM automatically, without code.

Zoho Flow uses two terms you will meet throughout this guide. A trigger kicks off a flow, for example a new lead being created in Zoho CRM. Actions are the automated tasks that follow, for example creating a folder in WorkDrive. Every automatic folder in this guide is one trigger followed by a few actions.

Three ways to connect WorkDrive and CRM, compared

You can connect WorkDrive to Zoho CRM through the Marketplace extension, through Zoho Flow, or through a custom function that calls the WorkDrive API. The extension puts the folder on the record. Flow decides when folders are created and who can see them. A custom function gives full control but needs a developer.

Method	What it does	Code needed	What to watch
Zoho WorkDrive for Zoho CRM extension	Adds the WorkDrive section to CRM records. Files uploaded there sync to the computer for users who run desktop sync.	None	The folder does not appear by itself. Users have asked for one to be added as soon as each deal is created.
Zoho Flow	Creates folders and subfolders, updates share permissions and adds labels when CRM events happen.	None for prebuilt flows. Custom functions are optional.	Pick triggers that fire once, or use an action that checks for an existing folder.
Custom function calling the WorkDrive API	Creates folders from a CRM button or workflow.	Yes, plus an OAuth connection to WorkDrive	Scopes and configuration errors, such as error F6016.

Most small teams combine the first two. The extension gives salespeople the folder where they already work. Flow makes sure the folder exists before anyone needs it. A user on Zoho's forum described the extension as generally working "exactly" as needed, and the gap they raised was automatic creation. That gap is what Flow fills.

Folder structure: one fixed pattern per record type

A WorkDrive folder structure only works if every record follows the same pattern. Decide the pattern before the first folder exists. Renaming hundreds of folders later is slow, and people stop trusting folders that look different on every deal.

A workable pattern has three levels. At the top, keep one parent folder per record type, such as Accounts and Deals. In the middle, give each record its own folder, named from a field that never changes and never repeats. At the bottom, use the same fixed subfolders in every record folder.

Naming record folders

Name each folder after the record plus something unique, because two accounts can share a name. If a folder name can clash, Flow may attach the wrong folder or create a second one. The Zoho Flow action "Fetch or create folder" helps here. It fetches an existing folder, and creates a new one only if the folder does not exist.

Fixed subfolders

Zoho Flow's prebuilt flow for leads already creates a folder and a subfolder in WorkDrive for each new lead. Extend that idea with a short, fixed list of subfolders, such as Proposals, Contracts and Correspondence. Keep the list short. Every extra subfolder is one more place someone has to check.

Labels for status

Zoho Flow can also add a label to a WorkDrive resource when a CRM event fires. Use labels for status instead of moving folders around, so the path to a file never changes.

Permissions: who sees which folder, decided up front

WorkDrive permissions decide whether a linked folder helps your team or gets ignored. If people cannot open a folder they need, they save files to their desktop or email instead. If everyone can open everything, contracts and customer documents travel further than they should.

At Svennis we agree the folder naming pattern and the permission rule with the sales manager before we build the first flow. Changing access on folders that already hold files is the work clients most want to avoid.

Use this checklist to make the decisions before you connect anything.

Decision	Common choice	Why it matters
Who owns the parent folders	A shared team folder, not one person's private space	Files stay put when the person who created them leaves.
Who can edit a record folder	The team that works the record type, such as sales for deals	Editors can rename and move files, which breaks the fixed pattern.
Who can only view	Finance and management	They need the signed contract, not the drafts.
Which folders are restricted	Contracts and anything with personal data	WorkDrive lets you secure folders with restricted access.
When access changes	Automatically, through Flow, when a record is created	Zoho Flow can update the share permission of a file or folder when a new lead is created in Zoho CRM.

Plan for people leaving as well as joining. Our guide to offboarding a salesperson in Zoho CRM covers handing over records. Shared team folders mean the files go with the records rather than with the person.

Worked example: a deal folder created automatically by Zoho Flow

This example creates a WorkDrive folder for a deal at the moment documents start to arrive. The account is Harbour Joinery Ltd, and the deal is "Harbour Joinery: workshop fit-out". The goal is a folder with three subfolders, shared with the sales team, that appears without anyone creating it by hand.

1. In Zoho Flow, create a new flow. Choose Zoho CRM as the trigger app and pick the "Updated deal" trigger.
2. Add an if-then branch so the flow continues only when Stage equals the stage where documents begin, such as your proposal stage. Zoho Flow supports if-then branches and time delays as logic elements.
3. Add the Zoho WorkDrive action "Fetch or create folder". Set the parent to your Deals folder and build the folder name from the deal name plus a unique value.
4. Add three more "Fetch or create folder" actions for Proposals, Contracts and Correspondence, each with the deal folder as the parent.
5. Add the WorkDrive action that updates share permissions, and give the sales team access to the deal folder.
6. If you use labels for status, add the label action last.

The "Fetch or create folder" action matters because "Updated deal" fires every time the deal changes. If you used a plain create action, each edit could produce another folder. Because the action fetches the folder when it already exists, a second run finds the existing folder and moves on.

Test the flow on a single deal first. Edit the deal twice and check that WorkDrive still shows one folder. Then open the deal in CRM and confirm the folder is reachable from the record. Do not assume this works for your setup until you have seen it.

If a later step in another flow needs to look up a deal, note that the Zoho Flow "Fetch deal" action needs at least one of Account name, Contact name or Stage to be filled.

Signed documents: getting them back onto the CRM record

Signed contracts are the documents your team most often needs to find later, so route them into the record's folder deliberately. Zoho Sign's extension for Zoho CRM lets you send and collect signatures on documents such as proposals, vendor agreements, sales contracts and invoices.

Zoho Flow can also work in the other direction, from WorkDrive to CRM. A prebuilt flow creates a new module entry in Zoho CRM every time a signed document is uploaded to Zoho WorkDrive. WorkDrive also offers several triggers you can build on:

• folder created
• folder renamed
• file updated
• file moved
• file downloaded
• team folder created

A practical pattern is to save the signed contract into the deal's Contracts subfolder. A flow watching that folder then records the signature in CRM. Your pipeline then reflects what has been signed, rather than what someone remembered to update.

Placement on the record matters too. If the WorkDrive section sits at the bottom of a long page, people will not scroll to it. Our guide to redesigning Zoho CRM record pages with Canvas shows how to put the sections each team uses most where they can see them.

Common failure points when linking WorkDrive to CRM

Most WorkDrive and CRM links fail in a handful of predictable places. Check each one before you roll the setup out to the whole team.

Desktop sync is changing

Users value the fact that files uploaded to the WorkDrive section of a CRM record sync to their computer. Zoho is deprecating the legacy WorkDrive Desktop Sync app and moving users to WorkDrive TrueSync. Make sure laptops run TrueSync before you promise anyone local copies.

Prebuilt flows that do more than you expect

Read every prebuilt flow before you switch it on. Zoho Flow lists one that moves a specified file or folder to trash in WorkDrive whenever a new lead is created in Zoho CRM. That is useful in a narrow case and destructive in the wrong one.

Custom functions and the F6016 error

Writing your own function is possible but less forgiving. One user on the Zoho Community sent POST requests from a Zoho CRM button function to the WorkDrive folders endpoint at https://workdrive.zoho.com/api/v1/folders. Their OAuth connection had the scopes WorkDrive.workspace.ALL, WorkDrive.files.Create and WorkDrive.teamfolders.Create. They still received error F6016, "URL Rule is not configured".

If you take the custom route, budget time for authentication and configuration, not just the code. The Zoho Community thread on integrating Zoho CRM and WorkDrive shows the full exchange.

Duplicate folders

Duplicates come from triggers that fire repeatedly combined with create-only actions. Use "Fetch or create folder" wherever a trigger can run more than once.

What linking WorkDrive to CRM means for a UK firm

For a UK firm, the main gains from linked folders are control and continuity. Customer contracts, proposals and correspondence end up in one place with known access. Many UK teams work hybrid, with people moving between office, home and client sites. For them, a folder reachable from the CRM record on any device beats attachments scattered across inboxes.

Three points deserve attention in a UK setting.

• Personal data in documents. Contracts and onboarding files often name individuals. Restrict those subfolders deliberately rather than inheriting broad team access.
• Laptops and sync. Local copies are convenient for staff on the road. Decide who genuinely needs them, and move those machines to WorkDrive TrueSync.
• One file store, not two. If your team also keeps files in another system, decide which one is the master for customer documents. Then say so in writing.

Treat files as part of your CRM data, not something separate from it. When you plan recovery, our guide to backing up and restoring Zoho CRM data covers keeping records and their relationships intact. Check that the links between records and their folders survive a restore as well.

Next steps to link WorkDrive folders to your CRM records

Linking WorkDrive to CRM is a short project if you make the decisions first and build second. Work through these steps in order.

1. Write down your folder pattern: parent folders per record type, a unique naming rule and a fixed list of subfolders.
2. Fill in the permission checklist from this guide with your sales manager and whoever looks after finance.
3. Install the Zoho WorkDrive for Zoho CRM extension from the Zoho Marketplace so folders appear on records.
4. Build one flow in Zoho Flow for one record type, using "Fetch or create folder", and test it on a single deal.
5. Read every prebuilt flow before you switch it on, especially any that move files to trash or change sharing.
6. Move users who need local copies to WorkDrive TrueSync.
7. Roll out to the team and check after two weeks whether files are landing in the right subfolders.

If your CRM itself needs work before files can sit cleanly against records, start with the record structure. Our Zoho CRM implementation and consulting page explains how we approach that build for UK teams.

Sources

• Zoho Flow: Zoho WorkDrive and Zoho CRM integrations
• Zoho Flow: WorkDrive and CRM triggers and actions
• Zoho Community: Integrate Zoho CRM and Zoho WorkDrive
• Zoho: CRM and WorkDrive, automatically add folder to WorkDrive related list