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

    • Duplicate Leads Concerns with Round Robin and Lead Approval Process

      It is great to have the Duplicate Lead Approval Process, there are a few issues with the process that I would greatly appreciate taken consideration in enhancing. It appears that A Lead comes in Lead owner assigned by the Round Robin Check for Duplicate,

    • need a packing list feature

      In our business, goods listed on an invoice are packed in separate boxes and shipped off. for e.g. an invoice may have 10 items. each item could then be packed in different boxes depending on qty of each item. this packing list is as important as the invoice for purposes of shipping documents.  Request you to add this feature asap.

    • Editing Item Group to add Image

      I did not have the image of the product when the Item Group was created. Now I have the product image, and would like to associate/add to the Item Group. However the Item Group Edit functionality does not show/allow adding/changing image. Please hel

    • Zoho CRM Queries Now Support Databases and Cloud Data Sources

      Hello everyone! We're thrilled to announce a major enhancement to the Queries feature in Zoho CRM! Queries now support a broader range of external data sources, allowing you to fetch live data and combine it with CRM records, all using a unified query

    • 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,

    • Files Uploaded to Zoho WorkDrive Not Being Indexed by Search Engines

      Hello, I have noticed that the files I upload to Zoho WorkDrive are not being indexed by search engines, including Google. I’d like to understand why this might be happening and what steps I can take to resolve it. Here are the details of my issue: File

    • Introducing a smarter, faster, and more flexible charting experience

      Hello Zoho Sheet users, We're delighted to share the latest news about a major update to charts in Zoho Sheet! The new version supports dynamic data ranges, granular styling options, faster loading, and other interesting enhancements that allow you to

    • Zoho Bookings - Feature Request - Services Which Include A Resource and Consultant

      Hi Bookings Team, My feature request is to have the ability to add Consultants and Resources to Services. Use case: Your business provides first aid training and there are certain equpment you require to provide the half day training. There are only specific

    • Assign Meeting in records

      It would be nice to be able to "call and assing" meetings from a record, for example from a Deal. Right now - calendar is synced with CRM - meetings show in calendar - you can go in each meeting and assign it to a record It would be nice to be able to

    • You have reached the maximum limit of bank accounts that can be connected to Zoho Books through token.

      I can no longer connect to my bank account to download transactions into Zoho Books. I egt the error message: "You have reached the maximum limit of bank accounts that can be connected to Zoho Books through token. To connect more accounts, write to us

    • Sincronizar eventos de Bigin en Zoho Calendar (Zoho Mail)

      Hola Me gustaría poder sincronizar mi Calendario de Zoho (Mail) con los eventos de Bigin. No veo la opción disponible.

    • Sales Receipts in UK Free tier

      Is Sales Receipts available in UK Books, specifically at the Free tier? None of the options from the help pages are available to me.

    • My client requires me to have custom pdf file names to except payment for invoices, how can I customize this before emailing.

      Hello! I love the program so far but there are a few things that are standing in the way. I hope you guys can code them in so I can keep the program for years to come. My client requires I customize the pdf file names I send in for billing. Can you please

    • When I schedule calendar appointments in zoho and invite external emails, they do not receive invites

      Hello, We have recently transitioned to zoho and are having a problem with the calendar feature. When we schedule new calendar appointments in zoho the invite emails aren't being sent to the external users that we list in participants. However, this works

    • Migrate different zoho subscription to zoho one

      Dear We have different zoho subscription we need to migrate it to zoho one. Currently we are paying for zoho email, zoho expense, zoho payroll etc under different admin We need to move it too zoho one flexlible plan for all my employees

    • Bigin use in hospital- Human Med or Veterinary

      I am looking for users who are in either human or veterinary medicine and use the CRM specifically for referral management tasks. Are you using the basic version? How many users update the CRM and is it effective? Did you pay for additional customizations?

    • Internal Fillable Contract with Zoho Writer (Before Sending to Client)

      Hi everyone, I’m trying to automate the following process in Zoho CRM and would appreciate some guidance. Process: When a Deal moves to a specific stage, CRM triggers an automation. CRM sends a contract template to an internal team member so they can

    • How to sync overtime from zoho people to zoho payroll

      Hi everyone, I’m currently setting up Zoho People with Zoho Payroll. While configuring the sync, I noticed I can only fetch Employee Profiles, LOP (Loss of Pay), and enable the Employee Portal. I can’t seem to find a way to automatically pull Overtime

    • Standardize email communication with Signature Template

      Maintaining a consistent and professional signature across all outgoing emails is essential for any organization. However, when users manage their signatures individually, it often leads to inconsistencies like varying formats, missing designations, or

    • How can I export all Deluge code across the application?

      I’m working on a application with multiple forms, reports, and HTML views, where Deluge scripts are used across workflows, field actions, and custom functions. Is there a way to export all Deluge scripts into a single file for easier search?

    • Zoho Books: tax is not automatically pulled from product-data anymore - why?

      Hi, until a short time ago, you could set a default taxrate for each product/item. This taxrate automatically appeared each time the item was chosen in an invoice or quote. Why does this not work anymore? The field is still there at the product record,

    • Setting up property management in Zoho Books

      Hi, I run a property management business that manages property complexes. There are multiple owners, some owning more than one property on the same complex. My role is to manage the fees they pay for maintenance of common areas, such as the swimming pool

    • Zoho Creator to GMAIL API Setup - Where Do I Begin?

      Does anyone know how to connect Zoho Creator to Google Workspace (Specifically GMAIL?) We have FLOW setup and working fine to send emails via GMAIL, but Flow doesn't accept file attachments which is a major problem. So, we need to be able to send an email

    • Kiosk Page Refresh

      We have a Kiosk running from a button in contacts to update values and also add related lists, which works great, but when the kiosk is finished the page does not refresh to show the changes. Is there a way to force the contact to refresh/update when

    • All new Address Field in Zoho CRM: maintain structured and accurate address inputs

      Availability Update: 29 September 2025: It's currently available for all new sign-ups and for existing Zoho CRM orgs which are in the Professional edition exclusively for IN DC users. 2 March 2026: Available to users in all DCs except US and EU DC. 24

    • Setting GC session variable programatically in a website

      Hi! Is there a way now to programatically set session variables from a website for a Guided Conversations? The current available methods are dependent on react-native.

    • Ticket Merge Error

    • Refresh frequency

      Dear Zoho Team, I really, truly appreciate that Zoho Books gets frequent updates. As a matter of fact this is how a good SaaS company should stay on top. However, I feel that I have to hit refresh almost every day. This was exciting at the beginning but

    • Update application by uploading an updated DS file

      Is it possible? I have been working with AI on my desktop improving my application, and I have to keep copy pasting stuff... Would it be possible to import the DS file on top of an existing application to update the app accordingly?

    • Two-factor authentication (2FA) Log-in Problems

      The Two-factor authentication (2FA) Login on my passwords doesn't match , so it wont accept login I'm down to my last backup code.

    • Remove my video

      Hi, How can I remove my video so that I don't have to see myself. It's weird so I always remove my own video from what I see but cannot find this feature here. Thanks!

    • Client Script: Any plans to add support for multi-select field with onChange

      Client Script is fantastic and the documentation lists multiselect form fields as unsupported. Just wondering if there are any plans to make this a supported field. https://www.zoho.com/crm/developer/docs/client-script/client-script-events.html 2. Field

    • 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

    • Feature Reqeust - Include MPN In Selectable FIelds

      I have noticed that the MPN is not available to show in the list view of Items. Please consider adding it as EAN, UPC and ISBN are all available, so it doesn't make much sense to exclude this similar option. Thanks for considering my feedback.

    • Experience effortless record management in CRM For Everyone with the all-new Grid View!

      Hello Everyone, Hope you are well! As part of our ongoing series of feature announcements for Zoho CRM For Everyone, we’re excited to bring you another type of module view : Grid View. In addition to Kanban view, List view, Canvas view, Chart view and

    • Windows Desktop Application for Bigin

      I'm finding the need for a standalone Bigin desktop app for Windows users. Most of my daily work is done through a browser, so I often have several open tabs while working with customers and checking product information, etc. With Bigin currently only

    • Set another Layout as Standard

      We created a few layouts and we want to set another one to standard:

    • Salesforceに添付ファイルを格納したい

      お世話になっております。 Salesforceに添付ファイルを格納したく、カスタムオブジェクトに連携し、 「ファイルのアップロード」項目を設けました。 実際、エラーもなく送信出来たのですが、実際生成されたカスタムオブジェクトのレコードを見ると、どこにも添付ファイルがありません。仕様として、この添付ファイルはSalesforceのどこに格納されるのでしょうか？ 今回作りたいフォームは、複数の書類を添付するため、Zohoformのファイルアップロード項目「本人確認書類」「源泉徴収票」などの項目を、Salesforce側にも設けた「本人確認書類」「源泉徴収票」という各項目にURLリンクとして紐づけたいと思っておりました。

    • Knowledge Base article lists

      Is it possible to adjust the number of articles that are visible under a category of the Knowledge Base portal? Currently it looks like by default it populates about 5 articles before it puts the "more" option at the bottom. Looking to see if I can extend

    • Discrepancy in Contracts with Fields list/Layout

      The Support Plan field on the layout isn't in the fields list. What am I missing?

    • Next Page