Kaizen 185 - Subqueries in COQL API

Kaizen 185 - Subqueries in COQL API


Hello everyone!!

Welcome to another Kaizen week, where we discuss developer centric topics every Friday. This week, we have picked an interesting topic to discuss - Subqueries in COQL API.

Zoho CRM's CRM Object Query Language (COQL) is a powerful way to retrieve data from your CRM in a structured manner. With the release of COQL API version 7, we introduced a suite of enhancements, detailed in our previous Kaizen post. Today, we will cover one enhancement in detail—Subqueries.

Before the introduction of subqueries, filtering data dynamically across related modules required multiple API calls and additional code handling. Subqueries have fundamentally changed this, offering increased flexibility, reduced API consumption, and improved query performance. In today's Kaizen, we will explore what subqueries are, where and when to use them, their advantages, and a few practical use cases. We will also go through a few examples with different operators to help you understand COQL subqueries better.

What are Subqueries?

At its core, a subquery is a query nested within another query. This technique allows you to retrieve data from one module based on conditions derived from another related module. Think of it as a way to ask more sophisticated, multi-layered questions of your CRM data.
Imagine you're working on a CRM integration and need to find all Contacts associated with Accounts that have at least one Deal created in the last 30 days.

Before Subqueries:

Before subqueries, achieving this required multiple steps:
  1. Retrieve Account IDs from the Deals module where a Deal was created in the last 30 days - {"select_query": "SELECT Account_Name, Created_Time FROM Deals WHERE Created_Time >= '2025-01-01T00:00:00+05:30'"}
  2. Use these Account IDs in a second query to fetch associated Contacts - {"select_query": "SELECT Full_Name, Email FROM Contacts WHERE Account_Name in ('4876876000007481116', '4876876000007420031')"}
This requires writing extra code to store and use the Account IDs from the first query in the second query. This also means making multiple API calls, and handling responses separately. However, with Subqueries in COQL, this can now be achieved in a single query.

Using Subqueries:

With subqueries, you can achieve the same result in one single query!
{
  "select_query": "SELECT Full_Name, Email FROM Contacts WHERE Account_Name in (SELECT Account_Name FROM Deals WHERE Created_Time >= '2025-01-01T00:00:00+05:30')"
}
The Subquery (SELECT Account_Name FROM Deals WHERE Created_Time >= ...) retrieves Account IDs where a Deal was created in the last 30 days. The main query (SELECT Full_Name, Email FROM Contacts WHERE Account_Name IN (...)) fetches Contacts linked to those Accounts, all in one API call!
But there is a catch. Subqueries return only up to 100 records per query. If more than 100 matching records exist (e.g., over 100 Accounts with recent Deals in this case), the extra records are silently ignored. This can lead to incomplete results, so subqueries are best used when the filtered dataset is known to be small. Please head over to the Limitations section to learn about other limitations. 

Where to use Subqueries?

Subqueries in COQL are useful when there is a need to filter data dynamically based on conditions from other modules. Instead of fetching records separately and processing them, subqueries allow you to retrieve the required data in a single query.
Here are some common use cases where subqueries come in handy:

  • Segment accounts based on high-value Deal history: For instance, you can use subqueries to fetch accounts that have at least one high-value closed Deal. 
    { "select_query": "SELECT Account_Name FROM Accounts WHERE id in (SELECT Account_Name FROM Deals WHERE Amount > 100000 AND Stage = 'Closed Won')"}

  • Find Contacts whose Accounts have NEVER closed a deal: You can use subqueries in COQL to fetch Contacts that have no associated Deals. 
    {"select_query": "SELECT Full_Name, Email FROM Contacts WHERE Account_Name not in (SELECT Account_Name FROM Deals WHERE Stage != 'Closed Won')"}

  • Identify new Leads who haven’t been marketed to yet: For instance, if need to find all leads who were NOT part of a specific campaign, you can use Subqueries in COQL.
    {"select_query": "SELECT Full_Name, Email FROM Leads WHERE id not in (SELECT Leads FROM Campaigns WHERE Campaign_Name = 'T01')"}
    where Leads is a lookup up field in the Campaigns module.

  • Identify Deals Closed Outside a Specific Campaign: Similarly, to find all Deals that closed outside the “Q1 Marketing Blitz” campaign window, you can use the NOT BETWEEN operator with subqueries.
    { "select_query": "SELECT Deal_Name, Created_Time FROM Deals WHERE Closing_Date not between (SELECT Start_Date FROM Campaigns WHERE Campaign_Name = 'Q1 Marketing Blitz') and (SELECT End_Date FROM Campaigns WHERE Campaign_Name = 'Q1 Marketing Blitz')"}

Key Benefits of Using Subqueries

  • Reduces API calls and Credit consumption – Instead of fetching related data in multiple queries, subqueries fetch it in one go.
  • Less Data Processing – No need to store and process results from one query before making another.
  • Improved Query Efficiency – Filters and retrieves only relevant records dynamically.
  • Simplifies Integration Code – Removes extra loops and logic required to handle multiple queries.

Limitations of Subqueries in COQL

While subqueries improve performance and efficiency, they come with certain limitations:

  • Subqueries can only be used in the WHERE clause. You cannot use subqueries in SELECT or FROM.
  • There can be a maximum of 5 subqueries per query.
  • Only one column can be selected in a subquery. You cannot fetch multiple fields from the subquery.
  • Limited to 100 records per subquery. If more records are needed, or there could be more than 100 possible records in the subquery, consider using JOINs.

Credit Consumption Considerations

Please note that using subqueries does not introduce any change in credit consumption compared to regular COQL queries. Credit usage is determined by the number of records retrieved in the main query.
The following table outlines the credit consumption based on the number of records retrieved:

LIMIT (No: of records)
API credits consumed
1 - 200
1
201 - 1000
2
1001 - 2000
3

Subqueries vs. JOINs

A JOIN clause in COQL lets you retrieve fields from two (or more) related modules in a single query by linking them on a lookup field—no nested queries needed. It’s ideal when you need columns from both modules, ie., the parent module and the related modules, in the same response.

For example, consider a scenario where it's necessary to query all accounts that have associated Deal records created within the past month.
—without getting duplicate Account rows if an Account closed multiple Deals.

Subquery Approach:

{  "select_query": "SELECT Account_Name FROM Accounts WHERE id in (SELECT Account_Name FROM Deals WHERE Created_Time >= '2025-03-01T00:00:00+05:30')"}

The subquery first selects Account_Name from Deals where the Created_Time is within the past month. Then the main query fetches the Account_Name from Accounts, once per matching account.

JOINs Approach:

{ "select_query": "SELECT 'Account_Name.Account_Name', 'Account_Name.id' FROM Deals WHERE Created_Time >= '2025-03-01T00:00:00+05:30'"}

This JOIN COQL query queries the Deals module and pulls related fields from the Account_Name lookup (Account name and ID) for each Deal created in the last month. As a result, it returns duplicate rows for accounts that have multiple matching deals.

Sample Response:

Subquery
JOIN
 {
    "data": [
        {
            "Account_Name": "Chapmans",
            "id": "4876876000004946070"
        },
        {
            "Account_Name": "Customer Daily",
            "id": "4876876000005030168"
        },
        {
            "Account_Name": "Luma Infotech",
            "id": "4876876000007420031"
        },
        {
            "Account_Name": "Luma Biotech",
            "id": "4876876000007481116"
        }
    ],
    "info": {
        "count": 4,
        "more_records": false
    }
}




{
    "data": [
        {
            "Account_Name.id": "4876876000007481116",
            "Account_Name.Account_Name": "Luma Biotech",
            "id": "4876876000010128001"
        },
        {
            "Account_Name.id": "4876876000007481116",
            "Account_Name.Account_Name": "Luma Biotech",
            "id": "4876876000010128016"
        },
        {
            "Account_Name.id": "4876876000007420031",
            "Account_Name.Account_Name": "Luma Infotech",
            "id": "4876876000010128047"
        },
        {
            "Account_Name.id": "4876876000005030168",
            "Account_Name.Account_Name": "Customer Daily",
            "id": "4876876000010193006"
        },
        {
            "Account_Name.id": "4876876000004946070",
            "Account_Name.Account_Name": "Chapmans",
            "id": "4876876000010213010"
        }
    ],
    "info": {
        "count": 5,
        "more_records": false
    }
}

Why Subqueries Are Better in This Case:

  • No Duplicates: Subqueries ensure that each matching parent (Account) appears only once, even if multiple child records (Deals) match. This is perfect for deduplicated reporting or dropdown lists.
  • Cleaner Result: Easier to parse and use directly in UIs or aggregations where duplicates are not useful.
  • Lower Payload Size: Especially useful if you just want the Account info and don’t need Deal-level detail.
Both subqueries and JOINs allow you to retrieve related data, but when should you use one over the other?

Use Subqueries When:

  • You need to filter data based on related module conditions.
  • You do not need to fetch fields from multiple modules. ie., you want to query the inner lookup fields only in the WHERE clause, and not in any other clause.
  • You need deduplicated parent records.
  • The subquery has 100 or less records.

Use JOINs When:

  • You need to retrieve fields from multiple related modules in the same response. ie., you want to query the inner lookup fields in any clause other than the WHERE clause.
  • You are dealing with large datasets exceeding the subquery limit of 100 records.
  • You need detail per child record, even if it leads to duplicate parent values.

Operator support for Subqueries in COQL

When using subqueries in COQL, make sure to use the correct operators depending on whether the subquery returns multiple values or a single value.

Multi-Value Operators

These operators are to be used with the subqueries that return multiple values, which are then used in the main query. 
Operator
Description
Example use case and query
in
Checks if a value is present in a list of values returned by the subquery.
Fetch all Contacts whose Accounts have won high-value deals.

{"select_query": "SELECT Full_Name, Email FROM Contacts WHERE Account_Name in (SELECT Account_Name FROM Deals WHERE Stage = 'Closed Won' AND Amount > 100000)"}
not in
Excludes records where the value is present in the subquery result.
Fetch all Contacts whose Accounts have never closed a deal.

{ "select_query": "SELECT Full_Name, Email FROM Contacts WHERE Account_Name not in (SELECT Account_Name FROM Deals WHERE Stage = 'Closed Won')"}

Single-Value Operators

These operators require the subquery to return a single value. If the subquery returns multiple values, an error will occur. 
Operator
Description
Example use case 
=
Matches records where the field is equal to the subquery’s result.
Fetch Deals created on the same date as the latest deal.
!=
Retrieves records where the field is not equal to the subquery’s result.
Fetch Deals not created on the same date as the latest deal.
<, >, <=, >=
Compares a field with the single value returned by the subquery.
Fetch all Deals that closed before the latest high-value deal.
between
Ensures a field's value falls within a range.
Fetch all Deals closed between two specific deal closure dates.
not between
Excludes records within the range.
Fetch all Deals closed outside a specific date range.

Example 1: Using the IN operator to fetch Contacts linked to high-value Deals

{ "select_query": "SELECT Full_Name, Email FROM Contacts WHERE Account_Name in (SELECT Account_Name FROM Deals WHERE Amount > 100000 AND Stage = 'Closed Won')" }

Example 2: Using the NOT IN operator to fetch Contacts from Accounts that have never closed a Deal
{ "select_query": "SELECT Full_Name, Email FROM Contacts WHERE Account_Name not in (SELECT Account_Name FROM Deals WHERE Stage = 'Closed Won')"}

Example 3: Using the BETWEEN operator to identify Deals closed during a specific Campaign (Q1 Marketing Blitz)
{ "select_query": "SELECT Deal_Name, Created_Time FROM Deals WHERE Closing_Date between (SELECT Start_Date FROM Campaigns WHERE Campaign_Name = 'Q1 Marketing Blitz') and (SELECT End_Date FROM Campaigns WHERE Campaign_Name = 'Q1 Marketing Blitz')"}

Combine JOINs and Subqueries for Smarter Filtering

In many business scenarios, it is not enough to simply retrieve related fields via JOINs—you also need to dynamically filter data based on conditions from another module. This is where subqueries can be incredibly useful in conjunction with JOINs.

Let’s say you're analyzing deal performance and want to pull a list of Deals that are:
  • Associated with Active Campaigns
  • Linked to Accounts in high-revenue Industries (Annual Revenue > 10,000,000)
  • You need to fetch details from the related modules—like Account name, Campaign name, and Contact email—in the same query
Why this can't be solved easily: While COQL supports JOINs for pulling data from related modules and subqueries for dynamic filtering, you can’t do all of this in one approach alone.
  • JOINs allow you to retrieve fields from related modules (like Contact_Name.Email )—but they do not let you dynamically filter using fields from those modules.
  • Subqueries, on the other hand, allow you to filter based on fields from related modules (like filtering Deals based on the Annual Revenue of the associated Account)—but you can’t fetch fields from multiple related modules using just a subquery.
So, if you need to both filter based on fields in a related module (like Accounts.Annual_Revenue) and retrieve fields from related modules (like Contact_Name.Email, Campaign_Source.Campaign_Name), you need both tools.

Solution: Combine JOINs and Subqueries in the Same Query
{"select_query": "SELECT Deal_Name, Amount, Account_Name, Campaign_Source, Contact_Name.Email FROM Deals WHERE (Campaign_Source.Status = 'Active') AND Account_Name.Industry in (SELECT Industry FROM Accounts WHERE Annual_Revenue > 10000000 GROUP BY Industry)"}

This query:
  • Uses JOINs to fetch:
    • Contact_Name.Email – from Contacts
  • Uses a subquery to apply dynamic filtering on Deals based on the Industry of Accounts with Annual Revenue > 10000000. COQL subqueries return a maximum of 100 records. If multiple accounts satisfying the criteria share the same industry, using GROUP BY Industry ensures only unique industry values are returned. This helps stay within the 100-record limit and avoids redundant filtering.
In the results, you get a deduplicated, filter-accurate list of Deals tied to Active Campaigns and high-value industries—with rich contextual fields in one API call.

You can even use JOINs inside subqueries. For instance, to fetch all deals from Optical Networking accounts managed by Jane (jane.doe@zohotest.com), and include key details about the deal, contact, account, and campaign:
{ "select_query": "SELECT Deal_Name, Amount, Account_Name, Contact_Name.Email, Campaign_Source FROM Deals WHERE Account_Name in (SELECT id FROM Accounts WHERE Industry = 'Optical Networking' AND Owner.email = 'jane.doe@zohotest.com')"}

By combining JOINs and subqueries, you can handle more complex, real-world business requirements in a single query. JOINs help you enrich your data with fields from related modules, while subqueries let you apply smart, condition-based filters across modules. 

Advanced Filtering: Nested Subqueries

For more advanced use cases, you can nest subqueries within subqueries to create complex filtering conditions.
Let's say Imagine you need to identify all Contacts associated with Accounts that meet two specific criteria:
  • The Account is in the "Retail" industry.
  • The Account has at least one associated Deal that is in the "Closed Won" stage and has a value greater than $50,000.
This scenario is common in sales and marketing, where you want to target high-potential customers within a specific industry. Here's how you can achieve this using a nested subquery in COQL:
{
  "select_query": "SELECT Full_Name, Email FROM Contacts WHERE Account_Name in (SELECT id FROM Accounts WHERE Industry = 'Communications' AND id in (SELECT Account_Name FROM Deals WHERE Stage = 'Closed Won' AND Amount > 50000))"
}
Innermost Subquery: (SELECT Account_Name FROM Deals WHERE Stage = 'Closed Won' AND Amount > 50000)
This subquery identifies all Account_Name values from the Deals module where the Stage is "Closed Won" and the Amount is greater than $50,000. Although the field name is Account_Name, it's a lookup to the Accounts module, so it returns the Account ID. This effectively isolates Accounts that have closed high-value deals.

Middle Subquery: (SELECT id FROM Accounts WHERE Industry = 'Retail' AND id IN (...))
This filters Accounts by the "Retail" industry and ensures that only those whose ID appears in the innermost subquery are selected.

Main Query: SELECT Full_Name, Email FROM Contacts WHERE Account_Name IN (...)
Finally, the main query retrieves the Full_Name and Email of all Contacts whose Account_Name matches the id values returned by the middle subquery.

Info
Note: COQL supports a maximum subquery nesting depth of 5, and you can include up to 5 subqueries total within a single query. The nesting limit refers to subqueries embedded within the WHERE clause of another subquery. 
Subqueries in COQL are a game-changer for developers looking to build efficient, context-aware queries across modules—allowing dynamic filtering that was previously only possible with multiple API calls. While JOINs help you fetch rich, multi-module data in a single response, subqueries let you filter records based on conditions from related modules. And when you combine the two, you unlock a powerful mechanism to tackle real-world CRM business cases with precision and clarity.

For advanced use cases, don’t hesitate to nest subqueries—COQL allows up to five levels deep—giving you the flexibility to build truly nuanced filters. Mastering the balance between JOINs and subqueries is key to writing smarter, cleaner, and more performant queries.

We hope you found this guide useful in understanding and implementing COQL subqueries. If you have any questions or require further clarification, please don't hesitate to leave a comment below or reach out to us directly at support@zohocrm.com. 

Keep experimenting, and as always, happy querying!






      • Sticky Posts

      • Kaizen #198: Using Client Script for Custom Validation in Blueprint

        Nearing 200th Kaizen Post – 1 More to the Big Two-Oh-Oh! Do you have any questions, suggestions, or topics you would like us to cover in future posts? Your insights and suggestions help us shape future content and make this series better for everyone.

      • Kaizen #226: Using ZRC in Client Script

        Hello everyone! Welcome to another week of Kaizen. In today's post, lets see what is ZRC (Zoho Request Client) and how we can use ZRC methods in Client Script to get inputs from a Salesperson and update the Lead status with a single button click. In this

      • Kaizen #222 - Client Script Support for Notes Related List

        Hello everyone! Welcome to another week of Kaizen. The final Kaizen post of the year 2025 is here! With the new Client Script support for the Notes Related List, you can validate, enrich, and manage notes across modules. In this post, we’ll explore how

      • Kaizen #217 - Actions APIs : Tasks

        Welcome to another week of Kaizen! In last week's post we discussed Email Notifications APIs which act as the link between your Workflow automations and you. We have discussed how Zylker Cloud Services uses Email Notifications API in their custom dashboard.

      • Kaizen #216 - Actions APIs : Email Notifications

        Welcome to another week of Kaizen! For the last three weeks, we have been discussing Zylker's workflows. We successfully updated a dormant workflow, built a new one from the ground up and more. But our work is not finished—these automated processes are

        • Recent Topics

        • FSM integration with Books

          Hi, I have spent a few months working with FSM and have come across a critical gap in the functionality, which I find almost shocking....either that, or I am an idiot. The lack of bi-directional sync between Books and FSM on Sales Orders/ Work Orders

        • How to close an estimate ?

          Hello, I have created estimates, and converted them to invoices to get 50% payment. Now I have 2 cases where the estimate stills shows status partially invoiced, however: 1. for one of them, project stopped half way, so the remaining part will never be

        • Power up your Kiosk Studio with Real-Time Data Capture, Client Scripts & More!

          Hello Everyone, We’re thrilled to announce a powerful set of enhancements to Kiosk Studio in Zoho CRM. These new updates give you more flexibility, faster record handling, and real-time data capture, making your Kiosk flows smarter and more efficient

        • How do you print out the invoices comments

          I have some invoices where i need to print out the comments that show when reminders and etc were sent how do we print those out in Zoho Books.

        • Unable to load a specific image

          Hi I am trying to upload an svg file, which reports that there is "a problem with the file", but does not say what sort of problem. I can't find anything which says which files are supported, so it may be it does not support svg. (which would be a real shame) The file itself will open in either Firefox or Chrome without problem. For the moment I am using a png file, which does not zoom well of course. David

        • Why does the Address field show the wrong map location even with a correct Pincode?

          I am noticing an issue with the Address field map in Zoho Creator. When I enter a city name that exists in multiple locations within the same state, the map sometimes points to the wrong area even if I have entered the correct Pincode. Currently, it seems

        • Books <-> CRM synchronisation with custom Fields

          Hello, We are synchronising Books Customers with CRM Accounts. In CRM Accounts I set up last year a "segments" multiselect field shown below In Books, I set up a custom multi-select field with the same value as in the CRM And set up the synchronisation inside Books. Want to synchronise the Books Segments with the CRM Segments, but the later doesn't exist, and another non-existing is there ?! First, I don't understand where the field Segmentation is coming from. Second, I set CRM Segmentation to sync

        • CRM x WorkDrive: We're rolling out the WorkDrive-powered file storage experience for existing users

          Release plan: Gradual rollout to customers without file storage add-ons, in this order: 1. Standalone CRM 2. CRM Plus and Zoho One DCs: All | Editions: All Available now for: - Standalone CRM accounts in Free and Standard editions without file storage

        • Archive Option in Conversation View

          Hello, I have a suggestion\request to add an "Archive Thread" button in conversation view of Zoho Mail. The best suggestion I have is to put an "Archive Thread" button next to the "Label Entire Thread" button in conversation view. Most users don't just

        • Outlook/Hotmail Blocking Zoho SMTP IPs (S3150)

          We are currently facing a serious deliverability issue with Zoho SMTP while sending transactional OTP emails for our production application. Emails sent to Outlook / Hotmail addresses are being rejected with the following error: 550 - 5.7.1 Unfortunately,

        • Outlook is blocking incoming mail

          Outlook is blocking all emails sent from the Zoho server. ERROR CODE :550 - 5.7.1 Unfortunately, messages from [136.143.169.51] weren't sent. Please contact your Internet service provider since part of their network is on our block list (S3150). It looks

        • Track Marketing Automation Campaigns in Zoho CRM

          Hello, I've been searching but haven't found the exact answer to this question. I am looking to track Marketing Automation email campaigns and activities inside of Zoho CRM. Use Case: Action: Prospect Submits A Lead Form Outcomes: Prospect created in

        • Zoho Social API for generating draft posts from a third-party app ?

          Hello everyone, I hope you are all well. I have a question regarding Zoho Social. I am developing an application that generates social media posts, and I would like to be able to incorporate a feature that allows saving these posts as drafts in Zoho Social.

        • Temporarily rate limited due to IP reputation.

          We have suddenly started receiving the following Mail Delivery Status Notification: Diagnostic-Code: 4.7.650 The mail server [136.143.184.12] has been temporarily rate limited due to IP reputation. For e-mail delivery information, see https://aka.ms/postmaster

        • Incorrect Functioning of Time Logs API (Version 3)

          We need to fetch the list of time logs for each task for our company internal usage. We are trying to achieve it by using the next endpoint: https://projects.zoho.com/api-docs#bulk-time-logs#get-all-project-time-logs Firstly, in the documentation the

        • IMPORTANT: It doesn´t search for letters with portuguese characters.

          Some of my articles have for example the word "vídeo". But if I search for "vídeo" it doesn´t find them. If I search for "video" it does find them. Idealy, it should find the articles either way. But if I have to choose, it would be better to find the

        • IMPORTANT: It doens´t show full article name on search - Should add line break

          When we search for articles, it doesn´t show the full name. There should be a line break so the user can see the full article name, otherwise the user can´t know if that´s the article he/she is looking for. This is very important, otherwise the user has

        • Zoho Books - Payment Gateway - Revolut

          Hi Books Team, My feature request if to include the popular platform Revolut as a payment collection option on invoices in Zoho Books. Please upvote if you are also looking for this option.

        • Zoho Books | Product updates | January 2026

          Hello users, We’ve rolled out new features and enhancements in Zoho Books. From e-filing Form 1099 directly with the IRS to corporation tax support, explore the updates designed to enhance your bookkeeping experience. E-File Form 1099 Directly With the

        • Kaizen #233 - Generating AI-powered Follow-up Emails Using CRM Functions and Widgets

          Hey everyone! Welcome back to another interesting post in the Kaizen series! Sales teams regularly capture interaction notes in CRM after speaking with prospects. However, drafting a follow-up email that reflects the conversation context can be repetitive

        • Connect Bank in Zoho Books

          Can I connect UOB or Ariwallex in Zoho Books?

        • Using MPN across multiple SKUs and inventory tracking

          I have several different SKU's that share a common MPN and would like to track inventory by MPN. SKU1 has MPN1 assigned SKU2 has MPN1 assigned Here is an example If I start with 5 of MPN 1 in stock I want each SKU1 and SKU2 to show as 5 in stock, If I

        • Extend Zoho Canvas Customization to Zoho Creator Forms and Reports

          Currently, Zoho Canvas allows users to design and customize the UI of Zoho CRM modules with a much better visual experience. This helps organizations create cleaner layouts, improve usability, and design interfaces that match their workflows. However,

        • Marketing Tip #1: Optimize item titles for SEO

          Your item title is the first thing both Google and shoppers notice. Instead of a generic “Leather Bag,” go for something detailed like “Handcrafted Leather Laptop Bag – Durable & Stylish.” This helps your items rank better in search results and instantly

        • Feature Enhancement Request – Text Formatting Options in Item Description (Zoho Books/Quotes Module)

          Dear Zoho Development Team, Greetings from Radiant360 Integrated Technical Services LLC. We would like to bring to your attention a functional limitation we've encountered within the Item Table / Quote Description section of Zoho Books (and Zoho CRM Quotes).

        • ZOHO Books Query

          Good day, Can someone please advise. I recently migrated from ZOHO Invoice to ZOHO Books. No that I want to use the inventory on Books I cant as all my items have transaction history. The person I spoke to at ZOHO said I need to create a new Company profile

        • Best way to schedule bill payments to vendors

          I've integrated Forte so that I can convert POs to bills and make payments to my vendors all through Books. Is there a way to schedule the bill payments as some of my vendors are net 30, net 60 and even net 90 days. If I can't get this to work, I'll have

        • ZOHO.CRM.UI.Record.open not working properly

          I have a Zoho CRM Widget and in it I have a block where it will open the blocks Meeting like below block.addEventListener("click", () => { ZOHO.CRM.UI.Record.open({ Entity: "Events", RecordID: meeting.id }).catch(err => { console.error("Open record failed:",

        • inventory removal at packing list or shipment.

          currently our system is set to remove inventory at invoice. This is creating an inventory nightmare? Is it possible to change the settings to remove the item from inventory at either the packing slip stage or shipping the item.

        • How to add employee and not invite them to log in?

          I want to add 50 employees, but invite them only when everything will be configured and ready. Is it possible? Should we create employee profiles and then convert them later? Thank you,

        • How is Your eCommerce Experience w/Zoho Inventory?

          First off, I'm SUPER grateful for the advent of Zoho Inventory and now the Zoho Commerce Suite. Overall, Inventory is a great product, especially for customers without an eCommerce presence. For eCommerce companies (especially those shipping more than ~10 packages/day), however, there are certain drawbacks that keep my clients from moving over to Zoho Inventory: Cons: 1. Invoice + Package Creation from Shopify/Other eCommerce Integrations: Zoho Inventory makes the somewhat perplexing decision to

        • Ability to Use Both AND and OR When Creating Rules (Advanced Conditions)

          I'd like to be able to use more complicated logic when setting up rules. E.g. in Zoho Mail, I can choose "Advanced conditions (AND/OR) to create a rule that can be applied to multiple subject lines from the same sender. But in Zoho TeamInbox, I will have

        • Zoho Desktop App- Unable to Minimize/Freezes

          I'm having issues with my Zoho Mail desktop app (PC). When go on my desktop and open the app this is what happens: - Unable to minimize and close app (in the screenshot attached you can see at the top right there is no option to minimize/close) - Unable

        • Zoho Invoice Zapier Integration

          Is there still a way to use Zapier with Zoho Invoice? I've read online that that migrated to Zoho Books or Billing but since I am just using Invoice I can not find a Zapier Connection anymore.

        • Conect chat of salesiq with zoho cliq

          Is there any way to answer from zoho cliq the chat of salesiq initiated by customers?

        • Bug: OAuth 2.0 State Parameter fails with Pipe Delimiters (RFC 6749 Non-Compliance)

          I've discovered a bug in how Zoho's API Console handles the OAuth 2.0 authorization flow when the state parameter contains pipe characters (|), and I'm hoping the Zoho team can address this in a future update. The Issue Zoho's OAuth 2.0 implementation

        • Zobot with Plugs

          Hello, I am having a problem with Zobot using Plugs. Here is my current flow: When I run the flow, I should immediately see the messages from the initial cards (Send Message cards), then after running the plug, and finally, see the messages after the

        • Print a document from Zoho Writer via Zoho Creator

          If i use the code below i can get writer to create a new document or email it to me but i want to be able to print it directly from the browser and not have to send it via email and then print. Below is the code im using. Attached options form zoho writer

        • Training for How can i Operate the Software Features

          need to Help for Training of the ZOHO Billing Software

        • Automating Vendor Contract Management between Zoho Contracts and Zoho Books using Zoho Flow

          Managing vendor agreements across procurement and finance systems often requires manually downloading executed contracts and attaching them to vendor records. This can become time-consuming and difficult to manage when dealing with a large number of contracts.

        • Next Page