Customization and integration, for Zoho software

Many apps,
working as one

We fit Zoho software to how your business works, keep its Deluge scripts where your team can find them, and connect its apps to each other and to your product, so each record has one home.

Thanks, we’ll be in touch soon.

{{ heroStatus }}

You’re in good company

A few of the companies we’ve worked with.

When scripts are spread across apps

Many companies’ Zoho software has grown one app at a time, each app set up by whoever needed it, from sales to accounting to support.

Scripts written in Deluge, Zoho’s own scripting language, sit in workflow rules, buttons and schedules across several of those apps, and the same customer is often kept in more than one of them.

So a change in one app can stop a script in another, and often no one has the full list.

What we build

The work we do around Zoho software. Every script, sync and integration we add is written down with what it reads and changes, and each change is tried before it reaches your team.

  • Your CRM, fitted to how you sell

    Modules, the kinds of record your team keeps, with their fields, layouts and validation rules, and Blueprint processes whose steps come in order, so Zoho CRM software follows the way your team sells.

  • Deluge scripts you can find

    Functions with one job each, attached to workflow rules, buttons and schedules, written in Deluge or another language Zoho allows, and kept in source control with Zoho’s Functions APIs. Other services are reached through Deluge connections, never a token typed into a script.

  • Zoho Creator apps

    Apps of your own for the jobs your standard apps don’t cover, built on the Zoho Creator low-code platform, with Deluge scripts where they need logic.

  • Integrations with your product

    Your product connected through each app’s own API, in its current version, every integration signed in through Zoho’s API console with only the scopes, the access it asks for, that it needs. Changes reach your product through Zoho’s notifications rather than repeated checks.

  • Apps that share their records

    Zoho’s built-in integrations, such as the sync between Zoho Books software and Zoho CRM software, and the Zoho Flow integration platform where it fits, each set up once every record’s home is decided.

  • Large jobs within the limits

    Big syncs and imports moved to Zoho’s bulk APIs and run in batches, with the allowance checked before a job grows.

  • Changes tried first

    Customizations tried in a Zoho CRM sandbox, a copy of your setup kept apart from the one your team uses, on the editions that include it. Where an app has no sandbox, they’re tried on test records.

  • Moves from older systems

    Data from spreadsheets and older systems brought into Zoho CRM software with Zoho’s own import tools, each record matched and checked before it moves.

  • AI where it helps

    Zia, Zoho’s AI assistant, and Zia Agents where they fit the work, and AI assistants reaching your Zoho apps through Zoho MCP, each acting only within the permissions of the person it works for.

One home for each record

Zoho’s apps are separate apps, each keeping records of its own, and Zoho’s built-in integrations connect them. Zoho CRM software and Zoho Books software, for example, can keep customers, vendors and items in sync.

For customers, that sync can run both ways, or only from Zoho CRM software into Zoho Books software, so a change made in accounting stays there. When several Zoho Books organizations share one Zoho CRM organization, it runs one way only.

And quotes and invoices made in Zoho CRM software’s own modules don’t sync with those in Zoho Books software, so the same sale can be recorded twice, once in each.

So each kind of record is given one home, the one app that keeps it, the way it syncs is chosen on purpose, and every script and integration writes to that home.

Which way it syncs

How customers sync

Both ways: a change made in either app reaches the other at the next sync, so both teams can keep the customer up to date.

From Sales only: Sales is the customer’s home. A change made in Accounting stays there, so changes are made in Sales.

Either works, as long as every app and script knows where each record’s home is.

{{ suStatus }}

Every call counts

Zoho CRM software counts each API call in credits, one for most calls and more for some, over a rolling 24-hour window. An organization’s allowance, the credits it has in that window, depends on its edition and its number of user licenses, and Zoho also limits how many calls run at once.

Each run of a Deluge function uses a credit too, from an allowance of its own, and every function has limits on how long it runs and how much it returns. Zoho’s other apps set limits of their own, as each one’s docs state.

So integrations ask for many records in one call, large jobs use Zoho’s bulk APIs, changes arrive through Zoho’s notifications rather than repeated checks, and every integration names the API version it was built for.

Zoho is also retiring outdated encryption settings for connections, in phases, so older servers that still connect with them need updating, as Zoho’s notice says.

Start with every script in one list

The review covers the Zoho apps and editions you use, and which of them sync with which, in which direction; every Deluge script and function: where it runs, from workflow rules, buttons and schedules to Blueprint steps and your other apps, what it reads and changes, and whether it’s in source control; the modules, fields, layouts and processes in each app; each integration: what it reads and writes, how it signs in, its scopes and the API version it uses; the credits your API calls and functions use against the allowance; the profiles and roles of people and integrations; and which features need which edition, as Zoho sets them out.

The first step is one script or integration the business relies on, rewritten, tried in a sandbox or on test records, and moved into source control.

You get a written review and a proposal for the first step.

  1. Our scripts are spread across several apps. Where do we start?

    With the review: every Deluge script and function in one list, with where it runs, what it reads and changes, and who answers for it. From that list we choose one the business relies on, rewrite it, try it first and move it into source control, then take the next. How long the list runs varies from company to company.

  2. Should this be a Deluge script, a Zoho Creator app or code of our own?

    It depends on the job. A Deluge script suits work that belongs to one record or one app, such as a button or a workflow rule. A Zoho Creator app suits a job your standard apps don’t cover that people do every day. Code of your own, outside Zoho’s apps, suits work that runs long, moves a lot of data or serves your product, reaching Zoho’s apps through their APIs, since Zoho limits how long each function runs. Many setups use all three.

  3. Our integration keeps running out of API credits. What can we do?

    First, see what uses them: Zoho reports the credits left in its API responses once half the day’s are used, and lists usage in its API dashboard. Then fewer, larger calls: many records in each call, bulk APIs for large jobs, and notifications in place of repeated checks. If that isn’t enough, Zoho offers added credits, and we tell you what they would involve before anything is bought.

  4. Can you connect Zoho CRM software to our own product?

    Yes, through the Zoho CRM API, with your product signed in through Zoho’s API console and given only the scopes it needs. Changes reach your product through Zoho’s notifications, and what your customers do comes back as records your team can see. We agree which app is each record’s home first, then build one connection and try it with test records before starting the next.

  5. Can our Zoho apps share one set of customer records?

    Often, yes, through Zoho’s built-in integrations, with one app as each record’s home. Zoho CRM software and Zoho Books software, for example, can sync customers both ways or from Zoho CRM software only. Which suits you depends on the apps you use and how your teams work, so we decide each record’s home with you first.

  6. Do we need a different edition, or a Zoho One subscription, for this?

    Sometimes. Some features need certain editions: Zoho CRM functions, for example, have full access only on some editions, the Zoho One edition among them. We name each edition or app the work depends on, and why, before anything is bought.

  7. Can you build a Zoho Creator app for our team?

    Yes. We start with one job and the people who do it, build the app on the Zoho Creator platform with Deluge scripts where it needs logic, and try it with them before it goes live.

  8. Can AI assistants work with our Zoho data?

    Yes, through Zoho’s own routes. Zoho MCP lets AI assistants that support MCP use data and actions from Zoho’s apps, and they can do only what the signed-in person is allowed to do. Inside the apps, Zia, Zoho’s AI assistant, and Zia Agents work within the permissions your organization has set. We set them up for the jobs you agree, with each person’s access kept to what the job needs.

  9. Can you move us onto Zoho software from our current system?

    Yes, with Zoho’s own import tools. Records are matched and checked first, duplicates found and settled, and a trial import is checked with your team before the full move.

  10. Can you build the reports our teams need?

    Yes, in the reports and dashboards of Zoho CRM software, or in Zoho Analytics software where a report draws on several apps. Each report reads from the record’s home, so what it shows matches the app your team works in.

  11. Where is our data kept?

    In the Zoho data center your account was set up in. Zoho hosts its apps in several regions, each holding the data of the accounts registered there, so every integration uses the addresses for your account’s data center.

  12. Can you take over our existing Zoho setup?

    Yes. We start with the review, so we know what each script, sync and integration does and who answers for it, then take over the changes one app at a time.

  13. How do you keep our data secure?

    People get profiles and roles with only what their job needs. Each integration signs in with only the scopes it needs, scripts reach other services through connections rather than tokens typed into them, and multi-factor sign-in is enforced for everyone, as Zoho lets an organization’s admins do.

  14. What does it cost?

    It depends on the work: the apps, scripts and integrations involved, and whether each part is kept, fixed or rebuilt. Before any work starts, you get a written proposal with the scope, the price or rate, and how you pay.

  15. Can we hire Zoho developers for our own team?

    Yes. We introduce developers who know Zoho software within 48 hours of your request, working in your time zone. You meet them first, and decide who joins.

Zoho and Blueprint, Deluge, Zia, Zia Agents, Zoho Analytics, Zoho Books, Zoho Creator, Zoho CRM, Zoho Flow, Zoho MCP and Zoho One are trademarks of Zoho Corporation Private Limited and/or its affiliates. Webair is independent of Zoho Corporation Private Limited, and isn’t sponsored by, endorsed by or affiliated with it.

Let’s build it better

Tell us which Zoho apps your teams use and what your scripts and integrations do. We’ll agree on a first step in a short call.

Thanks, we’ll be in touch soon.

{{ ctaStatus }}