Kaizen #193: Creating different fields in Zoho CRM through API

Kaizen #193: Creating different fields in Zoho CRM through API

🎊 Nearing 200th Kaizen Post – We want to hear from you!
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. 

Hello all, welcome back to another exciting Kaizen post!

In Zoho CRM, you have the option to tailor modules according to your organization's unique needs using custom fields. These can be created manually in the module builder or via API.

From Zoho CRM API version 6, you can add custom fields via API using the below endpoint:
POST 
{api-domain}/crm/{version}/settings/fields?module={module_API_name}

From Zoho CRM API version 8, additional field types like multi-select lookups, multi-user lookup additions are also supported.
This article is intended to be a guide on how to create fields through the API.

Field Type (UI)
Field Data Type 
Single Line
text
Multi-Line
textarea
Email
 email
Phone
phone
Pick List
picklist
Multi Select
multiselectpicklist
Date
date
Date/Time
datetime
Number
integer
Auto-Number
autonumber
Currency
currency
Decimal
double
Percent
percent (only in POST)
Long Integer
bigint
Checkbox
Boolean
URL
website
Lookup
lookup
Formula
formula
User (Type- Single User)
 userlookup
User (Type- Multiple Users)
multiuserlookup
File Upload
fileupload
Image Upload
imageupload
Rollup Summary
rollup_summary
Multi-Select Lookup
multiselectlookup

The fields in below JSON are common for all fields. Field types such as single line text, phone, email, date, datetime, integer, and url fields consists of the below common fields alone and there are no dependent fields for them. 
{
  "fields": [
    {
      "field_label": "Your Field Label",
      "data_type": "<field_type>",
      "length": "<length>",
      "tooltip": {
        "name": "static_text",
        "value": "Tooltip message"
      },
      "profiles": [
        {
          "id": "<profile_id_1>",
          "permission_type": "read_write"
        },
        {
          "id": "<profile_id_2>",
          "permission_type": "read_only"
        }
      ],
      "external": {
        "type": "user",
        "show": false
      },
      "crypt": {
        "mode": "decryption"
      }
    }
  ]
}


Key
Mandatory
Description
field_label
Yes
Display name of the field
date_type
Yes
Field type
length
No
 Max number of characters allowed for a field
filterable
No
 Whether field can be used in filters. When set to true, the field will be available for use in Criteria Pattern Editors. Note that it is not applicable for imageupload, fileupload, textarea, and formula fields 
tooltip
 No
Field help text; name can be static_text or info_icon 
profiles
No
Access control per profile (read_write, read_only, hidden)
crypt
No
Whether to encrypt the field (encryption or decryption)
unique
No
Enforce uniqueness across records
hipaa_compliance_enabled
No
Enable HIPAA protection
private
No
Enable GDPR-level handling (Low or High)

Single line Field

The single line field is a string field that can store 255 characters, and alphanumeric and special characters. It can be used to store fields like name, company, account name, etc. To create a single line field, give data_type as text. 
A single line field can be marked as an external field. An external field is used to hold a record's unique ID available in an external system.
{
    "fields": [
        {
            "data_type": "text",
            "field_label": "External ID",
            "external": {
                "type": "org",
                "show": true
            }
        }
    ]
}

Multiline Fields

The multi line field is a string field that can be used when you need a larger string field. It accepts alphanumeric and special characters. Multiline fields are of three types: plain text small, plain text large, and rich text field.
Multi-line field type
Character limit
Can be marked Mandatory?
Can be Encrypted?
Plain text small
Up to 2000
Yes
Yes
Plain text large
Up to 32000
Yes
No
Rich text (RTF)
Up to 50000
No
No

1) Plain Text Small Field

This type of multi-line field is ideal for concise entries up to 2000 character size. To create a plain text small multi line field, give data_type as textarea and type key in text area JSON object as "small".
{
    "fields": [
        {
            "field_label": "Apartment_details",
            "data_type": "textarea",
            "length" : 2000,
            "textarea": {
                "type": "small"
            }
        }
    ]
}

2) Plain Text Large Field

This type of multi line field is ideal for more extensive entries of up to 32000 character size. To create a plain text large multi line field, give data_type as textarea and type key in text area JSON object as "large".

{
    "fields": [
        {
            "field_label": "Apartment_details",
            "data_type": "textarea",
            "length" : 32000,
            "textarea": {
                "type": "large"
            }
        }
    ]
}

3) Rich text Field

Rich text field is ideal when formatted text needs to be entered. The length of the entry can be up to 50000 characters. To create a plain text large multi line field, give data_type as textarea and type key in text area JSON object as "rich_text"
{
    "fields": [
        {
            "field_label": "Apartment_details",
            "data_type": "textarea",
            "length" : 50000,
            "textarea": {
                "type": "rich_text"
            }
        }
    ]
}

Picklist Field

Picklist is a field that lets you choose a value from a set of predefined values. The pick list value accepts all alphanumeric and special characters.
To create a picklist field, give data_type as picklist .Picklist fields have dependent JSON array - pick_list_values.  
  • pick_list_values: This JSON array comprises the options for the picklist field. Inside the array, display_value and actual_values stores the label shown for the picklist value in the CRM UI and the actual internal value of the picklist option respectively.  The colour_code field consists of the color code of the picklist option in hex format, if color code is enabled.
  • enable_colour_code - Boolean value that represents whether color code is enabled for the script
  • history_tracking_enabled -   This key when set as true audit/history tracking for the picklist field is enabled. Users with Module Customization permission can enable picklist history tracking. You can enable tracking for one picklist field per module, and this will be applicable across all layouts.
{
  "fields": [
    {
      "field_label": "Your picklist's field label",
      "data_type": "picklist",
      "enable_colour_code": true,
      "history_tracking_enabled": true,
      "pick_list_values": [
        {
          "display_value": "Option 1",
          "colour_code": "#af38fa",
          "actual_value": "Option 1"
        },
        {
          "display_value": "Option 2",
          "colour_code": "#ffd6bc",
          "actual_value": "Option 2"
        },
        {
          "display_value": "Option 3",
          "colour_code": "#cfddbc",
          "actual_value": "Option 3"
        }
      ]
    }
  ]
}

Global picklist Field

Global sets in Zoho CRM is a type of picklist that helps you easily manage picklist values that recur across modules. To create a global picklist, use the Create Global Picklist API. The global picklist can then be associated to a module in the below format using the Create Custom Field API.
{
  "fields": [
    {
      "field_label": "Source",
      "data_type": "picklist",
      "global_picklist": {
        "id": "72223455366"//Id of the global picklist
      }
    }
  ]
}

Multi-Select Picklist Field

Multi-select picklist allows you to select multiple values while creating or editing record. The pick list value accepts all alphanumeric and special characters. To create a multi select picklist, give data type as multiselectpicklist.
Note that Picklist tracking is not supported for multi-select picklists
{
    "fields": [
        {
            "field_label": "Preferred working days",
            "data_type": "multiselectpicklist", // Specify the data type as multiselectpicklist* 
            "pick_list_values": [
                {
                    "display_value": "Monday",
                    "actual_value": "1"
                },
                {
                    "display_value": "Tuesday",
                    "actual_value": "2"
                },
                {
                    "display_value": "Wednesday",
                    "actual_value": "3"
                },
                {
                    "display_value": "Thursday",
                    "actual_value": "4"
                },
                {
                    "display_value": "Friday",
                    "actual_value": "5"
                }
            ],
            "pick_list_values_sorted_lexically": true,
            "enable_colour_code": true
        }
    ]
}

Auto Number Field

Auto Number fields are used for assigning a unique incremental number automatically to each record, making identification easy. To create an auto number field, set "data_type" as "autonumber" and include an auto_number object with the following keys:

  • start_number (mandatory) – Starting value for the auto-number sequence.
  • prefix (optional) – (String) to prepend to the number.
  • suffix (optional) – (String) to append to the number.
  • _update_existing_records (optional) – (Boolean). If set to true, updates existing records with new auto-numbers based on the current format. Default value is false.
{
  "fields": [
    {
      "field_label": "Order ID",
      "data_type": "autonumber",
      "auto_number": {
        "start_number": 1000,
        "prefix": "ORD-",
        "suffix": "-2025",
        "_update_existing_records": true
      }
    }
  ]
}

Currency Field

Currency field is used to store amount values. To create a currency field, set "data_type" as "currency" and define the currency JSON object with the following keys:
  • rounding_option(mandatory) – Specifies how values should be rounded:
    • "normal" – No rounding.
    • "round_off" – Rounds to nearest based on precision.
    • "round_up" – Always rounds up based on precision.
    • "round_down" – Always rounds down based on precision.
  • precision(optional) – Number of decimal places displayed in the UI (e.g., 123.466 with precision 2 becomes 123.47).
  • decimal_place(optional) – Maximum number of decimal places stored. Values beyond this are truncated. Max allowed decimal places: 9.
{
  "fields": [
    {
      "field_label": "Deal Amount",
      "data_type": "currency",
      "currency": {
        "rounding_option": "round_up",
        "precision": 2,
        "decimal_place": 3
      }
    }
  ]
}

Decimal Field

Decimal field is used to store decimal numbers. To add a decimal (floating point) number field, use "data_type": "double".
  • length(optional) – Total number of digits allowed, including both sides of the decimal point.
  • decimal_place(optional) – Number of digits to allow after the decimal point (e.g., 2 means values like 123.45).
{
  "fields": [
    {
      "field_label": "Discount Rate",
      "data_type": "double",
      "length": 16,
      "decimal_place": 2
    }
  ]
}

Percent Field

This field type is used to capture percentage values, such as scores or growth rates. To create a percentage field, use "data_type": "percent". 
{
  "fields": [
    {
      "field_label": "Enrollment number",
      "data_type": "bigint",
      "length": 18,
      "separator": true
    }
  ]
}

Long Integer Field

Long Integer Fields are number fields that accept up to 18 digits. To create a long integer field, use "data_type": "bigint".  
{
  "fields": [
    {
      "field_label": "Enrollment number",
      "data_type": "bigint",
      "length": 18,
      "separator": true
    }
  ]
}

Separator: a Boolean key that indicates whether the number is formatted for better readability. It is applicable for data types integer, double, bigint. Refer to this article on changing locale information for information on how to change it.

Checkbox Field

Checkbox value allows you to select or unselect a value indicating true or false. To create a checkbox field, use "data_type": "boolean".
{
  "fields": [
    {
      "field_label": "Previously Employed?",
      "data_type": "boolean"
    }
  ]
}

Lookup Field

Use "data_type": "lookup" to associate records from another module. The lookup JSON object defines the target module, display label, and optional filter criteria.
  • module.api_name(mandatory) – API name of the target module (get via Modules API).
  • display_label(mandatory) – Label shown in the related list.
  • query_details(optional) – Used to define lookup filters. Inside query_details JSON Object following keys are present:
    • criteria(mandatory if query_details is used) – Filter logic.
    • group_operator – "AND"/"OR" (required for multiple conditions).
    • group – Array of filter conditions. Each condition includes:
      • field.api_name: Field in the target module
      • comparator: Operator like contains, equal
      • value: Value to match
  • revalidate_filter_during_edit(optional) – If true, validates filter conditions on record edit.
{
  "fields": [
    {
      "field_label": "Your lookup",
      "data_type": "lookup",
      "lookup": {
        "module": {
          "api_name": "Contacts"
        },
        "display_label": "Contact Lookup",
        "revalidate_filter_during_edit": true,
        "query_details": {
          "criteria": {
            "group_operator": "AND",
            "group": [
              {
                "field": {
                  "api_name": "Phone"
                },
                "comparator": "contains",
                "value": "91"
              },
              {
                "field": {
                  "api_name": "Lead_Source"
                },
                "comparator": "equal",
                "value": [
                  "Cold Call"
                ]
              }
            ]
          }
        }
      }
    }
  ]
}

Formula Field

Formula fields are used to calculate different types of values, including numeric values, text values, date values, etc. Use "data_type": "formula" to calculate dynamic values based on other fields.
For more details on all the available usages in the formula field, refer to this help doc on formula field. The formula object defines the logic and output type.
  • formula.return_type (mandatory for formula field) – Output type of the formula. Possible values: double, currency, text, date, datetime, boolean
  • formula.expression(mandatory) – The actual formula logic (e.g., "Sqrt(Len(${Email}))").
  • decimal_place(optional) – Number of decimal places (only for double or currency).
  • number_separator(optional) – If true, formats the number using separators (default is true).
{
  "fields": [
    {
      "field_label": "Total amount",
      "data_type": "formula",
      "formula": {
        "return_type": "double",
        "expression": "${Amount} + 150"
      },
      "decimal_place": 0,
      "number_separator": false
    }
  ]
}

Auto refresh formula field

These type of formula fields are used when you need an accurate time measurement whenever you view the record. The key "dynamic" set as true indicates that the field is an auto refresh formula field.
 For example, the age of a deal can be calculated by comparing the created time of the deal with the current time. A condition can be given to stop computing the value of the auto refresh field. 
  • dynamic: When set as true, indicates that the formula field is an auto refresh field.
  • stop_compute_conditionally:  When set as true, indicates that the computation of field stops when the condition given in stop_compute_expression key
  • stop_compute_expression:  Mandatory when stop_compute_conditionally is true. Consists of the condition for stopping computation of the auto refresh formula field.
{
    "fields": [
        {
            "field_label": "Deal Age",
            "data_type": "formula",
            "formula": {
                "expression": "Datecomp(${Created_Time},Now())",
                "return_type": "double",
                "dynamic": true,
                "stop_compute_conditionally": true,
                "stop_compute_expression": "${Probability}==100"//When the deal probability is 100, the calculation gets stopped.
            }
        }
    ]
}

User lookup Field

User lookup field is used to associate a specific user to a record of the module. Use "data_type": "userlookup" to add a user lookup field.
The lookup JSON object defines the key properties of the user lookup
  • query_details (JSON object): Defines filters to restrict which users are selectable.
  • criteria: Uses a group of field conditions (field, comparator, value) with a group_operator (AND, OR) to filter users.
  • revalidate_filter_during_edit (Boolean): If true, the criteria is reevaluated on record edit for the value selected on the record creation. This option is useful when associated values or fields have changed due to updates. It allows users to re-check and confirm that the correct records are still linked when editing the record.
  • sharing_properties (JSON object):  Contains details of access given to users
    •  share_preference_enabled (Boolean): If true, enables access to the records for the users.
    • share_permission (String): Defines what level of access the associated user has (e.g., "read-only", "full-access", "read-write").

{
  "fields": [
    {
      "field_label": "Assigned Sales Rep",
      "data_type": "userlookup",
      "tooltip": {
        "name": "info_icon",
        "value": "Sales user responsible for this lead"
      },
      "lookup": {
        "revalidate_filter_during_edit": true,
         //associate only users from countries India, and email containing "zylker.com".
        "query_details": {
          "criteria": {
            "group_operator": "AND",
            "group": [
              {
                "field": {
                  "api_name": "country"
                },
                "comparator": "equal",
                "value": "India"
              },
              {
                "field": {
                  "api_name": "email"
                },
                "comparator": "contains",
                "value": "@zylker.com"
              }
            ]
          }
        }
      },
      "sharing_properties": {
        "share_preference_enabled": true,
        "share_permission": "read-only"
      }
    }
  ]
}

Multiuser lookup Field

Multi-user look up is a lookup field that lets you add multiple users to a module record. It allows you to establish many-to-many relationships between modules and users in CRM.
Multi user lookup can be added by using the data_type "multiuserlookup". 
  • record_access: This Boolean key when marked as true indicates that the added user has access to the record. The users selected in the multi-user lookup field will be able to 'Edit', 'Delete', 'Change the owner' of that respective record
{
  "fields": [
    {
      "field_label": "Associated_Agents",
      "data_type": "multiuserlookup",
      "multiuserlookup": {
        "record_access": true
      }
    }
  ]
}


File Upload Field

User data type "fileupload" to add a file upload field 
{
  "fields": [
    {
      "field_label": "Resume Upload",
      "data_type": "fileupload",
      "length": 1,// Allow only 1 file, Maximum length : 5
      "tooltip": {
        "name": "info_icon",
        "value": "Upload the applicant's resume in PDF or DOC format"
      }
    }
  ]
}


Image Upload Field

User data type "imageupload" to add an image upload field
{
  "fields": [
    {
      "field_label": "Profile Photo",
      "data_type": "imageupload",
      "length": 1, // Only 1 profile photo allowed, Maximum length 10
      "tooltip": {
        "name": "info_icon",
        "value": "Upload a professional head shot for the employee record"
      }
    }
  ]
}

Rollup Summary Field

Rollup Summary is a field that aggregates or summarizes a desired related list field. Rollup Summary Fields are of two types - Custom Rollups and Predefined Rollups. You can create only custom rollups using APIs. Supported related modules for APIs are Calls, Meetings, and Tasks
  • function - Indicates the mathematical function applied to calculate the rollup summary.
  • field_label - Represents the label of the field as it appears in the UI. 
  • data_type - This must be set to "rollup_summary" for rollup summary field.
  • rollup_summary -  This object contains all the configuration details for the rollup field.
  • return_type - Specifies the type of value returned.
  • expression - Defines the calculation logic for the rollup. 
    • function_parameters  An array containing parameters needed by the function, typically including:
      • api_name: The field being summarized.
    • criteria Defines the filters to apply to the related records. Each condition includes:
      • group_operator:  If there are multiple conditions, you should also include AND or OR as the group operator for the conditions. It consists of an array of conditions.
      • group: Array element of a condition
        • field
          • api_name: The API name of the field.
        • comparator: The comparison operator (e.g., equal, greater_than, contains).
        • value: The value used in the comparison.
  • function - The function to be applied to the filtered records.  Allowed functions : COUNT, MAXIMUM, MINIMUM, AVERAGE, RECENT, UPCOMING, EARLIEST.
  • based_on_module - Specifies the module from which to summarize related records.
  • related_list - Indicates the related list within the module (e.g., "Deals", "Contacts") to summarize from.
{
    "fields": [
        {
            "field_label": "Total Invoice Amount",
            "data_type": "rollup_summary",
            "rollup_summary": {
                "return_type": "currency",
                "expression": {
                    "function_parameters": [
                        {
                            "api_name": "Grand_Total"
                        }
                    ],
                    "criteria": {
                        "group_operator": "AND",
                        "group": [
                            {
                                "comparator": "equal",
                                "field": {
                                    "api_name": "Billing_Country"
                                },
                                "value": "United States"
                            },
                            {
                                "comparator": "greater_than",
                                "field": {
                                    "api_name": "Invoice_Date"
                                },
                                "value": "2024-01-01"
                            }
                        ]
                    },
                    "function": "SUM"
                },
                "based_on_module": {
                    "api_name": "Invoices"
                },
                "related_list": {
                    "api_name": "Invoices"
                }
            }
        }
    ]
}


Multi-Select Lookup Field

 Multi-Select Lookup Field enables you to establish a many-to-many relationship between two modules in CRM.
  • multiselectlookup : The mulitselectlookup JSON object specify the linking details between the module in which the field is present and another module 
    • connected_details: This JSON object contains details about the module you want to connect the current module with.
      • module.api_name:  Specify the module API name you want to link the current module with.
      • field.field_label: When connecting a module, the system creates a new lookup field in the connected module for the current module. Use this key to specify a field label in the connected module.
  • linking_details: When creating a multi-select lookup field, the system creates a separate module connecting these two modules, which contains their common details. This module is called the linking module
    • module: Consists of the details of the linking module.
      • plural_label: Specify a plural label for the linking module.

{
    "fields": [
        {
            "field_label": "Skills",
            "data_type": "multiselectlookup",
            "multiselectlookup": {
                "connected_details": {
                    "module": {
                        "api_name": "Skills"
                    },
                    "field": {
                        "field_label": "SkillName"
                    }
                },
                "linking_details": {
                    "module": {
                        "plural_label": "EmpXSkill"
                    }
                }
            }
        }
    ]
}


    • 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

    • How to add a custom hyperlinked button in ZohoCRM Canvas Builder?

      I am building custom views in ZohoCRM Canvas builder, with one view that will be used for a client Portal. Trying to add a custom button that when clicked opens a separate window to a ZohoForm. How do I do this?

    • Filtering on related module

      I have a custom module (Module1) which is related to another custom module (Module 2) Module 1 can have many related records in Module 2. Module 2 has a date field. Module 1 has related list Module 2 I want to filter Module 1 to list all records where

    • Multi-Select Field Option Limit Inquiry

      Hello FSM Team, We would like to inquire about the limitation of the Multi-Select field in Zoho FSM. Currently, the system allows a maximum of 10 selectable options, and we encountered the message: “Option count more than allowed count of 10.” Issue:

    • Disable Zoho Contacts

      We don't want to use this app... How can we disable it?

    • Records Per Page

      Can we get max number of records per page increased from 100 to 250 and 500 please? Or alternatively allow us to use the Zoho Sheet View for all records and not just the max 100 showing on the page? thanks.

    • Zoho Forms sheet prefil

      I've been using zoho sheet prefill for a week and it was working perfectly, as soon as i deleted the particular sheet and replaced it with another one no matter what I do it cant find the record and i get this message. Could you please assist me to resolve

    • Check out in Meetings

      Why there is no check out in Meetings of Zoho CRM, very difficult to track

    • WO Completion Status Not Updating Automatically

      Hello Latha, Hope you are doing well. Over the past few days, we have been facing an issue with WO completion. When an AP is marked as complete, the work order status is not automatically updating to “Completed,” and we have to mark it manually. Could

    • CRM to Desk Contact Sync Issues?

      Hello, I noticed none of the contact changes in CRM are being transferred over to Desk. Anyone else experiencing this? I checked the sync history in desk and it confirms it - it doesn't show "X Contacts Synced" like it normally does.

    • Microsoft Teams integration in Zoho Apptics

      Good app monitoring is not just about collecting data. It is about making sure important updates reach the team in time to act on them. When an app crashes or a user shares feedback from within the app, teams should be able to see it promptly without

    • Able to change project on timelog entries

      Ability to move the timesheet entry from one project to another. When a user adds a wrong entry a manager can change/update the timesheet entry to the correct project.

    • Marketing Tip #28: Increase buyer confidence with visible social media links

      Your social media pages are often where customers go to “double-check” your brand before buying. When visitors can easily find your Instagram, Facebook, YouTube, or LinkedIn from your store, it builds trust and makes your business feel more real and active.

    • [Webinar] Solving business challenges: One tool for documents, forms, PDFs, e-signatures, and more

      Hi Zoho Writer users, Most businesses rely on multiple tools, such as a word processor, form builder, e-signature provider, and PDF editor, for their document workflows. Managing multiple subscriptions, switching between tools, and moving data across

    • Customer Message Edit/Delete Function & Backend Visibility Inquiry

      目前客服已发送的对话支持编辑和删除功能，请问在 Zoho 系统后台，是否可以查看客服具体发送了什么内容，以及删除或修改了哪些信息？如果无法查看，这个功能是否可以通过设置关闭客服的编辑和删除权限？如可以，请告知具体设置路径。 Currently, customer service agents are able to edit and delete messages after sending them. In the Zoho system backend, is it possible to view

    • Google Drive API 403 PERMISSION_DENIED from Deluge custom function - OAuth connection not recognised

      Hi all, I've built a custom Deluge function to route Zoho CRM Account attachments into specific Google Drive subfolders based on filename prefix. The CRM API steps all work correctly, however our first Google Drive API call (listing subfolders via drive/v3/files)

    • Supercharge Your Zoho Billing Workflows with AI Using Zoho MCP

      What is MCP and how does it connect to Zoho Billing? If you've ever wished you could just tell your billing software what to do without clicking through menus, running reports manually, or switching tabs every five minutes, that's exactly what the Zoho

    • Automation Series: Notify Admin When User Accepts an Invitation

      In Zoho Projects, a portal is an organisational-level workspace where user can manage multiple projects. To join a portal, a user will have to accept the portal invitation. However, it is important for admins to be in the loop when a user accepts the

    • Knowledgebase SEO

      We have a custom-domain mapped help center that is not restricted via login. I have some questions: a) will a robots.txt file still allow us to control indexing? b) do we have the ability to edit the sitemap? c) do category URLs get indexed by search

    • Mail Merge preview won't load

      Hello! One of our users has not been able to use mail merge templates in CRM as the preview screen does not load. We have many templates for one of our custom modules and the users are used to this feature and have been using it for years without any

    • mask Customer phone number and agents cant see customer phone number

      Is there any way we can integrate Zoom Phone with Zoho CRM while ensuring that customer phone numbers remain masked? We need a solution where agents can make outbound calls but cannot see customer phone numbers. Please let us know if there is any solution

    • Issue with Zoho Sheets

      Edit: Small Error of Opening doc and losing entire formatting while downloading to *.xlsx format. Also my formulas don't work while opening a document downloaded from Zoho sheets, since the colors aren't matched to the correct data. Even though the data

    • Record-Level Cliq Conversations Inside Zoho CRM

      It would be extremely useful to bring the Zoho Projects + Cliq conversation experience into Zoho CRM records. Today, in Zoho Projects, each project or task can have its own related chat conversation through Cliq, allowing team members to discuss that

    • Introducing note actions and dynamic visibility in Kiosk Studio

      Hello all, We are introducing enhancements to Kiosk Studio that will improve the product scope and meet your custom needs more precisely. What's new? Add notes as Actions: You can add notes to CRM records as kiosk Actions, as well as insert merge fields

    • Logging Calls not working

      For some reason, logging calls is not working anymore. Description of problem: On a Lead's record, in the "Open Activities" block, clicked on "Add New" Clicked on "Call", clicked on "Log a call" Nothing happens. If I click on "Schedule a call" nothings

    • How do I filter contacts by account parameters?

      Need to filter a contact view according to account parameter, eg account type. Without this filter users are overwhelmed with irrelevant contacts. Workaround is to create a custom 'Contact Type' field but this unbearable duplicity as the information already

    • Data Import into Zoho Forms

      Hi everyone, I am migrating several Google Forms into Zoho Forms. I can recreate the forms, but I also need to bring over historical response data currently stored in Google Sheets. I want to keep using that data inside Zoho for analysis, reporting, and

    • How Can I Clear Deleted Members and Free Up Their Storage?

      Can we remove these deleted members and free up their storage?

    • Pro rata holiday allowance for variable part time employees

      We have some part time staff who work variable hours and their holiday allowance is based on pro rata system. In Zoho people is there any way to calculate their holiday allowance based on actual hours worked? I.e. worker is entitled to a pro-rata amount of 5.6 weeks holiday, which is equivalent to 12.07% of hours worked over a year. So part time staff's holiday is accrued at a rate of 12.07% per hour worked. Thanks

    • Zoho Bookings - Provide Appointment System ID in Zoho Flow Variable

      Hi Bookings Team, It would be great if you could provide the system record ID for appointments as a variable in Zoho Flow trigger outputs and Fetch Appointments action. This would allow us to create a dymanic URL which can be clicked by a staff user to

    • Understanding tasks

      So we have a module linked to contacts called Equipment and that in turn has a related module called service calls. Often on a service call we want add a task but we are not able. I think it needs a link to the contact. WE therefore tried to add tasks

    • How to transfer files from Creator file upload fields to CRM file upload fields

      This article describes how to transfer files from Zoho Creator file upload fields to Zoho CRM file upload fields. I'm posting it here because the current documentation does not fully and accurately describe how to do this with certain file types (PDF,

    • Add Comprehensive Accessibility Features to Zoho Writer

      Hello Zoho Writer Team, We hope you are doing well. We would like to submit a feature request to enhance Zoho Writer with a full set of accessibility tools, similar to the accessibility options already available in the Zoho Desk agent interface. 🚧 Current

    • ¿Puedo migrar mi sitio desde WordPress a Zoho? ¿Zoho admite herramientas con código personalizado?

      ¡Hola comunidad! Estoy evaluando la posibilidad de migrar mi sitio web https://calculadoradenotas.cl/ desde WordPress a una solución Zoho, y tengo algunas dudas técnicas que espero puedan aclararme. Mi sitio no es solo informativo: es una herramienta

    • Make Task ID and Issue ID columns filterable like all other columns

      Hello Zoho Projects Team, We hope you are doing well. We would like to submit a feature request regarding the Task ID and Issue ID columns in Zoho Projects list views. Current Limitation: As of now, in both the Tasks and Issues modules, almost every visible

    • Improve Back Navigation (X Button) Inside Nested Milestones, Task Lists, Tasks, and Issues

      Hi Zoho Projects Team, We would like to request an improvement to the X / close button navigation behavior inside milestones. Currently, the milestone area behaves as a nested hierarchy (tree structure): Project → Milestone → Task List → Task So when

    • Add a way to connect Log360 Cloud logs with Zoho analytics

      Hi, Several month ago Log360 Cloud was added to zoho one - and this is great. But as far as I see there is no prebuilt way to connect Zoho analytics to the logs we have in Log360 Cloud. Please add a prebuilt connection like we have for so many other zoho

    • Extend GitHub Commit Integration to Tasks in Zoho Projects

      Hello Zoho Projects Team, We hope you are doing well. We would like to submit a feature request regarding the current GitHub integration in Zoho Projects, specifically the ability to link commit information. Current Limitation: As of now, Zoho Projects

    • Enable Screen Recording in Zoho WorkDrive Mobile Apps (Android & iOS)

      Hi Zoho WorkDrive Team, How are you? We are enthusiastic Zoho One users and rely heavily on Zoho WorkDrive for internal collaboration and content sharing. The screen-recording feature in the WorkDrive web app (similar to Loom) is extremely useful- however,

    • Zoho Project - Total Forecasted Hours

      Does anyone know an easy way to get a total of all the forecasted hours across the portfolio? I'm aware trying to create a custom report that can generate this figure for each task and the total up but the completion percentage doesn't seem to come back

    • Bank Fees - Allow User to Choose Expense Account

      Bank fees from Customer Payments can only be debited against the system Bank Fees account due to hard-coding. The user should be able to select which expense account those fees are debited against. The use case is pretty straightforward. A business like

    • Next Page