Re: Application Architecture in Zoho Creator — A Platform-Specific Deep Dive

Re: Application Architecture in Zoho Creator — A Platform-Specific Deep Dive

A recent community post on application architecture made some excellent points about planning architecture early in Zoho Creator projects. The core message is right — Creator applications have a habit of growing organically into maintenance nightmares, and thinking about structure upfront pays dividends.

However, much of the advice in that post reads as general software engineering principles that don't account for Creator's specific capabilities and constraints. I wanted to put together a more grounded reference — covering what Creator actually offers, where the guardrails are and what good architecture looks like in practice on this platform.
1. Modular Architecture — The Cross-App Trade-Offs
Splitting into separate apps by domain is more viable in Creator than many developers realise — cross-app lookups, function calls and lookup-based reporting all work natively. But there are still trade-offs worth understanding before committing to a multi-app approach:
Capability Single App Multi-App
Lookups between forms ✓ Native lookups ✓ Cross-app lookups supported
Reporting across domains ✓ Single report pulls from any form ⚠ Reports can include cross-app lookup fields, but each report is based on a single form — complex cross-app analysis may still require Zoho Analytics
Workflow triggers ✓ Direct form references in Deluge ✓ Functions can be invoked across applications natively — no API calls required
Deployment ✓ Single publish ⚠ Must coordinate deployments across apps. Environment limitations include: 10-app cap, 800-component publish limit, 30-min publish timeout, 30-version stacking limit in Stage, no data transfer between environments, and pre-production environments receive only 20% of your plan's usage limits (excluding Deluge execution statements, which get 100% per environment)
User management ✓ Shared permissions ⚠ Permissions managed per app
Practical reality: Cross-app lookups, reporting via lookup fields and cross-app function calls are all natively supported — which means the multi-app story in Creator is stronger than many developers assume. The remaining trade-offs are narrower but worth weighing: reports are still based on a single form (so complex cross-app analysis may need Zoho Analytics), permissions must be managed per app, and environments come with significant constraints — a 10-app cap, 800-component publish limit, 30-minute publish timeout, 30-version stacking limit in Stage, no data transfer between environments, and pre-production environments only receive 20% of your plan's usage limits for non-Deluge components (records, emails, schedules etc.) — though Deluge execution statements now get the full plan limit per environment independently. Portals, backup, audit trail and several other features aren't supported in development/stage at all. Every additional app multiplies this overhead. In most Creator projects, a well-structured single app with clear form naming conventions and organised sections will still be simpler to maintain — but the cross-app capabilities are more robust than many assume, so know the actual costs before deciding.
2. Workflow Orchestration — What Creator Actually Offers
Creator is sometimes described as supporting "event-driven architecture" — it doesn't have an event bus, message queue or pub/sub system, so that label overpromises. But it does have a broader workflow toolkit than many developers realise. Here's what's actually available:
Workflow Type Triggers Capabilities Key Constraints
Form Workflows Created, Created or Edited, Edited, Deleted (with success/failure blocks). Also supports form load, field rules and user input triggers via integration form workflows. Execute Deluge scripts, call functions (including cross-app), send notifications, manipulate records, push data to Zoho CRM/Recruit/Salesforce/QuickBooks. Multiple workflows can fire on the same form event and execute in order of creation. Execution time limits apply. On Success scripts not triggered for records inserted via Deluge. Integration form workflows have significant restrictions (no On Delete, no system field access, no Data Access tasks, limited Deluge support).
Scheduled Workflows Fixed date/time (daily, weekly, monthly, yearly, once) or based on a date field value in a form (before, on, or after the date) Execute Deluge scripts on a schedule without user input. Send automated emails, fetch external data, update records periodically. Form-based schedules can trigger relative to a record's date value (e.g. 3 days before a deadline). Custom schedules limited per plan. Monthly schedules skip months where the day doesn't exist (e.g. 31st). Cannot be triggered on-demand from other workflows.
Batch Workflows After successful import or on a custom schedule Process high-volume data in chunks (10–1,000 records per batch). Per-batch rollback on failure — a failed batch doesn't affect others. Before/during/after execution stages with variable support. 1-minute timeout per batch. Only one batch workflow executes concurrently per account. 15 consecutive failures terminates the workflow. Several standard Deluge operations restricted — aggregate functions (except distinct), getUrl/postUrl, client functions are not supported within batch workflows. Cannot be triggered on-demand from a button or workflow.
Approval Workflows On record submission (criteria-based) Route records through sequential multi-level approval chains. Criteria can auto-approve or escalate (e.g. expenses under $100 auto-approved, over $5,000 requires manager). Actions configurable on both approval and rejection. Does not apply to records submitted through published forms. Approval logic is configured per form. Cannot be tested in development/stage environments.
Payment Workflows On form submission (criteria-based, redirects to payment gateway) Collect online payments via configured payment gateways (powered by Zoho Checkout). Configure success/failure actions (e.g. confirmation emails, CRM updates, transaction logging). Supports registration fees, donations, subscriptions etc. Requires one-time payment gateway setup via Zoho Checkout. Currency type must match between form field and gateway. Not available in CN and UAE data centres. Old PayPal/PayflowPro/Payments Pro deprecated (Sept 2024).
Blueprints Triggered when a record is added or edited (associated after On Success workflow completes). State transitions driven by user actions in live mode. Define multi-stage process flows with configurable transitions between stages. Each transition supports before/during/after configuration: transition owners (by user, permission or user field), criteria, field updates via pop-up, opening another form to add records, notifications, data operations, integrations (CRM, Salesforce, QuickBooks) and Deluge scripts. Supports common transitions (accessible from any stage, e.g. "Reject"), parallel transitions (multiple steps required before advancing) and Deluge tasks (changeStage, executeTransition). Blueprint fields available for report filtering and workflow criteria. Multiple blueprints per form execute sequentially. Up to 100 stages and 100 transitions per blueprint. Max 5 common and 5 parallel transitions. A record can only go through a blueprint once — no re-entry. Blueprint fields cannot be modified by Deluge or UI actions. Completed records cannot re-enter even if new stages are added. Works with portal records.
Report Workflows User clicks a custom action item (button or menu) on a report or record Define custom actions beyond the standard edit/delete/duplicate/view. Appear as buttons in report headers or menus alongside system actions. Execute configured logic against selected records — e.g. "Notify All" to email multiple parties from a travel request report. Requires workflow configuration per action item. User-initiated only — cannot be triggered programmatically.
Functions Called from any workflow type, buttons, custom actions on reports, or other apps Reusable Deluge/Java scripts that can be invoked across applications. Related functions can be grouped under namespaces for organisation. Enable cross-app data manipulation, modular code and integration with report custom actions. 75-call recursion limit. Function size limits apply. Cannot be triggered independently — always invoked from another context.
What's still missing: There's no way to publish a custom event and have multiple independent subscribers, no automatic retry on failure, and no message queue. You also can't chain workflow types together natively (e.g. trigger a batch workflow from a form workflow). These gaps mean you'll need to design your own orchestration patterns — status-driven workflows, scheduled polling, or function-based coordination — rather than relying on platform-level event infrastructure.
The architectural takeaway: Creator's workflow toolkit is broader than "just form triggers" — between form workflows, schedules, batch processing, approvals, payments, blueprints, report action items and cross-app functions, there are real orchestration capabilities here. But it's not event-driven in any meaningful sense. Understanding what each workflow type can and can't do — and where they don't connect — is what lets you design reliable automation. Blueprints come closest to structured process orchestration for well-defined multi-stage flows. For everything else, "decoupled" in Creator means well-organised workflows calling reusable functions, not a pub/sub pattern.
3. The Platform Constraints That Actually Force Architectural Decisions
These are the walls you will hit, and they should inform your architecture from day one:
Constraint Impact Architectural Implication
50,000 record fetch limit You cannot fetch more than 50,000 records in a single Deluge query. Aggregations on large datasets hit this ceiling. Batch workflows can process records in chunks but have their own fetch limit of 5,000 records per batch operation. Design summary/aggregate tables early. Don't plan to calculate totals from raw data at scale. For high-volume processing, batch workflows help manage throughput within the limits.
Workflow execution time limits Specific timeouts per the platform performance documentation: regular workflows time out at 5 minutes, batch workflows at 1 minute per batch, external API calls at 40 seconds, and record locks at 30 seconds. If a transaction exceeds the time limit, the entire transaction is rolled back. Deluge execution is limited to 5,000–50,000 statements per function depending on your pricing plan. Blueprint changeStage and executeTransition are limited to 50 statements each. Batch workflows help by splitting large datasets into manageable chunks (10–1,000 records per batch) with per-batch rollback on failure — but only one batch workflow can execute concurrently per account, 15 consecutive failures terminates the workflow, and several standard Deluge operations are restricted within batch workflows — aggregate functions except distinct, getUrl/postUrl and client functions are not supported. Use batch workflows for high-volume repetitive processing (they can overcome the per-function statement limit). For complex multi-step processes that don't fit the batch model, break into chained stages with a status field to track progress and allow resumption. Minimise external API calls within workflows to avoid holding locks for extended periods.
Workflow action call rate limits A maximum of 120 workflow action calls per minute per IP address — this includes form on-load scripts, on-user-input scripts, formula expressions, filtered lookups and button clicks. The per-app limit is 250 requests per minute collectively across all users. Portal limit is also 250 per minute collectively. Design high-traffic forms with these rate limits in mind. Minimise on-load and on-user-input scripts where possible. For apps accessed by many concurrent users, these limits can be hit faster than expected.
Locking, deadlocks and rollback behaviour Creator employs record-level locking (30-second timeout) and form-level locking during schema changes. Deadlocks can occur when two workflows update the same records in different order — one workflow will fail. On timeout or script error, data operations within the workflow (record adds, updates, deletes) are rolled back. However, external side effects that already fired — API calls, emails, SMS — cannot be rolled back as they've already been sent. This means a workflow that sends an email in step 2 and fails in step 3 will revert the data changes but the email is already delivered. Batch workflows offer per-batch rollback (a failed batch's data operations are reverted without affecting others). Use consistent record update ordering across workflows to avoid deadlocks. Place external actions (API calls, emails) as late as possible in your workflow scripts — after all data operations that might fail. This minimises the risk of sending notifications for data changes that get rolled back. Keep workflows short to minimise lock duration. Refer to the platform performance best practices for optimising execution time.
Subform record limits Subforms are not designed for hundreds of rows. Performance degrades significantly and there are hard limits on row counts. Use related child forms via lookup instead of subforms for anything that could grow beyond ~50 rows.
Lookup/dropdown 5,000-choice scroll limit In live mode, dropdown, multi-select and lookup field pick lists only display up to 5,000 choices. Beyond that, users must use the search bar. Formula fields also don't reflect changes made in lookup/subform subfields across forms. For large reference datasets (e.g. product catalogues, customer lists), plan for the 5,000 display limit from the start. Consider filtered lookups or alternative UX patterns for very large datasets.
Form field count limits The number of fields per form depends on character limits. At default 255-character single line fields, you're capped at ~60 fields of that type. Reducing character limits increases field count (e.g. 100-char limit allows ~160 choice fields). Max 4 display fields per lookup. Design forms with field counts in mind. For complex entities, split across related forms via lookups rather than cramming everything into one form.
Report operation limits Only 1,000 records can be bulk-selected for edit/duplicate/delete in live mode. When importing with "Execute scripts" enabled, workflows only run for the first 3,000 records. Export limits: 50,000 records max for HTML, PDF and print, 150MB/70MB for XLSX (existing/new users), 12MB and 5-min rendering timeout for PDF. Reports won't load when a subform/multi-select lookup has more than 2,500 values mapped to a record. Design for these ceilings when planning data migration, bulk operations and report-based exports. For large imports that need workflow execution, process in batches under 3,000 records or use batch workflows.
Grid/spreadsheet report workflow conflicts Grid and spreadsheet reports silently fall back to list reports if the underlying form has Deluge scripts in On Edit > On Load or On User Input workflow blocks, or if a lookup field has "Set Filter" configured. This is undocumented in the form workflow setup — you only discover it when the report type changes unexpectedly. Be aware of this interaction when adding On Load or On User Input scripts to forms that power grid or spreadsheet reports. Test report rendering after adding these workflow types.
Page capabilities and constraints Pages have two scripting mechanisms with very different capabilities. Page Scripts (the dedicated feature) are limited: no custom function calls, no write operations, no email/postUrl/openUrl, one script per page, max 50 variables, and scripts can't be shared across pages. However, HTML/ZML Snippets embedded in Pages can execute full Deluge — including data fetching, record manipulation, API calls and function triggers. Other Page-level limits: HTML snippets capped at ~500KB, charts plot only the first 200 data points, and pages containing pivot charts, pivot tables or iframes cannot be exported as PDF. Use HTML/ZML snippets for dynamic, data-driven page elements rather than relying on the limited Page Script feature. Be mindful of the performance best practices — Pages are common interaction points for multiple users, so write operations from snippets can cause concurrency issues. For heavy computation, move logic to workflows and display results in Pages.
API rate limits Integration tasks and external API calls (e.g. invokeUrl to Zoho or third-party APIs) are rate-limited per minute and per day. Heavy integration workflows can exhaust limits quickly. Batch API calls where possible. Distinguish between native cross-app functions (no API quota impact) and external API calls (rate-limited) when designing integrations.
Connection limits In Creator 5, each user is limited to 100 active Zoho OAuth connections — exceeding this silently deactivates the oldest connection. OAuth authorisation is valid for only 90 seconds. Connections invoked within nested functions (functions called inside other functions) are not displayed in the Connections slider or tracked as references. Custom OAuth connectors cannot be imported/exported across data centres. Track active connection counts in integration-heavy apps. Be aware of the nested function blind spot — connections used there won't appear in the management UI. For cross-DC deployments, avoid reliance on custom OAuth connectors.
Deluge 5MB file handling limit Deluge cannot handle files larger than 5MB. This directly impacts document management architecture — you can programmatically upload/download via Deluge to WorkDrive only if files stay under 5MB. Larger files require manual handling or external tooling. Factor file sizes into your document architecture early. WorkDrive integration works well for metadata-driven workflows, but automated file processing at scale needs a realistic assessment of what Deluge can actually move.
Custom Function size limits Individual Deluge functions are limited to approximately 5,000–50,000 statements depending on your pricing plan. You cannot build monolithic utility libraries. Recursive functions are capped at 75 calls. Keep functions focused. Accept some duplication rather than trying to build an abstraction layer Creator won't support. Batch workflows can be used to overcome the per-function statement limit for data processing tasks.
Cloud function limits Cloud functions (Node.js and Java) have a 40-second maximum execution time. A single Deluge transaction can invoke a cloud function no more than 5 times. Cloud functions are not available in CN, JP, CA, SA and UAE data centres. Don't rely on cloud functions for heavy orchestration — 5 invocations per transaction is a hard ceiling. Use them for specific compute-heavy tasks that Deluge can't handle efficiently. Check data centre availability before architecting around them.
150-field report export limit Duplicating an application or exporting its DS file is not supported when a report displays data from 150 fields or more. This directly affects backup and migration strategies for complex apps. Monitor field counts in reports. If approaching 150, split into multiple reports before the limit blocks your ability to export or duplicate the app.
Data centre feature availability Feature availability varies by data centre. Payment workflows are not available in CN and UAE. Cloud functions are not available in CN, JP, CA, SA and UAE. AI modeler is unavailable in CN, JP, SA and UAE. Zia assistance is restricted in CN, JP, SA and UAE. Only the IN data centre has no feature restrictions. This is a hard constraint you cannot work around. Check your account's data centre before architecting around features like payment workflows, cloud functions or AI capabilities. If you're building for a global client base, verify feature availability per DC early.
Backup limitations Scheduled backups do not include files (images, file uploads, audio, video, signatures) — only immediate backups do. Backup is only available for production environment apps, not development/stage. Compressed size limits apply (meta: 50MB/100MB, data: 1GB, files: 3GB). Restored apps lose shared user access and published components. Backup is not supported for installed apps. Forms with 30+ multi-select/checkbox fields may cause backup failures. Don't rely on scheduled backups for file-heavy apps — you'll only get the data, not the files. Build a separate file backup strategy if files are business-critical. Factor environment restrictions into your disaster recovery planning.
Audit trail blind spots Records updated via Deluge scripts are not captured by the audit trail. Audit data is only retained for 6 months. Several field types are excluded from auditing (subform, rich text, URL, formula, signature, text area, file upload, image, audio, video). Pivot report exports/prints are not logged. If compliance or data lineage matters, do not assume the audit trail covers script-driven changes — it doesn't. Build your own logging for automated workflows if you need a complete audit history. Plan for the 6-month retention limit.
No interactive debugging No breakpoints, no step-through execution, no stack traces. Debugging relies on info statements, runtime error messages with line numbers, and try-catch blocks. Application Logs exist but are only accessible through the Logs interface — they cannot be queried via Deluge or surfaced in reports. Write smaller functions. Log aggressively with info statements. Use try-catch to handle and log expected failure modes. For workflow failure tracking beyond what Application Logs provide, build your own logging form — write error details to it from try-catch blocks so you can report on failures independently.
Key takeaway: Good architecture in Creator isn't about applying textbook patterns — it's about knowing where the platform will break and designing around those specific limits from the start. Every constraint above should inform decisions before a single form is created.
4. What "Good Architecture" Actually Looks Like in Creator
Rather than adapting enterprise patterns to fit Creator, here's what works in practice:
Naming conventions are your architecture. Creator doesn't have folders or modules for forms and reports — your form names, function names and field names are your organisational structure (functions do support namespaces for grouping, which helps). Adopt a consistent prefix convention early (e.g. CRM_Clients, CRM_Deals, OPS_Tasks, OPS_Timesheets) and enforce it ruthlessly. This gives you the logical separation of "modules" without the cost of multi-app architecture.
Summary tables over real-time aggregation. Don't calculate dashboard totals by querying thousands of records on load. Where you do need to aggregate at runtime, use Deluge's built-in aggregate functions (sum, count, average, min, max, median, distinct) directly in fetch tasks rather than looping through records — this is significantly more efficient. For larger datasets, create dedicated summary forms that get updated via workflows when source data changes, or use batch workflows to recalculate summaries on a schedule. This sidesteps the fetch limit and keeps reports fast.
Status-driven workflows over complex chains. Instead of workflow A calling function B which triggers workflow C, use a status field that progresses through stages. Each workflow responds to a specific status change. This gives you visibility into where a process is, makes failures recoverable and keeps individual workflows simple. For well-defined, repeatable processes, Blueprints are the native implementation of this pattern — they enforce stage progression with configurable transitions, transition owners, criteria and automated actions. Use blueprints where the process is predictable; fall back to manual status-field patterns where you need more flexibility (e.g. records that may re-enter a stage, or processes that don't follow a linear path).
Lookups over text duplication — but know the trade-off. Using lookup fields instead of storing text copies is good practice, but lookup fields in Creator have their own quirks. They display as record IDs in API responses, they add load time to forms with many lookups, the pick list only shows 5,000 choices (users must search beyond that), formula fields don't reflect changes made in lookup subfields across forms, and lookups can complicate imports/exports. Use them, but don't over-normalise to the point where every form has 15 lookups loading on open.
Final Thought
The best Creator architects aren't the ones who import the most patterns from other platforms — they're the ones who know exactly where the guardrails are and build accordingly. Architecture in Creator needs to be grounded in what the platform actually does and doesn't support.

Hope this serves as a useful reference. Happy to discuss any of these points further.
📚 Documentation References:


      Zoho Campaigns Resources


        • Desk Community Learning Series


        • Digest


        • Functions


        • Meetups


        • Kbase


        • Resources


        • Glossary


        • Desk Marketplace


        • MVP Corner


        • Word of the Day


        • Ask the Experts


          Zoho CRM Plus Resources

            Zoho Books Resources


              Zoho Subscriptions Resources

                Zoho Projects Resources


                  Zoho Sprints Resources


                    Zoho Orchestly Resources


                      Zoho Creator Resources


                        Zoho WorkDrive Resources



                          Zoho CRM Resources

                          • CRM Community Learning Series

                            CRM Community Learning Series


                          • Tips

                            Tips

                          • Functions

                            Functions

                          • Meetups

                            Meetups

                          • Kbase

                            Kbase

                          • Resources

                            Resources

                          • Digest

                            Digest

                          • CRM Marketplace

                            CRM Marketplace

                          • MVP Corner

                            MVP Corner




                            Zoho Writer Writer

                            Get Started. Write Away!

                            Writer is a powerful online word processor, designed for collaborative work.

                              Zoho CRM コンテンツ






                                ご検討中の方

                                  • Recent Topics

                                  • How has Zoho still not resolved Daylight Savings Time?

                                    According to these forums Zoho has been working on DST for 12 years. Totally unacceptable. Am I missing something? Why are other customers who observe DST not screaming for this to be fixed? Are there reasonable workarounds? This is a must-have for us. 

                                  • ZOHO Desk attachments support

                                    Hi I just setup MCP with claude, it works well, but it can't read attachments... which makes it kind of useless... Will you be adding attachment capabilities anytime soon?

                                  • Very limited support for MCP

                                    Has anyone else noticed how limited the MCP support for Zoho People currently is? Right now only a small set of read-only actions (exactly 15) seem to be available. At the same time Zoho CRM supports over 700+ functions. It makes it almost impossible

                                  • How to Generate Separate Labels for Each Invoice SKU Line Item in Zoho Books?

                                    Hi everyone, I’m trying to implement a requirement in Zoho Books where separate labels need to be generated for each SKU/item from an invoice. Scenario: One invoice can contain multiple products/SKU items Each item/box should have its own separate label

                                  • HTML PDF Templates / Build From Scratch option not visible for Custom Modules

                                    Hi everyone, I am working with Zoho Books Custom Modules and trying to create a custom 4x4 package label PDF template using HTML/CSS. According to the official Zoho Books documentation for HTML PDF Templates, there should be an option like: Settings →

                                  • Updating Sales orders on hold

                                    Surely updating irrelevant fields such as shipping date should be allowed when sales orders are awaiting back orders? Maybe the PO is going to be late arriving so we have to change the shipment date of the Sales order ! Not even allowed through the api - {"code":36014,"message":"Sales orders that have been shipped or on hold cannot be updated."}

                                  • Direct Integration Between Zoho Cliq Meetings and Google Calendar

                                    Dear Zoho Team, We’d like to submit the following feature request based on our current use case and the challenges we’re facing: 🎯 Feature Request: Enable meetings scheduled in Zoho Cliq to be automatically added to the host's Google Calendar, not just

                                  • billable_expense_id in Invoice API does not set invoiced=true on bill line items — causes duplicates in Projects > Create Invoice

                                    Hi Zoho Community, We are running an automated batch invoicing system using the Zoho Books API and have hit two critical bugs that are causing duplicate invoice risk in production. Raising this here for visibility alongside a support ticket already filed.

                                  • New fields : radio button

                                    Hi, when customizing a module (eg: Candidates), we are able to select different types of fields (check box, currency, list, ...). However there is no "radio-button" component. This type of fields is often used in Web pages and will be certainly a plus-value

                                  • Huge confusion in zoho crm and zoho analytics

                                    Context => We have reporting based hierarchy in zoho crm and basically there will be one sales head and couple sales managers and 10 pre sales excutives divided between 2 sales managers we have maintained that in zoho crm and there is complex reporting

                                  • Huge confusion in zoho crm and zoho analytics

                                    Context => We have reporting based hierarchy in zoho crm and basically there will be one sales head and couple sales managers and 10 pre sales excutives divided between 2 sales managers we have maintained that in zoho crm and there is complex reporting

                                  • Import KB template OR Export template for zoho desk?

                                    Greetings. Can you tell me if there is a way to get an EXPORT of my KB articles? OR is there a template you supply for importing KB articles into my zoho desk? I am looking for a method of understanding what fields can be imported, and what their possible

                                  • Choice Availability Reset

                                    If an entry is deleted which included a response to a field with choice availability enabled does that increase the number of remaining times the choice can be selected?

                                  • Rich Text Type Format for Notes Field

                                    Has it been discussed or is there a way to insert a table in the notes field? We sometimes receive information in a table format, and it would be beneficial to have it in the same format as a note on a record.

                                  • [Bug] WebAuthn passkey registration blocked on rpIds with TLDs longer than 6 characters (.accountant, .technology, etc.) — isValidDomain regex too strict

                                    Hi, Filing on behalf of an enterprise customer where Zoho Vault is deployed across the company. The Chrome extension blocks WebAuthn passkey registration on legitimate sites whose Relying Party ID (rpId) has a TLD longer than 6 letters. This affects every

                                  • [Heads Up] Upcoming update to field values in Zoho Books - Zoho Analytics integration

                                    Hello Users, We'd like to inform you of an upcoming update to the Account Type field values in the Zoho Books integration for Zoho Analytics from June 1, 2026. What's Changing? The following values under the Account Type field are being renamed to align

                                  • Important update: Migrate to the new SalesIQ live chat widget before May 15, 2026

                                    The old SalesIQ live chat widget will be deprecated on May 15, 2026. This is a final reminder to migrate to the new SalesIQ live chat widget before this date. After May 15, 2026, the old widget will no longer be maintained, which can lead to slower performance

                                  • Zia Agent built in ChatKit UI does not render markdown

                                    Hi, You have a major shortcoming in the Zia Agent UI. The test UI that is embedded in agents.zoho.com allows you to test the agent has full support for rendering markdown, but your ChatKit UI does not have support for rendering markdown. If I embed it

                                  • Team folder not created when creating project using zoho flow

                                    When I try to automate project creation using zoho flow, and I have enabled workdrive integration to automatically create team folders to attach to the project, this only works when I create a new project through the UI. But I am trying to automate project

                                  • Zoho Projects - Email notification relabelling of modules not present on default templates

                                    Hi Projects Team, I noticed that in the default email template notification, the word "bug" was not renamed to the lable I am using in my system. As many users may used the Bugs modules for various purposes including Changes, Revisions, Issues, etc...

                                  • GLM 5 not available

                                    Hello, I am trying to setup a Zia Agent using agents.zoho.com. The settings says that GLM5 is among the list of free zoho hosted models available. However, when I try to setup an agent and pick a model from the list only GLM 4.7 Flash is available. How

                                  • Set Custom Icon for Custom Modules in new Zoho CRM UI

                                  • Can not send or reply to mails

                                    Hello, I can not send mails or reply. If I try to send a mail i get "Unable to send message;Reason:553 Replaying disallowed. Invalid Domain - invata-programare.ro" Can you help me, please? Thank you!

                                  • Kaizen #241: Automating Deal risk escalation using Workflow APIs, Connected Workflows, and Functions

                                    Hello everyone! Welcome to another Kaizen week. In many organizations, sales teams work in Zoho CRM, finance teams manage invoices in Zoho Books, and support teams handle customer issues in Zoho Desk. Now consider this scenario: A sales representative

                                  • Upload own Background Image and set Camera to 16:9

                                    Hi, in all known online meeting tools, I can set up a background image reflecting our corporate design. This doesn't work in Cliq. Additionally, Cliq detects our cameras as 4:3, showing black bars on the right and left sides during the meeting. Where

                                  • Allow Super Admins to Edit Task “Created By” and Issue “Reporter” Fields

                                    Hello Zoho Projects Team, We hope you are doing well. We would like to submit a feature request regarding the ability to manage and correct system ownership fields in Zoho Projects, specifically: Task → Created By Issue → Reporter / Reported By Current

                                  • The Social Wall: April 2026

                                    Hello everyone, This month, we’re excited to bring you a set of new updates for Threads in Zoho Social, designed to make publishing, monitoring, and managing your content much easier Threads updates You’ll now see a few useful improvements in the compose

                                  • Sort or filter CRM report by count value

                                    Hi there, I'm trying to create a report that will show me high frequency bookings (leads) coming through within a time period for any particular account - this is so we can proactively reach out to these accounts. I have a report that shows the information

                                  • Error when changing user permission from read only to user.

                                    Hi there, Ive tried to change one of my users to be able to edit, however i kept getting the error user license exceed.

                                  • Marketing Tip #30: Promote your brand differently on each social platform

                                    Not all social platforms work the same way. Posting the same content in the same way across every channel can limit your reach. Each platform has its own discovery system, and understanding what it prioritizes can dramatically improve how your brand is

                                  • Whatsapp Limitation Questions

                                    Good day, I would like to find out about the functionality or possibility of all the below points within the Zoho/WhatsApp integration. Will WhatsApp buttons ever be possible in the future? Will WhatsApp Re-directs to different users be possible based

                                  • **Building Role-Appropriate Accountability Layers in Zoho Projects - Looking for Real-World Experience**

                                    We're a small ISP/telecom operator on Zoho One and I'm trying to solve what I think is a common organizational problem. Would love to hear from others who've tackled it. **The Core Problem** Staff will only consistently use a project management system

                                  • Duplicate entries for contacts birthdays

                                    Good morning I have recently started to use my Zoho calendar and noticed that there are multiple birthday events showing for some of my contacts. I have checked my contacts and there were duplicates for some contacts which I have now rectified but the

                                  • Using IMAP configuration for shared email inboxes

                                    Our customer service team utilizes shared email boxes to allow multiple people to view and handle incoming customer requests. For example, the customer sends an email to info@xxxx.com and multiple people can view it and handle the request. How can I configure

                                  • What's New in Zoho Billing | March 2026

                                    March is here with a fresh wave of updates to Zoho Billing. From making compliance easier, reporting more flexible, to making day-to-day workflows smoother across the board. Here's everything that's new this month. Introducing Usage-Based Billing Reports

                                  • Subforms in Creator-Lookup Price

                                    I've got a modular called Price List with items and prices. Ive got another module called Estimates with a subform that looks up that Price List. I am trying to get the "Price" to auto-enter based on the Lookup field of the item name. Anyone know how

                                  • Feature request - pin or flag note

                                    Hi, It would be great if you could either pin or flag one or more notes so that they remain visible when there are a bunch of notes and some get hidden in the list. Sometimes you are looking for a particular name that gets lost in a bunch of less important

                                  • Tip #20 - Three things you probably didn't know you can do with picklists

                                    Hello Zoho Sheet users! We’re back with another quick tip to help you make your spreadsheets smarter. Picklists are a great tool to maintain consistency in your spreadsheet. Manually entering data is time-consuming and often leaves typos and irregular

                                  • Map Dependency Upgrades in Zoho CRM

                                    Map Dependency Fields enhancements are available in CA, SA, JP, CN, UAE, AU and EU DCs. Latest update: Also available in IN and US DCs. Hello everyone, We’ve introduced a set of enhancements to Map Dependency Fields to make setup simpler, faster, and

                                  • CRM to FSM Setup

                                    Good Afternoon, I am trying to connect CMS to FSM. My current field mapping is: Companies ↔ Accounts Contacts ↔ Contacts Service And Parts ↔ Products I'm setting this up for an elevator service company. The idea is that: Accounts represent Companies.

                                  • Next Page