Zoho Deluge Scripting Examples: Four Short Scripts That Survive Production.

Most Deluge examples you find online are toys. They work on a blank sandbox and fall apart the first time they meet a real organisation. Deluge is the scripting language built into Zoho, and it is how you make Zoho do what configuration alone cannot. This video shows four short patterns that do most of the real work, and the three habits that decide whether a script merely demonstrates or survives a night on its own. Everything on screen is a mock demo with sample data, and the field names are illustrative: yours will differ.

First, where the script runs, because the same logic is wired up differently in each place. A custom function is called from a workflow, a blueprint or a button. A workflow rule runs when a record is created or changed. A validation rule runs before the record is saved, and it can block the save. A button runs when a person clicks it. And a scheduled function runs on a timer, with nobody there. Get the place right and the rest is ordinary programming. A validation must give an answer back.

A scheduled function simply acts. Mixing those up is the first way a script goes wrong. Pattern one: roll a child total up to its parent. Keep an account's total deal value correct as its deals change. The script finds the account that the deal belongs to, adds up the amounts of every deal on that account, and writes the total back to the account. The checks matter more than the sum. If the deal has no account, stop. If a deal has a blank amount, skip it. Without those two lines, a single deal with an empty amount will throw an error and stop the whole function, and from then on the total quietly goes out of date.

Pattern two: call another system. When a large deal is won, send a message to a team chat channel. The script builds a short message from the deal name and amount and sends it to the other system's web address. The same pattern works for any system that accepts a request. For anything that needs a login, never paste the secret into the script. Store it once as a Zoho connection and name the connection in the call. That way the secret is not in the code, not in a copy of the code, and not visible to everyone who can read the function.

Pattern three: a check before the record is saved. For instance, a deal that is closed won must have a closing date. The script looks at both fields, and if the date is missing it gives back an error with a message the person will see. Otherwise it gives back success. That returned answer is the whole point. Leave it out, and the validation silently passes when you meant it to block. It is the kind of detail that trips up people who know configuration but have not written scripts, and it is easy to test: try to save a record that should be refused.

Pattern four: a scheduled job. There is no user and no trigger record, only logic on a timer. A nightly job finds open leads, works out how long each has been untouched, and flags any that have been idle for more than fourteen days, so the owner sees them in the morning. For a large number of records, process them in pages and not all at once, and write a log line at each step so that a stopped job tells you where it stopped. The shape is simple, which is why it is worth getting the habits right: a job that runs unattended at night is the one you most need to be able to trust.

Four mistakes cover most of what goes wrong. No check for an empty value, which is the number one cause of a function that simply stops working. A credential written into the script. Bulk work with no batching and no log. And a validation with no return. Test every script in a sandbox first, and test the empty case on purpose. When the logic grows beyond what you want to maintain yourself, that is the point where custom development pays for itself, because the script that demos in five minutes and the one you trust to run unattended at two in the morning are rarely the same script.

To sum up. Know where the script runs. Check for empty values. Keep credentials in a connection, and give a validation its answer. Do that, and four short patterns will carry a surprising amount of your Zoho. We are CodeStringers, a Zoho authorised consulting partner, and we write Deluge for clients every week. The full article with the scripts is linked below.