Deluge Forge
Write, run and manage Zoho Deluge code for CRM, Books and Creator without leaving your editor.
Zoho's in-browser script editor is fine for a quick fix. It is a poor place to live all day: no real search, no version control, no linting worth the name, and every function hides behind another click. Deluge Forge brings your Deluge functions into VS Code as ordinary .dg files, keeps them in sync with Zoho, and lets you run them against your real organization with one keystroke.
- Edit locally. Pull every function of an organization into a workspace folder, work on it with syntax highlighting, completion, diagnostics and an outline, then push it back.
- Run for real. Execute the function you are looking at against your Zoho organization and read the result and the logs next to your code.
- No API keys to create. Deluge Forge reuses the Zoho session you already have open in Chrome. Nothing to register in the Zoho developer console.
- One editor, three products. Zoho CRM, Zoho Books and Zoho Creator, side by side, each organization in its own workspace.
🧭 How it works
Zoho tab in Chrome
| the Deluge Forge Chrome extension reads your signed-in session
v
Chrome Native Messaging (local to your computer, no network)
|
v
Deluge Forge in VS Code -----> Zoho CRM, Books and Creator, as you
The Chrome extension captures the Zoho session from a tab you already have open and hands it to this extension through Chrome's local Native Messaging channel. This extension keeps it encrypted on your disk and uses it to talk to Zoho on your behalf. You pair the two once, with a short code.
✅ Requirements
| You need |
Notes |
| VS Code 1.100 or newer |
Compatible editors such as Antigravity load it too. |
| Google Chrome |
Install the Deluge Forge Chrome extension from the Chrome Web Store. The local host is also registered for Edge and Brave. |
| Node.js 22 or newer on your PATH |
The small local host that receives the session from Chrome runs on it. Check with node --version in a new terminal. |
| A Zoho account you can sign in to |
CRM, Books or Creator, on any of the supported data centers listed below. |
| A Google account |
Used to sign in and activate the licence on this computer. |
Supported computers: macOS and Linux. Windows is supported too and is new: it has been verified on one Windows machine so far.
🚀 Quick start
The Getting Started walkthrough opens once, the first time the extension activates with a licence, and follows the same four steps. You can reopen it from Help, Welcome, Open Walkthrough.
- Sign in. Run
Deluge Forge: Sign in and sign in with your Google account. The extension starts with a trial. If your request has to be approved first, you will be told, and you can sign in again once it is.
- Pair the browser. Run
Deluge Forge: Setup. A dialog shows a pairing code. Open the Deluge Forge Chrome extension's popup and paste it there. You do this once per browser profile.
- Open Zoho. In the paired Chrome profile, open a Zoho tab you are already signed in to. The Chrome extension captures the session from it. This step is done when the editor has a Zoho session saved.
- Add a workspace. Run
Deluge Forge: Add Workspace. A workspace is one Zoho organization on this computer. Deluge Forge pulls its functions into a folder so you can edit them right away.
Open the Deluge Forge view in the activity bar to see your workspaces. If something is missing, the view tells you which step comes next.
🛠️ Everyday workflow
- Open a
.dg file from your workspace.
- Edit it. Completion, diagnostics and the outline work as you type.
- Run it with
Cmd+Alt+R (macOS) or Ctrl+Alt+R, or use Deluge Forge: Save and Execute Function to save and run in one step.
- Read the output and the logs, fix what the run showed you, run again.
- Push it back to Zoho with
Cmd+Alt+U or Ctrl+Alt+U.
How each product runs a function:
- Zoho CRM: the script in your editor is what runs, so you can try a change before you push it.
- Zoho Creator: Creator runs the function that is already saved in Zoho, so push first, then execute.
- Zoho Books: pull, edit, push and execute work the same way as in CRM.
Pull brings a function down from Zoho, and Deluge Forge: Pull All brings down every function of the active workspace. For Creator, Deluge Forge: Pull All Apps (Creator) and Deluge Forge: Pull Some Apps (Creator) pull whole applications. Deluge Forge: Create Function makes a new function in Zoho and a matching file here.
🗂️ What you see in the editor
The Deluge Forge activity bar view has four parts:
- Workspaces: every organization you added, with its functions, and the state of its Zoho session. Switch the active workspace with
Deluge Forge: Switch Active Workspace.
- Workspace Dashboard: an overview of the active workspace.
- Function Inspector: details of the function you have selected.
- Data Schema & Variables: the variables and data shapes the editor knows about for the current function. Create, edit, duplicate and delete them from the view, and use them to get smarter completion on values Zoho returns.
The status bar shows the active workspace and how fresh its Zoho session is, so you notice an expired session before a push fails.
✍️ Writing Deluge
Files ending in .dg open in the Deluge language mode, with:
- syntax highlighting;
- completion for Deluge built-ins and for the variables and schemas you defined;
- diagnostics that flag mistakes as you type;
- an outline of the symbols in the file;
- connection names completed from the connections your Zoho organization actually has (
Deluge Forge: Pull Connections refreshes the list, Deluge Forge: Manage Connections opens it).
⌨️ Commands
Open the Command Palette and type "Deluge Forge".
| Command |
What it does |
Deluge Forge: Sign in |
Activates the licence on this computer with your Google account. |
Deluge Forge: Licence Status |
Shows the state of your licence. |
Deluge Forge: Setup |
Shows the pairing code for the Chrome extension and sets up the local host. |
Deluge Forge: Setup with a Custom Chrome Extension ID |
For developers running a differently keyed build of the Chrome extension. |
Deluge Forge: Add Workspace |
Adds a Zoho organization as a workspace and pulls its functions. |
Deluge Forge: Link Zoho System |
Links another Zoho product to a workspace. |
Deluge Forge: Set Active Workspace |
Chooses the workspace that commands act on. |
Deluge Forge: Switch Active Workspace |
Switches the active workspace from a list. |
Deluge Forge: Delete Workspace |
Removes a workspace from this computer. |
Deluge Forge: Pull |
Pulls the function you are looking at from Zoho. |
Deluge Forge: Pull All |
Pulls every function of the active workspace. |
Deluge Forge: Pull Connections |
Pulls the list of Zoho connections. |
Deluge Forge: Pull All Apps (Creator) |
Pulls every Creator application. |
Deluge Forge: Pull Some Apps (Creator) |
Pulls the Creator applications you choose. |
Deluge Forge: Refresh Function List |
Re-reads the list of functions from Zoho. |
Deluge Forge: Push |
Pushes your local change to Zoho. |
Deluge Forge: Execute |
Runs the function against your Zoho organization. |
Deluge Forge: Save and Execute Function |
Saves the file, then runs it. |
Deluge Forge: Manage Connections |
Lists and manages the Zoho connections a function can use. |
Deluge Forge: Create Function |
Creates a function in Zoho and a file for it here. |
Deluge Forge: Delete Function |
Deletes a function in Zoho, where Zoho allows it. |
Deluge Forge: Remove Local Copy |
Removes the local file and keeps the function in Zoho. |
Deluge Forge: Create Variable |
Adds a variable to the Data Schema & Variables view. |
Deluge Forge: Edit Variable |
Edits a variable. |
Deluge Forge: Duplicate Variable |
Copies a variable. |
Deluge Forge: Delete Variable |
Deletes a variable. |
Deluge Forge: Create Schema |
Adds a data schema. |
Deluge Forge: Edit Schema |
Edits a data schema. |
Deluge Forge: Delete Schema |
Deletes a data schema. |
Deluge Forge: Delete Dynamic Cache |
Clears the editor's dynamic schema cache. |
Deluge Forge: Refresh Variables & Schemas |
Reloads the Data Schema & Variables view. |
Deluge Forge: Start Task Timer |
Starts a timer for the task you are working on. |
Deluge Forge: Pause Task Timer |
Pauses it. |
Deluge Forge: Stop Task Timer |
Stops it. |
Deluge Forge: Task Timer Status |
Shows the running timer. |
Deluge Forge: Refresh Session from Chrome |
Re-reads the Zoho session the browser has already sent. |
Deluge Forge: Clear All Sessions |
Clears the Zoho sessions stored on this computer. |
Deluge Forge: Run System Diagnostics |
Checks every link of the chain and prints a report. See Troubleshooting. |
⌨️ Keyboard shortcuts
These apply while a .dg file is focused, except Pull All and Manage Connections, which work anywhere.
| macOS |
Windows and Linux |
Action |
Cmd+Alt+P |
Ctrl+Alt+P |
Pull the function you are looking at |
Cmd+Alt+Shift+P |
Ctrl+Alt+Shift+P |
Pull all functions of the workspace |
Cmd+Alt+U |
Ctrl+Alt+U |
Push the function to Zoho |
Cmd+Alt+R |
Ctrl+Alt+R |
Execute the function |
Cmd+Shift+E |
Ctrl+Shift+E |
Save and execute |
Cmd+Alt+C |
Ctrl+Alt+C |
Manage Zoho connections |
🔒 Privacy and security
Your Zoho session is the most sensitive thing this extension touches, so here is exactly what happens to it.
- It stays on your computer. The Chrome extension sends the session to this extension over Chrome's local Native Messaging channel. It never travels over the network to Deluge Forge.
- It is encrypted at rest. Sessions are stored with AES-256-GCM in
~/.deluge-forge/sessions.enc (on Windows, %APPDATA%\deluge-forge\sessions.enc). The key is derived from your pairing code. Without the code, the file cannot be read.
- The pairing code lives in a few places, on purpose. The editor keeps it in your operating system's keychain through VS Code's SecretStorage. The local host cannot reach the keychain, so a copy is kept in a file in your user profile, and the Chrome extension keeps a copy in its own local storage. Anyone who can read your browser profile or your home folder can read the code, so protect those the way you protect your sessions.
- Only the Deluge Forge Chrome extension can talk to the local host. The host accepts connections from the extensions you authorized, which by default is the Deluge Forge extension and nothing else.
- Licence checks send licence requests and nothing else. The part of the extension that talks to the licence service has no access to your Zoho sessions.
- Telemetry is off by default. The setting
delugeForge.telemetry.enabled is false until you turn it on. When it is on, it sends scrubbed reports about interface problems and nothing from your code or sessions.
- Diagnostics never print secrets.
Deluge Forge: Run System Diagnostics shows cookie names, never values, and never the pairing code.
🌍 Supported Zoho data centers
zoho.com, zoho.eu, zoho.in, zoho.com.au, zoho.jp, zoho.ca, zoho.com.cn and zohocloud.ca.
🩺 Troubleshooting
Start with Deluge Forge: Run System Diagnostics. It checks the Node.js it finds, the pairing, the stored sessions (and asks Zoho whether each one still works), the native host registration, whether the host answers, and which builds of the extension, the host and the Chrome extension are talking to each other. The last section tells you what to do next. When you ask for help, attach the whole report.
| What you see |
What to do |
| The Chrome popup says the native host was not found |
Run Deluge Forge: Setup, then run the diagnostics. On Windows the host is registered in the registry for your user, and the diagnostics list the keys it found. |
| Setup says it could not register the native host with the browser |
The pairing code was created, but the browser cannot find the host yet. Run the diagnostics and read the section on the native host manifest. |
| The workspace says its Zoho session is stale or missing |
Open a signed-in Zoho tab in the paired Chrome profile and give it a minute. Deluge Forge: Refresh Session from Chrome re-reads what the browser already sent. |
| A call fails with an authentication error or a 401 |
The Zoho session expired. Sign in to Zoho again in Chrome, and wait for the status bar to show a fresh session. |
| The Chrome extension refuses the pairing code |
Run Deluge Forge: Setup again to show the code, and paste it exactly. |
| Diagnostics say Node.js was not found |
Install Node.js 22 or newer, open a new terminal, and check node --version. Restart VS Code and Chrome afterwards. |
| Sign-in says the licence is active on another computer |
A licence is bound to one computer at a time. The prompt names that computer and when it was last seen. Choose Move to this computer to end the licence there and use it here; the account owner gets an email saying it moved. A licence can move 3 times in 30 days, at most once an hour, and the message tells you when you can move it again. Cancelling changes nothing. |
| The local host keeps running an old build after an update |
Close VS Code completely and open it again. The local host switches to the new build when the editor restarts. |
To start over completely, close VS Code and Chrome, remove the Deluge Forge folder in your user profile (~/.deluge-forge, or %APPDATA%\deluge-forge on Windows), remove and reinstall the Chrome extension, and run the Quick start again. Deleting the folder removes your saved sessions and the local licence file, so you will sign in and run Setup again. The licence service sees a deleted folder as a new computer, so the first sign-in afterwards offers to move your licence here.
📌 Good to know
- Zoho Flow is not supported yet.
- Chrome is the browser Deluge Forge has been exercised with. The local host is registered for Edge and Brave as well.
- Windows support is new and has been verified on one machine. If you hit a Windows problem, the diagnostics report is the fastest way to describe it.
📄 Licence
Deluge Forge needs a licence on this computer. Run Deluge Forge: Licence Status to see where yours stands, and Deluge Forge: Sign in to activate it. A licence is active on one computer at a time. If yours is active elsewhere, signing in offers to move it to this computer, after you confirm.