Skip to main content

Connecting Zoho WorkDrive

This guide walks you through connecting a Zoho WorkDrive storage destination to Pluton.

Prerequisites

Before connecting Zoho WorkDrive, you need:

  1. A Zoho account with WorkDrive access - Sign up here
  2. A Zoho API Console application with OAuth 2.0 credentials
  3. Client ID and Client Secret from the Zoho API Console

Getting Your Credentials

Step 1: Create a Zoho API Application

  1. Go to the Zoho API Console
  2. Click Add Client
  3. Select Server-based Applications (or Self Client for testing)
  4. Fill in the required details:
    • Client Name: e.g., "Pluton Backups"
    • Homepage URL: Your server URL
    • Authorized Redirect URI: http://127.0.0.1:53682/
  5. Click Create

Step 2: Copy Your Credentials

  1. After creation, you will see the Client ID and Client Secret
  2. Copy both values — you will need them in Pluton

Step 3: Generate an OAuth Token

Since Pluton runs on a server that may not have a web browser, you need to generate an OAuth token using rclone authorize:

  1. Install rclone on a machine with a web browser
  2. Run the following command:
    rclone authorize "zoho" "your_client_id" "your_client_secret"
  3. A browser window will open — log in with your Zoho account and grant access
  4. You may be asked to select a Team and Workspace — choose the appropriate ones
  5. Copy the JSON token blob printed to the terminal

Connecting to Pluton

Pluton Zoho WorkDrive

Step 1: Add Storage

  1. In Pluton, navigate to Storages
  2. Click Add Storage button
  3. Select Zoho WorkDrive from the provider list

Step 2: Configure Connection

Fill in the required fields:

  • Storage Name: A friendly name (e.g., "Zoho WorkDrive Backups")
  • Client ID: Your Zoho OAuth Client ID
  • Client Secret: Your Zoho OAuth Client Secret
  • Region: Select the Zoho region your organization is registered in:
    • United States / Global (zoho.com)
    • Europe (zoho.eu)
    • India (zoho.in)
    • Japan (zoho.jp)
    • China (zoho.com.cn)
    • Australia (zoho.com.au)
  • OAuth Access Token: Paste the JSON token blob obtained from rclone authorize
tip

To determine your correct region, check the URL you use when logging into Zoho. For example, if you access WorkDrive at workdrive.zoho.eu, select Europe.

Step 3: Advanced Options (Optional)

Additional settings available:

  • Client Credentials: Enable to use the OAuth2 Client Credentials flow instead of interactive login
  • Upload Cutoff: Cutoff for switching to large file upload API (default: 10 MiB)

Step 4: Test and Save

  1. Click Test Connection to verify credentials
  2. If successful, click Save
  3. Your Zoho WorkDrive storage is now ready for backup plans

Common Issues

Wrong Region Selected: If you get authentication errors, verify you selected the correct Zoho region. Your region must match where your Zoho organization is registered for the OAuth token to work.

Token Expired: Zoho OAuth tokens expire periodically. Re-run rclone authorize "zoho" with your Client ID and Client Secret to generate a fresh token.

Team/Workspace Not Found: During the rclone authorize flow, you need to select a Team and Workspace. If you don't see the expected options, ensure your Zoho account has WorkDrive enabled and you're a member of the appropriate team.

API Console Domain Mismatch: Ensure you created your API app in the same regional Zoho API Console that matches your account. For example, use api-console.zoho.eu for European accounts.

Insufficient Permissions: Verify your Zoho account has the necessary permissions to access WorkDrive. Admins may need to enable API access for your organization.

Best Practices

  • Always select the correct region matching your Zoho organization to avoid authentication issues
  • Create a dedicated Zoho API application specifically for Pluton
  • Consider using the Client Credentials flow for unattended server-to-server operations
  • Verify your WorkDrive storage quota before configuring large backup plans
  • Use a descriptive storage name in Pluton to easily identify the connection among multiple storages