This week’s Zoho activity centers on a single tension: the platform is expanding fast — new SDK capabilities, richer CRM intelligence, and deeper cross-product integrations — while a stubborn cluster of long-standing data management gaps continues to frustrate teams running real workloads. Knowing which direction to lean determines how difficult your next build may be.
PageSense Goes Mobile-First with Full React Native SDK Coverage
Zoho shipped a complete React Native integration layer for PageSense this week, covering both Android (Kotlin bridge) and iOS (Swift/Objective-C bridge), alongside a shared JavaScript wrapper and SDK customisation options for polling intervals and logging. The release notes confirm the headline addition is Revenue Goal tracking via a new PageSenseUserContext object and typed Goal Properties, which means API improvement for teams tracking conversion value, not just conversion events. If your product has a React Native mobile surface and you’re not yet running server-side experiments, this removes the last significant integration barrier. The polling-interval control is worth tuning immediately: too aggressive and you increase network overhead; too conservative and experiment config changes lag in production.
Zoho CRM Gets Smarter Forms, Safer Sandboxes, and API Access to Its Own Code
Three CRM announcements this week collectively reduce the gap between “configured in Zoho” and “actually tested and auditable.” Layout Rules now support nine new actions — including Set Field Value, Recommend Field Value, Show Buttons, and Verify Fields — plus profile-based execution, meaning form behavior can now differ meaningfully by user role without custom code. More consequentially, CRM Sandbox now supports integrations with Zoho Campaigns, Analytics, Finance, Forms, Flow, Creator, Backstage, and Circuits, letting teams validate end-to-end automation before it touches production data. Finally, the long-requested Metadata API access to Functions is marked “Working on it” with a Q2/Q3 2026 target — a win for anyone trying to build dependency maps across Deluge logic. Sandbox integration support is the one to act on now: if your team has been hand-testing CRM-to-Finance or CRM-to-Flow automations in production, you no longer have an excuse.
Zoho Books Ships Meaningful Features While a Decade-Old Reconciliation Bug Festers
The July 2026 Books release is genuinely substantial — Terminal Payments via Stripe, Square, Paytm, and PhonePe; CMP-08 filing for Indian composition taxpayers; SEPA Credit Transfer support; and a new Receipts and Payments Report for non-profits. These signal Books maturing into a more complete regional accounting platform. But community context this week is hard to ignore: the reconciliation editing thread now carries a 10-year timestamp, with an MVP explicitly noting that fixing a single mismatched transaction still requires unwinding up to 35 months of reconciliations — something every competing platform handles natively. For teams evaluating Books for mid-market or multi-period accounting workloads, this specific limitation warrants a direct pre-sales conversation before committing. The Books-to-Analytics Locations module migration also deserves attention: any Analytics reports referencing “Warehouse ID” or “Branch ID” will break post-migration and must be updated to “Location ID.”
CRM Backup Auto-Storage and IMAP Email Reporting: Both Shipping Soon, Both Long Overdue
Two “Working on it” threads surfaced notable progress this week. The automated CRM backup storage feature — where backups would push directly to external storage rather than requiring manual downloads — has a Zoho team member confirming the enhancement is complete and nearly published, with early access for thread participants. Separately, the CRM Product Manager acknowledged directly why IMAP/POP3 emails don’t appear in CRM reports (they’re fetched from the mail server rather than stored in CRM, creating access-permission inconsistencies) and confirmed active work on a solution. Both are pain points that affect nearly every Zoho CRM team; if either is blocking a workflow for you, it’s worth following those threads for early-access notification.
Zoho Desk Automation Hits a Practical Wall: No Native addComment in Workflow Functions
A detailed community post this week documented a real-world AI-augmentation workflow — trigger on ticket creation, call an external AI API, write the draft response back as a private comment — that broke at the final step because zoho.desk.addComment() simply doesn’t exist in the Workflow Function runtime. The workaround requires falling back to REST API calls with explicit authentication handling, which is both fragile and poorly documented. This matters beyond one use case: as teams add AI steps to Desk automations, the absence of native comment-writing in Deluge becomes a recurring blocker. If you’re building in this space, budget time for the REST API path and watch whether Zoho closes this gap — it has the hallmarks of a widely-requested missing primitive. A related thread on CRM-to-Desk contact association by email domain further illustrates how much custom scripting teams still need to paper over native integration limits between these two products.
Zoho Notebook Quietly Expands Its Ecosystem Surface
Notebook received an unusually broad documentation refresh this week: new or updated guides covering Projects and Sprints extensions, Microsoft Teams and Slack integrations, a HIPAA compliance guide, and updated export options. The volume of simultaneous documentation suggests a coordinated positioning push rather than incremental updates — Notebook appears to be making a case for itself as a serious enterprise tool rather than a consumer note-taking app. Teams already in Zoho One who’ve overlooked Notebook as “just notes” should revisit it, particularly if they’re paying for a third-party tool to handle in-context documentation within Projects or Teams.
As we approach August next week for the CRM backup auto-storage feature to go live for early-access participants — and whether the Layout Rules rollout reaches remaining data centers.