Kaizen #192 - Implementing Custom Token Persistence in Python SDK

Welcome back to another week of Kaizen!

Last week, we discussed how to implement Login with Zoho using OAuth 2.0 and saw how to bring it to life in a real-world application with the Zoho CRM Python SDK. We also discussed how Zylker Academy built a custom student portal powered by Zoho authentication.

In our sample project, we used the file-based persistence method, a simple setup where the access and refresh tokens are stored in a local file. While this method is great for getting started, it might not always fit your business requirements.

That is why our SDKs offer multiple ways to persist your tokens. 

This week, we will explore why token persistence matters for your app’s secure operation, and how to implement custom token persistence methods, including a practical example using SQLite.

Why does token persistence matter?

When a user logs in via OAuth, Zoho returns two tokens:

• An access token (valid for one hour), used to access Zoho CRM data.
• A refresh token, used to get a new access token when the current one expires.

If your app does not store these tokens properly, your users will be forced to log in again every time they make an API call. Or every time their access token gets expired. That is not inconvenient; it is a poor user experience.

When you use Zoho CRM SDKs, this is all handled for you behind the scenes. When you first authenticate with Zoho, the SDK stores your access and refresh tokens. Later, when a token expires, the SDK automatically uses the refresh token to get a new one. All you have to do is configure and initialize the SDK, and you are ready to start making API calls using the different methods offered by our SDKs! 

From the user’s perspective, it means:

• They do not have to log in every time.
• Their sessions are automatically renewed without interruption.
• Token revocation can be done centrally.

From a developer’s perspective:

• You can control how and where tokens are stored.
• You have control to enforce policies like session timeouts or token cleanup.

Supported token persistence options

The Zoho CRM SDKs support three token persistence mechanisms:

File Persistence:

As we have already seen in last week's Kaizen, in this method, the tokens are stored in a local file of your choice. This can be configured while configuring and initializing the SDK. While this is simple and great for internal and local use, it might not always meet the needs of a growing business. For instance, if the file gets deleted or corrupted, you lose the tokens. It also poses a security risk, as storing tokens in files may expose them to unauthorised access if the file is not properly secured.

Database Persistence:

This stores tokens in a MySQL database, making it better suited for production environments. It is more robust and can handle larger-scale user management. 

Using this persistence method, you can only provide the following connection parameters - host, DB name, table name, username, password, and port number. 

Custom Persistence:

But what if neither of these options fits your needs? Maybe you are working in an environment without traditional storage like AWS's Secret Manager, or you prefer any other Database, or running a microservice in a container where local storage is more practical. That is where Custom Token Persistence comes in.

Custom Token Persistence

Custom persistence means you can implement your own logic for storing and retrieving OAuth tokens, instead of relying on the SDK’s default mechanism. To do this, you should create a class that implements the TokenStore interface and override a standard set of methods, each handling a specific part of the token lifecycle.

Here’s what your custom class must implement:

Method	Purpose	Return Type
find_token(self, token)	Given a token, return a full Token (OAuthToken) object from storage. Used before making any CRM API call.	Token(OAuthToken) object
save_token(self, token)	Called right after Zoho returns a new access/refresh token. Your implementation must persist it.	None
delete_token(self, id)	Delete a specific token using its unique ID.	None
get_tokens(self)	Return all stored tokens.	A list of Token(OAuthToken) objects
delete_tokens()	Delete all stored tokens. Useful during cleanup or logout.	None
find_token_by_id(id)	Retrieve a token by its unique identifier.	Token(OAuthToken) object

The token object is an instance of OAuthToken. The SDK will invoke these methods automatically as part of its flow. You just have to focus on where and how to store the tokens. With this, you can persist tokens to any storage as long as your class handles these methods correctly.

Understanding the token object

Before we dive deeper into custom token persistence, let's clarify what this token (OAuthToken) object is and how you should work with it.

The token object is an instance of OAuthToken.  This class bundles all the credentials and details the SDK needs to authenticate your API requests. Here’s what it holds:

• access_token
• refresh_token
• client_id 
• client_secret
• redirect_url
• expires_in
• user_signature
• id
• api_domain

Implementing Custom Token Persistence with SQLite

Now that we've covered the basics of token persistence and how Zoho SDK supports custom stores, let’s dive into a practical, real-world example using SQLite as the backend for storing tokens.

SQLite is a lightweight, file-based database engine. It is perfect when you want a persistent store without the complexity of a full database server.

The CustomStoreSQLite Class

This class implements all six required methods of the TokenStore interface using SQLite as the backend. 

1. Initialization and Table Setup

When you create a CustomStoreSQLite object, it immediately checks if the token table exists in the SQLite database file zohooauth.db. If the DB or the table is missing, its __init__() method creates one with all the necessary columns to store token details like id, user_name, client_id, client_secret, refresh_token, access_token, grant_token, expiry_time, redirect_url and api_domain.

def __init__(self):         """         Initializes the SQLite database and sets up the oauthtoken table if needed.         """         self.db_name = 'zohooauth.db'         if not self.check_table_exists():             connection = sqlite3.connect(self.db_name)             cursor = connection.cursor()             cursor.execute("CREATE TABLE  oauthtoken (id varchar(10) NOT NULL,user_name varchar(255), client_id "                            "varchar(255), client_secret varchar(255), refresh_token varchar(255), access_token "                            "varchar(255), grant_token varchar(255), expiry_time varchar(20), redirect_url varchar("                            "255), api_domain varchar(255), primary key (id))")  cursor.close()

This means the first time your app runs, it sets up its own database schema automatically.

2. Saving a Token - save_token(self, token)

Purpose:

This method is called every time Zoho returns a new token, whether after a login or a token refresh. Your implementation is responsible for safely persisting this token, typically by upserting (inserting or updating) a row in your database that uniquely identifies the token’s user and client combination.

Expected behaviour: 

The method must store the token in your custom database or storage system.

• If a matching token already exists (based on user, refresh token, or client credentials), it should be updated.
• If no match exists, a new entry must be created.
• Tokens should not be duplicated. Multiple users should be managed separately.

Input Parameters: An instance of Token(OAuthToken) class containing details like access token, refresh token, user signature, client ID/secret, etc.

Return value: None. But must raise exceptions on failure.

Sample Implementation using SQLite:

Here is the logic used in the implementation of save_token() method:

• If the user name is available, use it to update the token.
• If no user name but the access token is available in the table, update by the access token.
• If there is a refresh or grant token with the same client credentials, then update accordingly.
• If none of these match, insert as a new row.

def save_token(self, token):         if not isinstance(token, OAuthToken):             return         cursor = None         connection = None         try:             connection = sqlite3.connect(self.db_name)             oauth_token = token             query = "update oauthtoken set "             if oauth_token.get_user_signature() is not None:                 name = oauth_token.get_user_signature().get_name()                 if name is not None and len(name) > 0:                     query = query + self.set_token(oauth_token) + " where user_name='" + name + "'"             elif oauth_token.get_access_token() is not None and len(oauth_token.get_access_token()) > 0 and \                     self.are_all_objects_null([oauth_token.get_client_id(), oauth_token.get_client_secret()]):                 query = query + self.set_token(                     oauth_token) + " where access_token='" + oauth_token.get_access_token() + "'"             elif ((oauth_token.get_refresh_token() is not None and len(oauth_token.get_refresh_token()) > 0) or                   (oauth_token.get_grant_token() is not None and len(                       oauth_token.get_grant_token()) > 0)) and oauth_token.get_client_id() is not None \                     and oauth_token.get_client_secret() is not None:                 if oauth_token.get_grant_token() is not None and len(oauth_token.get_grant_token()) > 0:                     query = query + self.set_token(                         oauth_token) + " where grant_token='" + oauth_token.get_grant_token() + "'"                 elif oauth_token.get_refresh_token() is not None and len(oauth_token.get_refresh_token()) > 0:                     query = query + self.set_token(                         oauth_token) + " where refresh_token='" + oauth_token.get_refresh_token() + "'"             query = query + " limit 1"             try:                 cursor = connection.cursor()                 cursor.execute(query)                 if cursor.rowcount <= 0:                     if oauth_token.get_id() is not None or oauth_token.get_user_signature() is not None:                         if oauth_token.get_refresh_token() is None and oauth_token.get_grant_token() is None \                                 and oauth_token.get_access_token() is None:                             raise SDKException(Constants.TOKEN_STORE, Constants.GET_TOKEN_DB_ERROR1)                     if oauth_token.get_id() is None:                         newId = str(self.generate_id())                         oauth_token.set_id(newId)                     query = "insert into oauthtoken (id,user_name,client_id,client_secret,refresh_token,access_token," \                             "grant_token,expiry_time,redirect_url,api_domain) values (?,?,?,?,?,?,?,?,?,?);"                     val = (token.get_id(),                            token.get_user_signature().get_name() if token.get_user_signature() is not None else None,                            token.get_client_id(), token.get_client_secret(), token.get_refresh_token(),                            token.get_access_token(), token.get_grant_token(), token.get_expires_in(),                            token.get_redirect_url(), token.get_api_domain())                     cursor.execute(query, val)             except Error as e:                 raise e             finally:                 connection.commit()                 cursor.close() if cursor is not None else None                 connection.close() if connection is not None else None         except Exception as ex:  raise SDKException(Constants.TOKEN_STORE, Constants.SAVE_TOKEN_DB_ERROR, cause=ex)

3: Fetching a Token - find_token(self, token)

Purpose:

This is the method the SDK calls whenever it needs to make an API call on behalf of a user, but has only partial token information.

Depending on the token flow - Grant Token, Refresh Token, Access Token, or ID-based - only a specific token or ID may be provided during the API call. In such cases, find_token(self, token) method locates and return the complete OAuthToken object from storage if a matching one exists. If no matching token exists in the storage, this method will return None, and the SDK will proceed to generate a new token with the provided details and save it using the save_token(self, token) method. 

Expected behavior:

• Based on the available details in the input token (user name, access token, refresh or grant token), this method should query storage and return a complete token object.
• If no match is found, it should return None.

Input Parameters: A partially filled Token(OAuthToken) object.

Return value: A fully populated Token object if found, or None.

Sample Implementation using SQLite:

The find_token(self, token) method implementation does the following:

• Dynamically builds a WHERE clause based on available attributes.
• Queries the database for a matching record.
• Fetches the matching record, if any, and populates the Token object with the full set of stored values (access token, refresh token, expiry time, etc.).
• Returns the Token object if a matching record is found, or return None.

Without this method, your app wouldn’t know which token to use during API calls. For example, consider the case when a user reopens your app after hours. You have their refresh token stored. The SDK calls find_token(self, token) to get the full token and proceeds without requiring a fresh login.

def find_token(self, token):         cursor = None         connection = None         try:             connection = sqlite3.connect(self.db_name)             if isinstance(token, OAuthToken):                 oauth_token = token                 query = "select * from oauthtoken"                 if oauth_token.get_user_signature() is not None:                     name = oauth_token.get_user_signature().get_name()                     if name is not None and len(name) > 0:                         query = query + " where user_name='" + name + "'"                 elif oauth_token.get_access_token() is not None and self.are_all_objects_null(                         [oauth_token.get_client_id(), oauth_token.get_client_secret()]):                     query = query + " where access_token='" + oauth_token.get_access_token() + "'"                 elif oauth_token.get_refresh_token() is not None or oauth_token.get_grant_token() is not None and \                         oauth_token.get_client_id() is not None and oauth_token.get_client_secret() is not None:                     if oauth_token.get_grant_token() is not None and len(oauth_token.get_grant_token()) > 0:                         query = query + " where grant_token='" + oauth_token.get_grant_token() + "'"                     elif oauth_token.get_refresh_token() is not None and len(oauth_token.get_refresh_token()) > 0:                         query = query + " where refresh_token='" + oauth_token.get_refresh_token() + "'"                 query = query + " limit 1"                 cursor = connection.cursor()                 cursor.execute(query)                 result = cursor.fetchone()                 if result is None:                     return None                 self.set_merge_data(oauth_token, result)         except Exception as ex:             raise SDKException(Constants.TOKEN_STORE, Constants.GET_TOKEN_DB_ERROR1, cause=ex)         finally:             cursor.close() if cursor is not None else None             connection.close() if connection is not None else None         return token

4: Deleting a Token - delete_token(self, id)

Purpose:

Delete a specific token record from storage based on a unique token ID. It is commonly used when a user logs out or an admin revokes access for a user.

Expected behaviour:

• Locate the token record by its unique ID.
• Delete the corresponding record from storage.

Input Parameters: The token ID to be deleted.

Return values: None

Sample Implementation using SQLite:

def delete_token(self, id):         cursor = None         try:             connection = sqlite3.connect(self.db_name)             try:                 cursor = connection.cursor()                 query = "delete from oauthtoken where id= " + id + ";"                 cursor.execute(query)                 connection.commit()             except Error as ex:                 raise ex             finally:                 cursor.close() if cursor is not None else None                 connection.close() if connection is not None else None         except Error as ex:             raise SDKException(code=Constants.TOKEN_STORE, message=Constants.DELETE_TOKEN_DB_ERROR, cause=ex)

5: Deleting All Tokens - delete_tokens(self)

Purpose: Delete all tokens from storage, typically used for global logout or cleanup scenarios.

Expected behaviour: Remove all token records from storage in a single operation.

Input Parameters: None

Return Values: None

Sample Implementation using SQLite:

def delete_tokens(self):         cursor = None         try:             connection = sqlite3.connect(self.db_name)             try:                 cursor = connection.cursor()                 query = "delete from oauthtoken;"                 cursor.execute(query)                 self.connection.commit()             except Error as ex:                 raise ex             finally:                 cursor.close() if cursor is not None else None                 connection.close() if connection is not None else None         except Error as ex:             raise SDKException(code=Constants.TOKEN_STORE, message=Constants.DELETE_TOKENS_DB_ERROR, cause=ex)

6: Fetch all tokens - get_tokens(self)

Purpose: Retrieve all currently stored tokens.

Expected behaviour:

• Query storage for all token records.
• Construct and return a list of token objects 

Input Parameters: None

Return Value: A list of Token objects representing all stored tokens.

Sample Implementation using SQLite:

def get_tokens(self):         cursor = None         try:             connection = sqlite3.connect(self.db_name)             tokens = []             try:                 cursor = connection.cursor()                 query = "select * from oauthtoken;"                 cursor.execute(query)                 results = cursor.fetchall()                 for result in results:                     oauth_token = object.__new__(OAuthToken)                     self.set_oauth_token(oauth_token)                     self.set_merge_data(oauth_token, result)                     tokens.append(oauth_token)                 return tokens             except Error as ex:                 raise ex             finally:                 cursor.close() if cursor is not None else None                 connection.close() if connection is not None else None         except Error as ex:             raise SDKException(code=Constants.TOKEN_STORE, message=Constants.GET_TOKENS_DB_ERROR, cause=ex)

7. Finding a Token by ID - find_token_by_id(self, id)

Purpose: Retrieve a specific token by its unique id.

Expected behaviour:

• Search storage for a token with the given ID.
• If found, return the complete token object; if not, return None.

Input Parameters: The unique identifier of the token (id)

Return Values: Returns a fully populated Token(OAuthToken) object if found; otherwise, returns None.

Sample Implementation using SQLite:

This method should follows a similar pattern to find_token, but use the unique id as the search key.

def find_token_by_id(self, id):         cursor = None         try:             connection = sqlite3.connect(self.db_name)             try:                 query = "select * from oauthtoken where id='" + id + "'"                 oauth_token = object.__new__(OAuthToken)                 self.set_oauth_token(oauth_token)                 cursor = connection.cursor()                 cursor.execute(query)                 results = cursor.fetchall()                 if results is None or len(results) <= 0:                     raise SDKException(Constants.TOKEN_STORE, Constants.GET_TOKEN_BY_ID_DB_ERROR)                 for result in results:                     self.set_merge_data(oauth_token, result)                     return oauth_token             except Error as ex:                 raise ex             finally:                 cursor.close() if cursor is not None else None                 connection.close() if connection is not None else None         except Error as ex:             raise SDKException(code=Constants.TOKEN_STORE, message=Constants.GET_TOKEN_BY_ID_DB_ERROR, cause=ex)

Please find the complete custom_store_sqlite.py file here.

How to use this in your project

To start using this custom token persistence class in your own Python project, follow these steps:

• Download the custom_store_sqlite.py and place this inside your project directory.
• Import the class in the script where you initialize the SDK. In our sample project, this is the record.py file.
  from store.custom_store_sqlite import CustomStoreSQLite
• In the SDK configuration, use the CustomStoreSQLite method instead of the FireStore method:
  

def init(self, client_id, code, location, redirect_url):         environment = DataCenter.get(location)         client_secret = "17565609051856218813123b9a98de52c301722b7d"         logger = Logger.get_instance(level=Logger.Levels.INFO,                                      file_path="./logs.txt")         store = CustomStoreSQLite()         token = OAuthToken(client_id=client_id,                            client_secret=client_secret,                            grant_token=code,                            redirect_url=redirect_url)         Initializer.initialize(environment=environment,                                token=token,                                logger=logger,  store=store)

That’s it! With this, all token operations (save, fetch, delete) will be routed through your custom store backed by SQLite.

The above video demonstrates this is in action. You can see what the database looks like when populated. 

More Custom Persistence Implementations

The advantage of using Zoho CRM SDKs is that it doesn't box you in. You are free to implement token persistence in a way that fits your business logic, team expertise, or project requirements. Whether you prefer SQLite, NoSQL, or something entirely different, the SDK gives you full control through the TokenStore interface.

In the SQLite example above, we walked through how to implement a custom store using a persistent file-based database. You need to implement all the methods as explained in the previous section, no matter where you decide to persist your tokens. 

To make things easier, we have included two additional reference implementations:

• An in-memory store, where tokens are stored in a dictionary
• A list-based store, which keeps token records as simple lists

Each one fully implements the required methods of the TokenStore interface.

SQLite In-Memory DB

This implementation uses SQLite's in-memory mode (using ":memory:") to store tokens in RAM. Here, we have implemented all the required methods from the TokenStore interface: find_token(), save_token(), delete_token(), get_tokens(), delete_tokens() and find_token_by_id().

Please find the custom_store_in_memory.py file here.

List-Based Persistence Using Simple Lists

The second reference implementation is a list-based token store that keeps token records in an in-memory Python list of lists. Each inner list represents a token’s attributes, such as ID, user signature, client ID, access token, refresh token, and so on.

This custom store fully implements all required methods from the TokenStore interface.

Please find the custom_store_list.py file here.

We hope this was useful and gives you enough info to build your own token persistence methods tailored to your needs. We used Python SDK here, but you can apply the same logic with any of our other SDKs. It is all the same logic, just different programming languages. Just remember to implement the required methods exactly as expected by the SDK, as explained here.

Give it a try, and please let us know how it goes or if you hit any bumps!  Comment below, or send an email to support@zohocrm.com. We will be waiting to hear from you!

Happy coding!

---

We are excited to be approaching the 200th post in our Kaizen series! As we get closer to this milestone, we would love to hear from you. Have questions, suggestions, or topics you would like us to cover in our future Kaizen posts? Your feedback helps us make the series even better.

 

Please take a moment to share your thoughts with us using this form - we'd really appreciate it!

---

  Previous Kaizen: Kaizen #191 - Implementing "Login with Zoho" using Python SDK |  Kaizen Directory                    

Download Links:

• Sample project files
  

Further Reading:

• Configuration and Initialization of Zoho CRM Python SDK (V7) for different client types   
  
• Zoho CRM Scala SDK (V6) - Configuration and Initialization
  
• Zoho CRM SDKs            
  

• Topic Participants

• Anu Abraham

  

• Ashley

• Sticky Posts

• 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

• Kaizen #152 - Client Script Support for the new Canvas Record Forms

  Hello everyone! Have you ever wanted to trigger actions on click of a canvas button, icon, or text mandatory forms in Create/Edit and Clone Pages? Have you ever wanted to control how elements behave on the new Canvas Record Forms? This can be achieved

• Recent Topics

• temporary system errorlouis

  J'essaye d'envoyer des mails avec mes 2 adresses mail qe nous avons sur le compte arthur@lepunch.fr et louis@lepunch.fr mais j'ai toujours le message temporaire system error, je reçois les mails mais impossible d'en envoyer a qui que ce soit

• How to Cancel/Delete Queued Mail Merge?

  Hi. I just tried to do a mail merge before realizing there's a limit on number of sends. I accidentally sent one of my lists twice, and all of those emails are currently queued. Is there any way to cancel or delete a queued mail merge? Would love to be

• SOLVED: Stopping Multiple Invitations when sync with Google Calendar

  I wanted to share this solution as I wasn't able to find it when searching through the Zoho community and via web search. The issue: When requestor books a meeting through Zoho Bookings, the requestor receives a confirmation email from both Bookings and

• Need to add a new admin for my domain

  Hello Zoho Support, I am the owner of the domain localeistanbul.com. The current super admin account (admin@localeistanbul.com) is not accessible. I do not want to reset or delete the existing account because I need to keep all existing emails. Please

• Possible Fraud Site.

  Hello. I received a text with the sender's name as zoho, claiming that my account was at risk and that I should sign in at https://verify.zohomails.ru/signin to verify my account. I signed in on the web address above, and a few days later someone hacked

• Zoho mail to Teaminbox

  Hello, We're searching for new mail program. Now I'm testing a bit with zoho mail and team inbox. My findings in the research: Pop mail throught zoho mail is almost instant. Any pop or imap via external provider takes a couple minutes to 15 minutes before

• Crear tarea CRM con recordatorio desde Zoho Flow

  Hola, estoy intentando crear desde Zoho Flow una tarea en CRM. Lo he logrado hacer pero sin recordatorio, ya que no se como se debe escribir el string adecuado. He probado varias alternativas, pero ninguna me funcionó hasta ahora. - FREQ=NONE;ACTION=EMAIL;TRIGGER=DATE-TIME:${FechaVto}

• Inquiry Regarding Automated Assignment of Zoho TeamInbox Messages using Zoho Flow and Deluge

  Hello, Our company is currently using Zoho TeamInbox, and we are interested in automating the assignment of responsible parties using tools such as ZOHO Flow and Deluge. Is it possible to achieve this? Allow me to provide more details. Currently, when

• Multiple clients in one project

  Hi team, What is the possibility to have more than one client to be linked for one project in the Zoho Books? Our business model is to have a project, and this project have expenses/bills, as well, we issue invoices for this same project to several customers.

• Upgrade Zoho Desk Agent-Side Answer Bot to GenAI

  Hello Zoho Desk Team, We hope you're doing well. Following the recent announcements and rollout of the GenAI-based Answer Bot in Zoho SalesIQ (Nova '25), we’d like to formally request a similar upgrade for the Answer Bot used by agents inside Zoho Desk.

• Marketers' Space: The importance of warming up your sender domain

  Hello Marketers, Welcome back to yet another post! Today, we'll talk about why warming up your sender domain matters. Imagine you've recently started a business and want to share the news with your customers. You've designed a great email campaign using

• An Exclusive Session for Zoho Desk Users: AI in Zoho Desk

  A Zoho Community Learning Initiative Hello everyone! This is an announcement for Zoho Desk users and anyone exploring Zoho Desk. With every nook and corner buzzing, "AI's here, AI's there," it's the right time for us to take a closer look at how the AI

• Search Just Got Smarter in Notebook

  Hello there! Introducing Our New & Improved Search Experience! We heard your feedback! Many of you shared that our previous search had some challenges like • Inconsistent results across different clients • Limited accuracy in finding the right content

• Zoho Desk app update - AI Integration for IM Chats

  Hello everyone! We have now introduced AI integration for IM Chats within the Zoho Desk mobile app. To access the feature, please enable the 'Generative AI' settings on the desktop site(desk.zoho.com). Please refer to the help link attached below: Zoho

• Open A.I assistant Connect with Zoho Desk instant Message Conversations

  I would like to know how do I connect my instant messenger in Zoho desk with my Open A.I Gpt Assistant. this is very easy to setup using the Salesiq Zobot but when it comes to Zoho Desk i cannot figure how to make the connection. Ideal workflow Customers

• Cannot upgrade subscription plan due to payment error message

  Hi Zoho team, This is to request support on an issue I am facing during an upgrade I am trying to make to our company's yearly Zoho subscription. I am trying to add 3 more license to my plan and during the payment phase I get the below error as in the

• Enhancing Zia's service with better contextual responses and article generation

  Hello everyone, We are enhancing Zia's Generative AI service to make your support experience smarter. Here's how: Increased accuracy with Qwen One of the key challenges in AI is delivering responses that are both contextually accurate and empathetic while

• Zoho Desk app update: AI powered features

  Hello everyone! We’ve introduced various AI-powered services on the Zoho Desk app. Let's take a look at what's new. Generate Content: Generate Content uses AI to formulate responses based on the your query and provides a ready-to-use reply which can be

• Bulk update Archived Ticket

  Dear All We would like to update the "Category" values to the new filed. We found the archived Ticket seems to be don't support the bulk action. Do we have any way to update it. Finally, we would to generate a report for our ticket system. Regards I

• Channel Configuration and Default Channels

  There are some of the default fields that cannot be removed or changed. Examples are the social media ones, such as Facebook. It would be nice to be able to remove these fields as it would be confusing if someone selected this but it's not configure

• Delay function execute

  I've got a workflow which uses a webhook to send information to Flow, which in return updates a record in Creator. Problem is, by the time this has executed, the rest of my script has run and can't find the (yet to be) updated info in the record. Is there

• Support www.camcard.com

  Hi, Is it possible CRM Zoho have integrations with https://camcard.com/? Thanks Br, Andy

• Option to Customize Career Site URL Without “/jobs/Careers”

  Dear Zoho Recruit Team, I hope you are doing well. We would like to request an enhancement to the Career Site URL structure in Zoho Recruit. In the old version of the career site, our URL was simply: 👉 https://jobs.domain.com However, after moving to

• Can't make a document editable to anyone

  Hey everyone, I am using Zoho Workdrive and trying to share a document so that it is editable by anyone with the link. I am trying to convince people to shift from Google to Zoho, but they don't have accounts yet. When I try to change the share settings

• Edit Default Print

  What I want to do is create / edit the "Default Print" template without changing the layout I'm using. Currently I can create "Email Templates" but I don't use them for emailing and getting to that selection takes multiple clicks. If an email template could be set to be the Default Print template that would be helpful. I'd also like to print these in bulk but don't see that option (there is a mail merge macro but that goes straight to emailing, not to print or PDF).

• Widget shows error

  Hi， May I ask why below characters will be auto added into the widget link and how to solve this error? As my widget shows 404 error now. ?serviceOrigin=https%3A%2F%2Fcrm.zoho.com&frameorigin=https%3A%2F%2Fcrm.zoho.com

• How to print envelope labels from Zoho CRM

  Can anybody give me any clue how to print envelope/package labels directly from Contacts view? Regards, Alexandru Moderation Update: The Canvas Print View, which also facilitates the formatting of mailing labels, is now available! Learn more here: Zoho

• Data Import: New interface, improved field mapping, and more

  Hello everyone! We’ve redesigned the data import process to ensure accurate field alignment and verify that every column in the uploaded file maps correctly with Desk fields before import. Here's how: Streamlined Import Steps Importing data is now more

• Address labels

  Hi, we've been searching for a long time for a simple way for our employees to print address labels using a Dymo Label Writer 450. We came up with two alternatives that work, bur aren't really optimal.  First one is WebMerge. Webmerge is a great application that does 100% what we need but it is way too expensive for our needs. We only need to print a couple of labels per month. The second one is the integrated print tool in Zoho CRM, (Print preview) You would think this is the obvious way to do this

• Print Labels

  How can I configure my address to print my labels like this: Name Mailing Address Mailing City, Mailing State Mailing Zip Country Instead of: Name Mailing Address Mailing City Mailing State Mailing Zip Country Thanks!!!!

• Mailing labels - Improperly formatted

  All I'm trying to do is print one, properly formatted, mailing label. I'm in the Contacts module. In the default "list view" for mailing labels I selected a single client, hit the "more actions" drop down and selected print mailing label. Unfortunately,

• Printing mailing labels

  The ability to print mailing labels would seem to be an important, basic, function of a good CRM. I find it very surprising that this has still not been addressed adequately by Zoho. When trying to use the existing "mailing label" included: 1. the data

• Pageless mode needed to modernise Writer

  When we switched from GSuite to Zoho, one of the easiest apps I found to give up, was Docs. In many ways, Writer has always been more powerful than Docs, especially in terms of workflows/fillable forms/etc. However, I went back into Docs because I notice

• Zoho Projects - Visual improvement to parent and sub-task relationship

  Hi Projects Team, My feature request is to improve sub-task visibility. Please see screenshot below. I really think parent child relationships could be visually improved. Even if the first letter of the parent task was inline with other same level tasks

• API method to get activity feed in Recruit

  Hi community, I'm trying to figure out - is there any API method tto get information about datetime when Recruit/Candidates record tag where added?

• Printing Mailing labels

  Is there any way to adjust the size of the printing labels? or product would I use to print labels from Zoho? Thanks, Josef Krieger Moderation Update (14th April 2025): We have another post discussing the same topic with votes and feedback from users.

• Default to Current Date

  I'm importing data from a excel spread sheet that does not have date column and I'd like the date column in the Zoho Database to default to the current date. Any way I can do this?

• Different Company Name for billing & shipping address

  We are using Zoho Books & Inventory for our Logistics and started to realize soon, that Zoho is not offering a dedicated field for a shipping address company name .. when we are creating carrier shipping labels, the Billing Address company name gets always

• Make Packages from multiple sales order of a single customer

  Our customers sends orders to us very frequently, some times what customer wants is to ship items from 5 to 6 sales orders in a single shipment. it will be very nice if, zoho can implement this function, in which we can select items from other sales orders of the customer.

• Show Custom Button in Portal Listview Canvas

  I have created a custom button that shows in a list view of deals (internally I can see it). I have permissions to allow this button on the portal. But it is not displaying in the canvas list? Before I do too much leg work, is this function allowed?

• Next Page