Zoho WorkDrive

Connect AI agents to Zoho WorkDrive cloud storage. Agents upload and download files, browse folder contents, create, rename, move, and trash files and folders, and enumerate teams and team folders to keep shared workspaces organized.

10 actions OAuth available

Zoho WorkDrive website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

A workflow finishes producing a document, an invoice, a report, a signed contract

List Team Folders resolves the shared workspace for the client or department

List Folder Contents checks whether this month's folder already exists

Create Folder builds it when missing, named to the team's convention

Upload File streams the document into place from its URL

Agent verifies the upload with Get File or Folder Metadata and captures the permalink

The team channel gets the file name and permalink so nobody asks where it went

A reviewer spot-checks filings the agent flags as ambiguous, a client name that matches two folders, a duplicate file name

What This Integration Enables

Zoho WorkDrive is shared storage, which means every file operation an agent performs is visible to a whole team, for better and for worse. The productive read on that: WorkDrive is where a Zoho-suite business keeps its filing system, and filing is exactly the kind of work that should never have needed a person. FlowRunner agents put documents where they belong the moment they exist, pull files back out to feed parsing and signature steps, and keep workspace structure from decaying. - Upload generated reports, invoices, and exports into team folders from any workflow - Download files into FlowRunner storage to feed parsing, emailing, or archiving steps - Create folders, rename, move, and trash items to keep shared workspaces organized - Browse team folder contents and act on each entry by ID - Enumerate teams and team folders, and confirm which account a connection is bound to Because the workspace is shared, destructive operations carry team-wide blast radius. FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) step keeps trash decisions with a person while the agent does the sweeping.

Without FlowRunner

Filing is a human afterthought Reports and contracts get generated, then sit in downloads folders until someone remembers to file them

Folder structure drifts Every person files by their own convention, and six months later nobody can find anything

Cleanup never happens Stale drafts and duplicates accumulate in team folders because nobody owns deleting them

With FlowRunner

Documents file themselves Every artifact a workflow produces lands in the right team folder, named to convention, with a permalink posted

Structure is enforced by the agent Folders are created from one convention, every time, because the same flow does the filing

Cleanup runs as a supervised sweep Agents propose what to trash with evidence, and a person approves before anything leaves view

Use Case Scenarios

Every order document filed before fulfillment asks

An order lands in [Shopify](/integrations/shopify). The flow generates the packing slip and invoice, then the agent resolves the fulfillment workspace with List Team Folders, ensures the order-month folder exists via List Folder Contents and Create Folder, and calls Upload File for each document. The permalink from Get File or Folder Metadata gets posted to [Slack](/integrations/slack). Fulfillment opens one folder and finds everything, every time.

The contract that routes itself for signature

A deal reaches the contract stage. The agent finds the template in the legal team folder with List Folder Contents, pulls it into FlowRunner storage with Download File, and hands the URL to the signature step or attaches it to a [Gmail](/integrations/gmail) draft for counsel to review first. When the signed copy comes back, Upload File places it in the client's folder and Rename or Move File stamps it to the naming convention. The executed contract is findable the day it is signed.

The quarterly workspace cleanup that actually happens

On a schedule, the agent walks each team folder with List Folder Contents, pulls Get File or Folder Metadata for each entry, and builds a list of candidates: files unmodified in a year, duplicate names across drafts folders, empty folders. It posts the list with sizes and timestamps to the workspace owner. Approved items get Delete File or Folder, which moves them to Trash, and Rename or Move File consolidates the survivors into an archive folder. The workspace stays navigable without anyone spending a Friday on it.

Human-in-Loop Highlight

Delete File or Folder moves an item to WorkDrive Trash, and in a shared workspace that is not a private act: the file disappears from every teammate's view at once, and Trash is a waiting room, not a safety net, because trashed items get permanently removed. A cleanup agent aiming that operation at a team folder can take a live proposal draft out from under the person presenting it tomorrow. So the sweep never trashes on its own judgment. It posts: "14 candidates in the Sales workspace: 9 files untouched for 13 months, 3 duplicate drafts of the Q3 deck, 2 empty folders. Full list with timestamps attached. Trash which?" The workspace owner picks, the agent trashes exactly those, and the flow logs what left and why. The same caution applies to Upload File with overwrite enabled, which replaces a same-named file's current revision: agents overwrite only when the flow explicitly versions.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

10 actions

Files and Folders

List Folder Contents Lists the files and sub-folders inside a folder or team folder, with IDs, names, and timestamps. The browsing step behind filing, sweeps, and lookups.
Get File or Folder Metadata Retrieves one item's name, type, size, timestamps, and permalink. Used to verify uploads and to gather evidence for cleanup decisions.
Create Folder Creates a folder inside a parent, returning its ID for subsequent uploads. The step that enforces one naming convention instead of five.
Rename or Move File Renames a file or folder, moves it to a new parent, or both. The consolidation write behind archive workflows.
Delete File or Folder Moves an item to WorkDrive Trash, recoverable until permanently removed. The operation this page's human gate exists for.
Upload File Streams a file into a WorkDrive folder from a public URL, with optional overwrite of a same-named file. The filing step for every document a workflow produces.
Download File Downloads a file into FlowRunner file storage and returns a public URL for later steps. The bridge that feeds WorkDrive content into parsing, signature, and email flows.

Team and Workspace

Get Current User Retrieves the connected account's display name, email, and user ID. Used to confirm which account a connection is bound to before writes run.
List Teams Lists the teams the account belongs to, with IDs and names.
List Team Folders Lists the top-level shared workspaces available to the account. The resolution step before any team folder operation.

Frequently Asked Questions

What can FlowRunner do with Zoho WorkDrive?

FlowRunner agents can run List Folder Contents, Get File or Folder Metadata, and Create Folder in Zoho WorkDrive, plus 7 more actions.

Does connecting Zoho WorkDrive to FlowRunner require OAuth?

Yes. Zoho WorkDrive connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Zoho WorkDrive trigger a FlowRunner workflow automatically?

Zoho WorkDrive doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Zoho WorkDrive

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us