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 can surface workflow failures but lack granularity for complex logic debugging. Write smaller functions. Log aggressively with info statements. Use try-catch to handle and log expected failure modes. Build admin reports that surface workflow failures from Application Logs.
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:

    • Recent Topics

    • Zoho Campaigns API endpoint for contact details

      there is some REST API support for Zoho Campaigns, however, I am not able to find an endpoint for "get contact details".  in particular, I'd like to access contact's subscription status and also their topic. ideally there is all profile available including

    • Migrating Documentation from Notion to Zoho Help Centre

      Hi there, We have a large chunk of documentation that currently sits on Notion. However, we are eager to move this into our Zoho Help Centre/Knowledge Base. What is the most efficient way of achieving this?

    • Can't add attachment on email template

      The attachment does show up. This is my template. Hi ${Cases.Assigned Programmers}, Please be reminded about the following task that has been assigned to you. Subject : ${Cases.Subject} Description : ${Cases.Description} Ticket # : ${Cases.Request Id}

    • Edit a previous reconciliation

      I realized that during my March bank reconciliation, I chose the wrong check to reconcile (they were for the same amount on the same date, I just chose the wrong check to reconcile). So now, the incorrect check is showing as un-reconciled. Is there any way I can edit a previous reconciliation (this is 7 months ago) so I can adjust the check that was reconciled? The amounts are exactly the same and it won't change my ending balance.

    • Custom CSS for Zoho CRM Team Bookings embeded widget

      Hello, we are adding Zoho CRM Team Bookings (crm.zoho.com) in our public website. We know that we can change Theme Color, Font Color and Background Color: Zoho CRM Booking Styling But is it possible to change other CSS attributes e.g. Font Family, like

    • Standard practice rerun updated deluge function over existing recordes

      Hi folks, we have a function which is triggered via webhook from a third-party solution which then calls another api with a contact-id and gets a json payload back and then parses that data to custom fields in our CRM to the record id. As requirements

    • Specifying time increments on a Date/Time field

      Hi all, Im using a Date/Time field in my CRM module. At the moment the increments are 30 minutes. How can I change these to be 15 minutes? Thanks

    • Sort by Project Name?

      How the heck do you sort by project name in the task list views??? Seems like this should be a no-brainer?

    • Maximum limit of bank accounts

      I'm currently setting up Zoho Books in order to migrate at the start of our next financial year (April) and while adding bank accounts I've tried to add a second account from the same bank and receive an error about the maximum limit of bank accounts.

    • Account and Email and Password

      I'm signing up as a Partner so I can move my website clients across to a separate email server from their current cPanel one.. So I have a Zoho account and then I moved one of my emails across to that account to test the import process... So the question

    • Zoho Sprints iOS and Android app update: Global view. Screen capture control, file encryption, tags enhancement(iOS)

      Hello everyone! We are excited to introduce new features in the latest version(v2.1) of the Zoho Sprints iOS app update. Let’s take a quick look at what’s new. 1. Global view Global view brings all your project items into one centralised space. You can

    • Creating Restaurant Inventory Management on Zoho

      Hi,  We run a small cloud kitchen and are interested to use Zoho for Inventory and Composite Item tracking for our food served and supplied procured to make food items.  Our model is basically like subway where the customer can choose breads, veggies,

    • Price Managment

      I have been in discussions with Zoho for some time and not getting what I need. Maybe someone can help explain the logic behind this for me as I fail to understand. When creating an item, you input a sales rate and purchase rate. These rates are just

    • How do I create an update to the Cost Price from landed costs?

      Hi fellow Zoho Inventory battlers, I am new to Zoho inventory and was completely baffled to find that the cost price of products does not update when a new purchase order is received. The cost price is just made up numbers I start with when the product

    • only 100 entry download entries in Zoho Form

      Is there a way to download more than 100 entries in a form at a time? It is capped (unless I am not doing the export correctly). This is very frustrating as I want to make sure I don't miss a record when downloading data. Thanks!

    • Zoho FSM Premium Edition is Here

      As your field service operations grow, so do the complexities — managing large distributed teams, keeping sensitive data secure, generating the right reports at the right time, and ensuring every technician dispatched is the right fit for the job. The

    • Seeking a WhatsApp Business App (not API) Zoho CRM integration

      We have a business need to integrated WhatsApp Business App (not API) into Zoho CRM to centrally manage communications between our Sales team and Leads & Contact. Is there a reputable integration available for this scenario of ours? Core features we would

    • Auto-sync field of lookup value

      This feature has been requested many times in the discussion Field of Lookup Announcement and this post aims to track it separately. At the moment the value of a 'field of lookup' is a snapshot but once the parent lookup field is updated the values diverge.

    • How are other Books users integrating crypto and digital assets into Books?

      If my company owns some digital assets I would want those to exist in Books as assets, and also be able to change the value as needed when generating reports. My company would also be receiving payment in cryptocurrencies and may sell at the time of payment

    • Lets Talk Recruit: Key takeaways from our India community meetups

      Welcome back to Let's Talk Recruit — the series where we bring you real stories, product insights, and community highlights from the world of recruitment. Our last post covered how Resume Harvester can take the follow-up out of hiring. This edition is

    • Unable to create new finance account in Zoho Books Android app due to missing account number field.

      Free plan I have enabled a setting via the website requiring unique account codes to be specified for all accounts. When using the android app, go to expenses, new expense, select account, new account. Promoted to enter the Account name and description.

    • How to Fetch data from Sales Order and Insert into Purchase Order with Deluge

      Hello, I am wanting to write a Deluge script that would take the shipping address on a Sales Order and upon conversion to a Sales Order automatically insert it into that corresponding PO. I am new to Deluge but understand that it has great capabilities.

    • Google Drive shared folder

      My deluge script has stopped working, no longer collecting files from Google Drive - have these connections finally been deprecated ?? They seem to be active but errors occur when updating them ?

    • Zoho Desk: Mobile Updates | Q1 2026

      Hello everyone, Greetings! As we gear up for the end of Q1, we are excited to share a quick journey into all that released in the first quarter of 2026. We have brought in a few enhancements in the mobile apps that improve overall user experience and

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

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

    • Additional Address - Company Name

      It would be very helpful to have a "Company Name" field in the Additional Address shipping section.  In a situation where you drop-ship orders to a different address or different company entirely, it may be necessary to list the company name of the receiver. I understand that the Attention field can be used for that purpose, but that's not really the intended purpose of that field.

    • Zoho Payroll's Kuwait, Oman, Qatar, Bahrain and Canada edition is available in Zoho One

      Great news for Zoho One users! Zoho Payroll has expanded to five new regions: Kuwait, Oman, Qatar, Bahrain, and Canada. And the best part? These new editions are fully integrated with Zoho One, just like our existing editions in India, the UAE, Saudi

    • Does Zoho Creator support multilingual translation for user-entered data?

      I understand that Zoho Creator provides localization support for UI elements such as field labels and static text. I would like to know: Does Zoho Creator support automatic translation of user-entered data (for example, form inputs or stored records)

    • Upload field on tasks module

      Hello, Why I cannot add an upload field to a Task? Or maybe when creating the task make attachements visible, so you can add an attachement while creating the task? Looking forward to your response! Moderation Update: The Canvas detail view for the Tasks

    • WhatsApp phone number migration

      Hi @Gowri V and @Pheranda Nongpiur, Thanks for implementing the promised enhancements to the integration between Zoho CRM and WhatsApp. The previous discussion has been locked, so I'm opening this new one. I am copying below a specific

    • How to let club members update their own profile data

      Our club has about 200 members. We keep names, addresses, phones, emails, payment records, etc. for each, recently migrated to Creator. Once a year I send email to each member to confirm or correct their info on file with us, as well as ask for payment

    • Document retention in Zoho Sign

      Document management doesn’t end at signing. It extends to how long you retain agreements—and how securely you dispose of them. With the document retention option in Zoho Sign, you can define structured, policy-driven timelines for managing completed documents.

    • Sales Allowed Beyond Available Stock and Payment Recorded Without Restriction

      Hi, While testing in Zoho Inventory, I noticed that a sales order can be created with a quantity exceeding the available stock in the selected warehouse. In my case: Available stock: 5 units Ordered quantity: 6 units Despite this: I was able to convert

    • Deleting, Adding and Changing a Zoho Books Entry

      Zoho Books Community & Support, If a bulk upload of entries were added to an account, what is the process to: - Delete an entry - Change the amount of an entry - Is there a means to manually add an entry other than upload?

    • Zoho CRM - Feature Request - Analytics Components Group By Week Alternative Formats

      On the Zoho CRM Analytics Components, please consider adding an option to allow group by week format to be changed to other formats such as Week Commencing or Week Ending dates, rather than the current Week Number. This would provide improved usability

    • The Social Playbook March edition: Myth vs Facts

      We’ve all heard a lot of myths growing up. Some sound convincing, some feel believable, and over time they start to feel like facts. But the truth is, a myth is still a myth until it’s backed by real facts. Marketing is no different. Over time, many ideas

    • Updating Analytical Fields Data

      Dear Zoho team, I'm having an issue with the recently added fields in both Analytical Desk and Analytical. How can I generate the data in Analytical when new fields are added? https://analytics.zoho.com/workspace/2436819000000007005/edit/24368190000

    • Marketing Tip #26: Optimize product images for SEO

      Product images can do more than make your store look good. They can also help customers discover your products through search. Since search engines can’t "see" images, they rely on text signals to understand what an image is about. Two small actions make

    • What's New in Zoho Analytics - February 2026

      Hello Users! We're back with another round of updates for Zoho Analytics. This month's release focuses on giving you greater flexibility in how you visualize, manage, and act on your data - with new features like custom visualizations, remote MCP server,

    • Clone a Module??

      I am giong to repurpose the Vendors module but would like to have a separate but very similar module for another group of contacts called Buyers. I have already repurposed Contacts to Sellers. Is it possible to clone (make a duplicate) module of Vendors

    • Next Page