CRM Explorer
Metadata Intelligence Hub for Zoho CRM
16
Modules
1
Extension
100%
Visibility
v1.0 · April 2026 · Built by Aaxonix Tech
Introduction
Overview

CRM Explorer is a Zoho CRM WebTab widget that provides complete metadata visibility across your entire organisation - schema, automation, users, permissions, data flow, and more - all from a single, unified dashboard. It connects directly to your Zoho CRM org via OAuth and surfaces information that would otherwise require dozens of separate admin screens to piece together.

CRM Explorer is designed for teams who need a fast, reliable audit of their CRM configuration. Whether you're onboarding a new client, conducting a health check before a migration, tracking down an automation conflict, or simply trying to understand what your org contains, CRM Explorer gives you the full picture in seconds.

No external data leaves your org. CRM Explorer reads your Zoho metadata via Zoho's own APIs and displays it within the widget. Nothing is stored on Aaxonix servers. All caching is browser-local.

Who It's For
CRM Admins

Get a complete, real-time picture of your org's configuration, automation, permissions, and user state without navigating dozens of setup pages.

Zoho Partners & Consultants

Audit a client's org in minutes. Generate exportable reports, spot config drift, and document the current state before any project begins.

Operations Managers

Understand data flows, identify automation overlaps, review permission structures, and ensure your CRM is configured to match your business processes.

Developers

Browse all Deluge functions, inspect field API names, trace automation dependencies, and commit code summaries directly to GitHub - all within the widget.

Prerequisites
  • Zoho CRM account - Professional plan or above
  • Access level - Admin or Super Admin role required
  • Browser - Google Chrome, Mozilla Firefox, or Microsoft Edge (latest versions recommended)
Getting Started
Installation Steps
  1. 1
    Log in to Zoho CRM as Administrator Ensure you are signed in with an Admin or Super Admin account. Standard user accounts do not have access to the Widget setup screens.
  2. 2
    Go to Setup → Developer Space → Widgets In the top-right corner of Zoho CRM, click the Setup gear icon. In the left panel, navigate to Developer Space and then select Widgets.
  3. 3
    Click "New Widget" → Select type "WebTab" Click the New Widget button. When prompted for the widget type, select WebTab. Give the widget a name - for example, CRM Explorer.
  4. 4
    Set hosting to External and enter the widget URL Set Hosting to External, then enter the following as the Base URL:

    https://aaxonix.com/Zoho-Plugins/Zoho-CRM-Explorer/widget

    Click Save.
  5. 5
    Open the Web Tabs setup Still in Setup, navigate to CustomizationModules and Fields. In the top tab bar, click Web Tabs, then click New Web Tab.
  6. 6
    Enter a Tab Name and set Source to Widgets Enter a Tab Name (e.g. CRM Explorer). Under Source, select Widgets. A Widget dropdown will appear — choose the CRM Explorer widget you created in the previous steps.
  7. 7
    Set Web Tab Access and save Under Web Tab Access, select which profiles should see the tab (at minimum, Administrator). Click Save.
  8. 8
    Open CRM Explorer from the top navigation CRM Explorer will now appear as a tab in your Zoho CRM top navigation bar. Click it to open the widget. It will load and prompt you to complete the connection setup.

CRM Explorer requires the connection setup (OAuth) to be completed before data will load. See Connection Setup ↓ for step-by-step instructions.

Connection Setup

This is a one-time setup. Once connected, CRM Explorer caches your org data for fast repeat access. You will not need to repeat this process unless you revoke the connection.

Connection Steps
  1. 1
    Open the Connections Page and create a new connection Inside the CRM Explorer widget, click Open Connections Page. This opens the Zoho Connections panel. Click Create Connection.
  2. 2
    Select Zoho CRM and set the link name Search for Zoho CRM in the connector list and select it. In the Link Name field, enter exactly:
    crmauditconnector
  3. 3
    Add the required OAuth scopes Search for and tick each of the following scopes:
    ZohoCRM.settings.ALL ZohoCRM.modules.ALL ZohoCRM.users.READ ZohoCRM.org.READ ZohoCRM.settings.scoring_rules.READ ZohoCRM.settings.workflow_rules.READ ZohoCRM.settings.automation_actions.ALL ZohoCRM.functions.execute.READ
  4. 4
    Save and authorise the connection Click Save, then click Connect to authorise via OAuth. Zoho will prompt you to grant permission - accept. Once authorised, return to CRM Explorer and click I've connected it.

The connection name must be exactly crmauditconnector - all lowercase, no spaces, no hyphens. Using a different name will cause authentication to fail and the widget will not be able to load any data.

Using a Different Connection Name

If you used a different link name when setting up the connection, enter it in the Connection Link Name field on the connect screen instead of crmauditconnector. CRM Explorer will use whatever name you enter for all API calls.

Global Interface
Top Bar

The top bar is persistent across all modules and provides global controls:

  • Search (⌘K) - Opens the universal search overlay. Search across all modules, fields, users, workflows, and functions simultaneously.
  • Data age indicator - Shows how long ago your org data was last collected (e.g. "collected 12 min ago"). Helps you know if you're working with fresh or cached data.
  • Export button - Opens the Export Menu with seven export formats. See Export Menu.
  • Refresh button - Triggers a full re-collection of all org data from the Zoho API. Clears the cache and reloads everything from scratch.
  • Settings ⚙️ - Opens the settings panel where you can change your connection name, adjust preferences, and view widget metadata.
  • Theme toggle - Switches between light and dark display modes.
Sidebar Navigation

The left-hand sidebar organises CRM Explorer's 16 modules into logical groups:

  • Command Center - Dashboard overview and org summary
  • Schema - Entity Explorer, ER Graph, Field Audit, Data Flow
  • Automation - Automation Map, Blueprint Studio, Function Registry, Email Templates
  • Governance - Permission Matrix, User Audit, Change Checker
  • Analysis - Config Review, Dead Weight, Module Compare, Org & Config

Clicking any item in the sidebar switches the active panel instantly. The selected item is highlighted with a blue left-border indicator.

Cache Banner

When CRM Explorer loads data from its local cache rather than making a live API call, a banner appears at the top of the content area:

Example banner

Loaded from cache - collected 8 minutes ago    Refresh Now

Click Refresh Now in the banner to trigger a full re-fetch. The cache keeps CRM Explorer fast on repeat visits and reduces unnecessary API calls to Zoho.

Use ⌘K (or Ctrl+K on Windows) to search across all modules, fields, users, workflows, and functions simultaneously. It's the fastest way to find anything in your org.

Export Menu

Click the Export button in the top bar to open the Export Menu. CRM Explorer offers seven export formats suited to different audiences and use cases.

Full JSON

Complete raw metadata export covering all modules, fields, automations, users, and settings. Ideal for developers and system integrations.

Field Inventory CSV

All fields across all CRM modules exported in spreadsheet form. Perfect for field-level audits, data mapping, and migration planning.

Workflow CSV

All automation rules - workflows, blueprints, macros, and more - exported in a clean tabular format for review and documentation.

User Report CSV

A complete user list including roles, profiles, reporting managers, and account status. Useful for governance and access reviews.

Standalone HTML

A fully portable, self-contained snapshot of the entire audit. Shareable with stakeholders who don't have CRM access - no login required to view.

Copy Summary

Copies a concise plain-text summary of your org's key stats to the clipboard. Ready to paste into a document, Slack message, or email.

Fetch Audit Report

Generates a comprehensive diagnostic report covering configuration health, automation conflicts, permission gaps, and unused assets.

The Standalone HTML export is ideal for sharing audit results with stakeholders who don't have CRM access. The exported file is fully self-contained - open it in any browser with no dependencies.

Dashboard

nb-dash

Overview

The Dashboard is the first view you see when CRM Explorer loads. It displays a health score gauge (0–100), key metric cards showing total modules, custom fields, active users, and automation rules, plus a dimension breakdown bar that lets you jump directly to any audit area. Think of it as a single-screen pulse check on your entire CRM configuration.

When to use it

First-time audit

Run the dashboard when onboarding a new client org to get an instant high-level picture before diving into specifics.

Weekly health check

Bookmark the dashboard for a quick Monday review. The health score trends over time as you clean up your CRM.

Prioritise remediation

The dimension bars show which areas (fields, automation, permissions) are dragging your score down most.

Stakeholder briefing

Use the at-a-glance stats when briefing management or a client on the current state of their CRM.

Step-by-step guide

  1. Open CRM Explorer - the Dashboard loads automatically as the default view.
  2. Review the health score gauge in the top-left - anything above 80 is healthy; below 60 needs attention.
  3. Read the metric cards: total modules, custom fields, active workflows, and user count.
  4. Click any dimension bar (e.g. "Fields" or "Automation") to jump directly to that audit module.
  5. Use the Refresh button in the top bar to re-collect data if your org has changed recently.

Example scenario

A Zoho consultant opens CRM Explorer on a client's org for the first time. The health score reads 42/100. The dimension bar shows "Automation" in red. She clicks the bar and jumps straight to Automation Map, where she finds 37 inactive workflows that have never fired. With one afternoon's cleanup, the score rises to 71.

Pro tips

If the health score seems lower than expected, check the Config Review module - it often flags picklist mismatches and permission gaps that drag the score down disproportionately.

Entity Explorer

nb-entity

Overview

Entity Explorer gives you a searchable, filterable catalog of every module in your Zoho CRM - both standard modules (Leads, Contacts, Deals, Accounts) and custom modules you've built. Select any module to see all of its fields, which layouts they appear in, related lists, and metadata like data type, mandatory status, and API name.

When to use it

Field discovery

Need to know the exact API name of a field for a Deluge function? Entity Explorer shows it instantly.

Layout audit

Find which fields appear in the desktop layout but not the mobile layout, or vice versa.

Pre-migration check

Before a data migration, confirm which fields are mandatory and which have picklist constraints.

Step-by-step guide

  1. Click Entity Explorer in the left sidebar.
  2. Use the search bar or module-type filter to find your target module.
  3. Click a module name to expand its detail view.
  4. Browse tabs: Fields, Layouts, Related Lists, and Settings.
  5. Click any field row to see its full metadata: API name, data type, mandatory flag, unique constraint, and layout appearances.

Example scenario

A developer is writing a Deluge function to auto-populate a custom field on the Deals module. She opens Entity Explorer, selects "Deals", and searches for the field name. Within seconds she has the exact API name (Custom_Field_1) and confirms it's a text field with no character limit - saving 20 minutes of trial and error.

Pro tips

Use the 'API Name' column in Entity Explorer when writing Deluge scripts or building integrations. Display names can be localised; API names never change.

ER Graph

nb-er

Overview

The ER Graph renders an interactive, drag-and-drop diagram showing how every module in your CRM connects to every other module through lookup and multi-select lookup fields. Nodes are modules; edges are lookup relationships. Hover on any edge to see the exact field that creates the link.

When to use it

Architecture mapping

Understand how a newly inherited CRM is structured before touching anything.

Dependency tracing

Before deleting a module, see all other modules that reference it via lookups.

Documentation

Use the diagram as a visual asset in technical documentation or client presentations.

Step-by-step guide

  1. Click ER Graph in the sidebar.
  2. Wait for the D3 force layout to settle - nodes will spread out automatically.
  3. Drag nodes to rearrange the graph for clarity.
  4. Hover over a connection line to see the lookup field name and direction.
  5. Click a node to highlight only its direct connections, dimming unrelated modules.

Example scenario

An admin is asked to remove the "Projects" custom module. Before doing so, she opens the ER Graph and clicks the Projects node. The graph highlights 4 outgoing lookup connections - Deals, Contacts, Tasks, and a second custom module - confirming that deletion would break 4 dependent modules. She creates a migration plan instead.

Pro tips

If the graph is too dense to read, use your browser zoom (Cmd/Ctrl −) to zoom out and see the full picture, then zoom in on the cluster you care about.

Field Audit

nb-field

Overview

Field Audit is a six-tab deep-dive into every field across your CRM. It surfaces inconsistencies, coverage gaps, and unused fields that accumulate over time as admins add fields without a governance process. The six tabs are: Picklist, Heatmap, Data Types, Required Fields, Layout Assignments, and Lead Convert Mapping.

Picklist Heatmap Data Types Required Fields Layout Assignments Lead Convert

When to use it

Picklist governance

Find dropdown fields with different option lists across modules (e.g. "Industry" has 8 values in Leads but only 5 in Contacts).

Field adoption

The heatmap shows which fields are actually populated vs ghost fields that admins added but users ignore.

Layout compliance

Ensure mandatory fields actually appear on all relevant layouts so users can't skip them.

Lead conversion

Confirm that every key Lead field maps correctly to a Contacts/Accounts/Deals field during conversion.

Step-by-step guide

  1. Click Field Audit in the sidebar.
  2. Select the Picklist tab - review any fields flagged in red for value inconsistencies across modules.
  3. Switch to the Heatmap tab - fields with <10% fill rate are candidates for archiving.
  4. Open Data Types to get a count of text, picklist, currency, date, and lookup fields by module.
  5. Check Required Fields to confirm mandatory fields have adequate coverage across layouts.
  6. Review Lead Convert Mapping to verify no important data is lost during the Leads → Contacts conversion.

Example scenario

A CRM admin notices that the sales team is entering "Industry" inconsistently across Leads and Contacts. She opens Field Audit → Picklist tab and immediately sees the problem: Leads has "Financial Services" while Contacts has "Finance". She standardises both picklists in 10 minutes, fixing months of reporting errors.

Pro tips

Run Field Audit before any reporting project. Heatmap fill rates often reveal that the fields driving your key reports have <30% data coverage - a root cause of inaccurate dashboards.

Data Flow

nb-flow

Overview

Data Flow maps inbound and outbound data movement for any module - showing which lookups pull data in, which workflows push data out, which blueprints gate state changes, and which custom functions read or write to the module. Select any module from the dropdown to see its complete data ecosystem.

When to use it

Impact analysis

Before modifying a module's structure, understand every upstream and downstream dependency.

Data quality debugging

Trace where a field value is being set or overwritten by finding all automation that writes to it.

Architecture reviews

Present a client with a visual map of how their CRM data flows as part of a health check report.

Step-by-step guide

  1. Click Data Flow in the sidebar.
  2. Select a module from the dropdown (e.g. "Contacts").
  3. Review the Inbound panel - these are all sources that push data into the selected module.
  4. Review the Outbound panel - these are all places the module's data flows to.
  5. Click any flow line to see the specific field, workflow, blueprint, or function driving it.

Example scenario

A consultant is debugging why a Contact record's "Account Manager" field keeps being overwritten. She selects "Contacts" in Data Flow and sees 3 inbound workflow rules all targeting the same field. She traces the conflict back to two rules with overlapping triggers and deactivates the redundant one.

Pro tips

Data Flow is most powerful when combined with Change Checker. Use Data Flow to understand the architecture, then Change Checker to verify the blast radius before making a change.

Automation Map

nb-auto

Overview

Automation Map aggregates all of your CRM automation in one view: workflow rules, validation rules, and assignment rules, across every module. Each row shows the rule name, module, trigger type, status (active/inactive), and a 90-day trigger count. Sort by trigger count to find dead automation; filter by module to focus your cleanup.

When to use it

Automation cleanup

Identify inactive workflows or ones with 0 triggers in the last 90 days. These are candidates for archiving.

Pre-migration audit

Before a CRM migration, export the full automation list to document what needs to be rebuilt.

Conflict detection

Spot multiple workflows on the same module with the same trigger - a common source of data inconsistencies.

Compliance check

Verify that required validation rules are active on all customer-facing modules.

Step-by-step guide

  1. Click Automation Map in the sidebar.
  2. Use the module filter to narrow to a specific module, or view all automation together.
  3. Sort by "90-day triggers" ascending to surface workflows that have never fired.
  4. Click any row to expand its details: trigger conditions, actions, and last fired date.
  5. Use the status filter to view only Active or only Inactive rules.

Example scenario

A new CRM admin inherits a Zoho CRM with 94 workflow rules. She opens Automation Map, sorts by trigger count, and finds 41 rules with 0 triggers in 90 days - all of them inactive relics from previous projects. After a quick review with the team, she archives 34 of them, dramatically reducing execution overhead.

Pro tips

Sort by trigger count descending to find your highest-volume automation. High-trigger rules with many actions are your biggest performance risks - review them for efficiency.

Blueprint Studio

nb-bp

Overview

Blueprint Studio renders a visual state diagram for each Blueprint in your CRM. You see every state (stage), every transition between states, which fields are required before a transition can be executed, and which profiles are permitted to make each transition. This replaces the need to click through Blueprint settings one-by-one to understand the process.

When to use it

Process documentation

Generate a visual map of your sales or service process for onboarding or compliance purposes.

Permission audit

Verify that only the right profiles (e.g. only "Manager" profile) can execute high-stakes transitions like "Close Won".

Blueprint redesign

Before restructuring a blueprint, use the visual to identify redundant states or missing transitions.

Step-by-step guide

  1. Click Blueprint Studio in the sidebar.
  2. Select a Blueprint from the module dropdown.
  3. The state diagram renders automatically - states are nodes, transitions are directed arrows.
  4. Click any transition arrow to see: required fields, permitted profiles, and any automation triggered on entry.
  5. Use the zoom controls to navigate large blueprints with many states.

Example scenario

A sales ops manager is asked to document the company's deal approval process for an ISO audit. She opens Blueprint Studio, selects the "Deals" blueprint, and screenshots the state diagram - a clean visual showing the 7-stage approval flow. The audit is satisfied in minutes instead of hours.

Pro tips

If a blueprint has a transition with no required fields, it means users can move a deal to the next stage without any data. Check whether this is intentional - it's a common governance gap.

Function Registry

nb-func

Overview

Function Registry lists every custom function in your Zoho CRM - Deluge, Java, and others - grouped by category: Standalone, Button, Workflow, Related List, Scheduled, and Connected App. For each function you see its name, category, associated module, and API call context. Use it to audit redundant functions, find orphaned code, and understand what's running in your org.

When to use it

Code inventory

Get a complete picture of all custom logic running in your org before a technical review.

Dead code detection

Find standalone functions that aren't called by any workflow, button, or blueprint - they're safe to remove.

Handover documentation

When transitioning CRM ownership, export the function list as a baseline for the incoming developer.

Step-by-step guide

  1. Click Function Registry in the sidebar.
  2. Switch between category tabs: Standalone, Button, Workflow, Related List, Scheduled, Connected App.
  3. Click any function row to see its full metadata: language, associated module, and creation date.
  4. Use the search box to find functions by name or keyword.
  5. Cross-reference with Dead Weight → Functions tab to identify unused functions.

Example scenario

A Zoho developer inherits a CRM with 60+ custom functions. She opens Function Registry, filters by "Standalone", and finds 18 standalone functions - none of them referenced in any workflow or blueprint. She reviews each one and archives 12 that are confirmed orphans.

Pro tips

Use the Call Graph tab to see at a glance which functions are heavily referenced versus orphans. The filter chips and search make it easy to work with hundreds of callers without scrolling.

Email Templates

nb-tpl

Overview

Email Templates lists every email template in your CRM, organised by folder. For each template you see its name, associated module, merge fields used, and folder assignment. This lets you spot templates with missing merge fields, orphaned templates with no folder, and templates that reference fields that no longer exist.

When to use it

Template cleanup

Find templates with no module association or no merge fields - these are likely abandoned drafts.

Merge field audit

Verify that merge fields in your templates still reference valid, populated fields.

Folder governance

Ensure all templates are organised into folders and owned by the right team.

Step-by-step guide

  1. Click Email Templates in the sidebar.
  2. Browse by folder or use the search bar to find a specific template.
  3. Click a template row to see its merge fields, module, and last modified date.
  4. Look for templates flagged with a warning indicator - these reference fields that may have been renamed or deleted.
  5. Cross-reference with Dead Weight → Templates tab for templates with zero sends.

Example scenario

An admin is cleaning up before migrating to a new email sender. She opens Email Templates and finds 23 templates with no folder assignment - all leftover from a previous project. She also finds 6 templates using merge fields that reference a deleted custom field. She deletes 15 unused templates and fixes the 6 broken merge fields before the migration.

Pro tips

After any field rename or deletion, run Email Templates immediately to catch broken merge field references. A broken merge field sends {!Leads.Deleted_Field} literally in customer emails.

Permission Matrix

nb-perm

Overview

Permission Matrix gives you a complete, cross-profile view of field-level permissions in your CRM. The four tabs cover: an Overview summary, a full Permission Matrix grid (fields × profiles), a Role Hierarchy tree, and a Profile-to-User mapping. This replaces the tedious process of clicking through each profile individually in CRM Settings.

Overview Matrix Role Hierarchy Profile → User

When to use it

Security audit

Verify that sensitive fields (salary, credit score, GDPR data) are hidden from non-authorised profiles.

Onboarding new profiles

When creating a new role, use the matrix to compare it against existing profiles to ensure consistent permissions.

Support escalation

When a user reports they can't see a field, find their profile in the matrix instantly to diagnose the issue.

Compliance reporting

Export the permission matrix for GDPR, HIPAA, or SOC 2 compliance evidence.

Step-by-step guide

  1. Click Permission Matrix in the sidebar.
  2. Start with the Overview tab for a summary of total profiles and permission coverage.
  3. Switch to Matrix - select a module to see a grid of every field vs every profile.
  4. Green = read-write, yellow = read-only, red = hidden.
  5. Open Role Hierarchy to visualise the reporting structure and inherited permissions.
  6. Use Profile → User to see exactly which users belong to each profile.

Example scenario

A GDPR audit reveals that the "Date of Birth" field on Contacts may be visible to too many profiles. The admin opens Permission Matrix → Matrix, selects "Contacts", and filters for "Date of Birth". She immediately sees it's visible to 5 profiles including "Sales Rep" - a compliance violation. She restricts access to 2 profiles in 3 minutes.

Pro tips

The Matrix tab is colour-coded. If you see a mix of green and yellow in the same row across profiles for a sensitive field - that's an inconsistency worth investigating.

User Audit

nb-users

Overview

User Audit provides a full inventory of every user in your CRM across four tabs: All Users, Active Users, Disabled Users, and Orphans. The Orphans tab is particularly powerful - it surfaces disabled users who still own open records, workflows, or automation, which can cause silent failures in your CRM processes.

When to use it

Offboarding cleanup

When an employee leaves, use the Orphans tab to find and reassign all records they own.

Licence audit

View active vs disabled user counts to ensure you're not paying for unused licences.

Profile compliance

Verify that every user has the correct profile and role assigned.

Step-by-step guide

  1. Click User Audit in the sidebar.
  2. Review the All Users tab for total headcount, timezone distribution, and confirmation status.
  3. Switch to the Disabled Users tab to see all deactivated accounts.
  4. Open the Orphans tab - this shows disabled users who still own active records, workflows, or automation.
  5. For each orphan, plan a reassignment of their owned items before permanently removing the user.

Example scenario

A company downsizes and 12 sales reps are deactivated in CRM. Three weeks later, several workflows stop sending follow-up emails - the "From" user is deactivated. The admin opens User Audit → Orphans, sees all 12 former reps listed with their owned automation, and reassigns each workflow to an active user in one session.

Pro tips

Run the Orphans audit every quarter, especially after organisational changes. A disabled user who owns a workflow action is one of the most common causes of silent CRM failures.

Change Checker

nb-impact

Overview

Change Checker is the safety net before any CRM modification. Select any module, field, workflow, or function and immediately see: what would BREAK (hard dependency - must fix), what MIGHT be affected (soft dependency - review recommended), and what's SAFE to change. Think of it as a pre-flight check for your CRM.

When to use it

Before deletion

About to delete a field or workflow? Check here first to avoid breaking dependent automation.

Before renaming

Renaming a field changes its display name but not its API name - Change Checker shows where the display name is referenced in templates.

Before module changes

Restructuring a module? See every workflow, blueprint, function, and template that references it.

Change management

Use the output to produce a change impact document for your CRM change management process.

Step-by-step guide

  1. Click Change Checker in the sidebar.
  2. Select the entity type: Module, Field, Workflow, Blueprint, or Function.
  3. Pick the specific item from the second dropdown.
  4. Instantly review the three-panel result: BREAKS, MIGHT AFFECT, SAFE.
  5. For each item in BREAKS, resolve the dependency before making your change.

Example scenario

A developer is about to delete a custom function called auto_assign_lead. Before doing so, he opens Change Checker and selects Functions → auto_assign_lead. The BREAKS panel shows 3 workflow rules and 1 blueprint transition that call this function directly. He updates all four before deleting, preventing a complete breakdown of the lead assignment process.

Pro tips

Change Checker is most valuable for fields with picklist type - renaming a picklist value in one module may break validation rules and workflow conditions that check for the old value string.

Config Review

nb-drift

Overview

Config Review (formerly Drift Detector) scans your entire CRM configuration and scores it for consistency. It flags issues like: the same picklist field having different option sets across modules, fields that are mandatory on one layout but optional on another, lead conversion mappings that leave data behind, and permission mismatches. The score ranges 0–100; below 70 needs attention.

When to use it

Baseline scoring

Get a configuration health score before starting a CRM cleanup project.

Inconsistency hunting

Find picklist value differences between Leads and Contacts that cause reporting errors.

Post-project validation

After a cleanup or migration, re-run Config Review to confirm the score improved.

Step-by-step guide

  1. Click Config Review in the sidebar.
  2. Review the overall score on the Overview tab.
  3. For any score below 70, click into each category to see specific issues.
  4. Each issue includes the affected module, field, and the exact inconsistency found.
  5. Fix issues in CRM Settings, then refresh CRM Explorer and re-run the audit to confirm improvement.

Example scenario

After merging two regional CRM orgs, a consultant runs Config Review and gets a score of 51/100. The top issue: the "Lead Source" picklist has 12 options in the UK org and 9 in the US org - 3 values mismatch. She standardises both orgs to 14 unified values and re-runs the audit - score jumps to 78.

Pro tips

The 'Picklist Consistency' category is almost always the highest-impact fix. Inconsistent picklist values corrupt cross-module reports and pipeline analytics.

Dead Weight

nb-dead

Overview

Dead Weight identifies configuration that exists in your CRM but serves no active purpose: ghost fields (custom fields not referenced in any layout, workflow, or function), unused custom functions (not called by any trigger or automation), and orphaned email templates (never sent, no workflow reference). Cleaning dead weight improves CRM performance and reduces admin confusion.

When to use it

CRM spring clean

Run Dead Weight quarterly to keep your configuration lean and maintainable.

Performance improvement

Removing ghost fields reduces the number of fields CRM processes on every record load.

Developer handover

Before handing a CRM to a new admin or partner, clear dead weight so they're not confused by orphaned config.

Step-by-step guide

  1. Click Dead Weight in the sidebar.
  2. Start with the Ghost Fields tab - these are custom fields in no layout, no workflow, and no function.
  3. For each ghost field, verify in Entity Explorer that it truly has no references before archiving.
  4. Switch to Functions - unused functions can be archived after checking with the team.
  5. Review Templates for email templates with no folder assignment and no send history.

Example scenario

A CRM admin runs Dead Weight on a 3-year-old org. She finds 67 ghost fields (custom fields added by former admins but never placed in any layout), 18 unused functions (Deluge scripts from abandoned projects), and 34 orphaned email templates. After a team review, she removes 48 fields, 15 functions, and 29 templates - making the CRM noticeably faster to navigate.

Pro tips

Never delete a ghost field without checking with the team first - some ghost fields are used by API integrations that write directly to the field API name without appearing in any layout.

Module Compare

nb-modcmp

Overview

Module Compare lets you select any two modules and view their configuration side by side - fields, layouts, automation count, blueprint status, and permission assignments. This is particularly useful when you have mirror modules (e.g. UK Leads vs US Leads as separate custom modules) and need to ensure parity.

When to use it

Mirror module parity

Ensure two similar modules (e.g. two regional versions of Contacts) have the same field set and automation.

Module consolidation planning

Before merging two modules, compare their fields to plan the migration mapping.

Rollout validation

After replicating a configuration change from one module to another, confirm both modules now match.

Step-by-step guide

  1. Click Module Compare in the sidebar.
  2. Select Module A from the first dropdown.
  3. Select Module B from the second dropdown.
  4. Review the diff panels: fields only in A, fields only in B, and shared fields.
  5. Check the automation and layout counts for each module to spot coverage gaps.

Example scenario

A company runs separate "Enterprise Leads" and "SMB Leads" modules. After a sales reorg, both teams now use the same process. The admin opens Module Compare, selects both modules, and sees Enterprise Leads has 14 more custom fields. She maps the relevant fields for migration and archives the redundant ones before merging.

Pro tips

Module Compare is most useful before a consolidation. Run it early - the field diff often reveals more complexity than expected and changes your migration timeline.

Org & Config

nb-org

Overview

Org & Config shows the top-level details of your Zoho CRM organisation: licence type, edition, timezone, currency settings, GDPR and HIPAA compliance flags, connected external services (Google, Microsoft, telephony), API domain, and data-centre region. It's the first stop for a new consultant learning about a client's CRM setup.

When to use it

Onboarding clients

Get all the key org details in one screen when starting a new CRM engagement.

Compliance verification

Confirm GDPR/HIPAA flags are correctly set before a compliance review.

Integration inventory

See all connected external services without clicking through 8 settings screens.

Step-by-step guide

  1. Click Org & Config in the sidebar (bottom of the left nav).
  2. Review the licence type and edition - this determines which features are available.
  3. Check timezone and currency settings - mismatches here cause reporting anomalies.
  4. Verify compliance flags: HIPAA On/Off, GDPR On/Off.
  5. Review connected services to see which external platforms are integrated.

Example scenario

A new consultant starts work on a client's Zoho CRM. Before touching anything, she opens Org & Config and discovers the org is on Enterprise edition, uses the EU data centre, has GDPR enabled but HIPAA disabled, and has 3 external integrations: Google Workspace, Twilio, and Shopify. This 30-second scan shapes her entire engagement plan.

Pro tips

Always check the API domain in Org & Config when writing integrations. EU orgs use crm.zoho.eu - not crm.zoho.com - and sending API calls to the wrong domain causes authentication failures.

AI CRM Assist

nb-ai NEW

Overview

AI Assist turns CRM Explorer from a read-only audit tool into a configuration assistant. It ships with a senior-consultant system prompt, full access to your CRM schema context, and the ability to execute safe configuration changes through a preview-and-approve flow. Every write is previewed before it hits Zoho, and every response is grounded in the audit data you've already collected, so answers are specific to your CRM and not generic Zoho documentation.

What it can do

Answer questions

"Which workflows are inactive?", "Who has Administrator profile?", "Compare Leads and Contacts", "How has my config grown over time?"

Recommend

"What would you clean up first?", "Any orphan fields?", "Where are the bottlenecks in my Deal pipeline?"

Run changes

"Add a multi-select field called Service Tags to Leads", "Create a module called Projects", "Delete the Agent 3 field from Leads"

Visualize

Charts (bar, pie, line, doughnut) and styled tables render inline in chat. Export conversations as Markdown.

How it works

  1. You type a question or instruction in plain English.
  2. AI Assist builds a schema context from your collected audit data - modules, fields, workflows, layouts, users, profiles, email templates, custom functions, webhooks, cross-references via the dependency graph, and pre-computed insights - and sends it to your chosen AI provider with your API key.
  3. The AI returns a structured response: a direct answer, a clarifying question (e.g., "which layout?"), a tool-call for deeper data, or a proposed configuration change.
  4. For writes, a preview modal shows the exact action before any API call fires. Nothing changes in your CRM until you click Apply.
  5. After a successful write, the local schema cache updates immediately so follow-up questions see the new state.

Setup & Configuration

ai-setup

Step 1: Enable AI Assist Mode

  1. Open CRM Explorer and go to Connection Setup.
  2. Toggle on Enable AI Assist Mode near the bottom of the connection panel.
  3. An expanded scope list appears. Add these additional scopes to your Zoho CRM connection:
Required write scopes for AI Assist:
ZohoCRM.modules.CREATE
ZohoCRM.modules.UPDATE
ZohoCRM.settings.fields.CREATE
ZohoCRM.settings.fields.UPDATE
ZohoCRM.settings.fields.DELETE

These are opt-in. Users who only want the audit don't need them. After adding the scopes, re-authorise the connection.

Step 2: Choose a provider

AI Assist supports three AI providers. You bring your own API key - it is stored only in your browser's localStorage and is never sent to Aaxonix servers.

Claude (Anthropic)

Recommended default. Strong reasoning, good with structured JSON output, and prompt-cache aware. Get a key at console.anthropic.com.

OpenAI (GPT)

Works well with the default prompt. Configure a model like gpt-4o-mini for speed or gpt-4o for depth. Get a key at platform.openai.com.

Google Gemini

Fastest and lowest cost. Good for high-volume exploration. Default model gemini-2.0-flash. Get a key at aistudio.google.com.

Step 3: Add your API key

  1. Click the AI button in the top bar (visible only when AI Assist Mode is enabled).
  2. Pick your provider from the dropdown.
  3. Paste your API key.
  4. Optional: set a specific model. Leave blank to use the default.
  5. Click Test to verify the key works, then Save.
  6. Open the AI Assist view from the sidebar to start chatting.

Privacy & data handling

Your API key is stored in your browser's localStorage only. CRM metadata (module names, field labels, workflow names, user names, etc.) is sent to your chosen AI provider as part of the prompt context. Record data is never sent. Aaxonix servers only proxy the request to the provider; no data is logged or retained on our side.

Capabilities

ai-capabilities

Exploration & analysis

  • Summaries: "Summarize my Leads module", "What modules do I have?", "What's in my Deal pipeline?"
  • Specific lookups: "Which fields are on the Standard layout?", "What are the Lead Status picklist values?", "Who has the Administrator profile?"
  • Cross-references: "Where is the Status field used?", "Which workflows reference the Account lookup?", "What breaks if I delete the Lead Source field?"
  • Counts and comparisons: "How many custom fields in Deals?", "Compare Leads and Contacts", "Show field count per module as a chart"
  • Health: "What would you clean up first?", "Any orphan fields?", "Which workflows are inactive?", "Show configuration maturity score"
  • Temporal: "Show configuration growth over time", "When were these fields added?", "User growth by month"

Configuration changes

Every change is previewed in a modal before it runs. You see the exact action, target module, and payload. Nothing happens until you click Apply.

  • Create module: "Create a module called Projects with singular label Project"
  • Create single field: "Add a text field called Client Name to Leads", "Add a multi-select field called Service Tags to Leads with options CRM Setup, Training, Support"
  • Create multiple fields: "Add 3 fields to Deals: Close Probability (integer), Discount Percent (decimal), Proposal Link (website)"
  • Delete a field: "Delete the Agent 3 field from Leads"
  • Delete multiple fields: "Delete the Agent 3, Agent 4, and Agent 5 fields from Leads"

Field types supported

AI Assist normalizes whatever data type you describe into Zoho's expected API values:

text, textarea, integer, bigint, decimal, double, currency, percent,
date, datetime, boolean, picklist, multiselectpicklist,
email, phone, website, lookup, autonumber

Type-specific defaults (length, decimal_place, picklist values) are added automatically. For picklists and multi-selects, include the options in your prompt: "add a picklist field Priority with options High, Medium, Low".

Visualizations

When the answer is quantitative, the AI returns a chart alongside the text explanation. When listing items with multiple attributes (e.g., users with their profile, role, and status), it returns a styled table. Charts and tables render inline in the chat.

Charts

Bar, pie, doughnut, line. Single-series or multi-series with a 10-color palette. Powered by Chart.js.

Tables

Headers + rows. Use for lists of items with multiple attributes. Hover rows to highlight.

Export

The Export button on the chat toolbar downloads the entire conversation (including tables and chart data summaries) as a Markdown file.

Multi-step reasoning (tool calling)

For complex questions where the default schema context isn't enough, AI Assist can request specific deeper data before answering. You'll see a "Fetching deeper data..." indicator in the chat when this happens.

module_detail

Full field list for a specific module.

workflow_actions

Full instant_actions and scheduled_actions for a workflow.

cross_ref

Every reference to a field, module, or workflow from the dependency graph.

picklist_values

Complete picklist values with display, actual, sequence, and color.

layout_detail

Full section structure of a layout with fields per section.

blueprint_detail

State transitions with from/to states and criteria.

Tool calls are hard-capped at 3 loops and 15 queries total per question to prevent runaway costs.

Self-healing writes

When Zoho rejects a write with a fixable error (INVALID_DATA, MANDATORY_NOT_FOUND, DUPLICATE_DATA, etc.), AI Assist automatically feeds the error back to the AI and asks for a corrected plan. Up to 2 retries per write. The retry plan is shown in chat before it runs so you can see what changed.

Example: end-to-end flow

User: "Add a multi-select field called Service Tags to Leads with options CRM Setup, Training, Support, Migration."

AI Assist: Detects Leads has 2 layouts (Standard, Zoho Leads). Asks: Which layout should Service Tags be added to? with the AI's suggestion highlighted.

User clicks: Standard.

Preview modal shows: Action = Create Field, Module = Leads, Label = Service Tags, Type = multiselectpicklist, Options = CRM Setup, Training, Support, Migration, Layout = Standard.

User clicks Apply.

Result: Field is created in Zoho CRM. Response message confirms success and notes the manual step for dragging the field onto the layout (the Zoho Widget SDK cannot modify layouts directly). The local schema cache is updated immediately, so a follow-up "delete Service Tags" works without refreshing.

Safety & Limitations

ai-safety

Safety guardrails

  • Preview before write. Every create or delete operation shows a modal with the exact action. No API call fires until you click Apply.
  • Pre-flight duplicate check. Before creating a field, AI Assist queries the live field list to catch duplicates and returns a clear message instead of a generic Zoho error.
  • Scope gating. AI Assist Mode is off by default. Write scopes are only added to your connection when you opt in.
  • Loop protection. Tool-call loops are capped at 3 iterations and 15 total queries. Write retries are capped at 2. The AI cannot hang or ring up unlimited costs.
  • No record data sent. Only metadata (module names, field labels, workflow names, user names, etc.) is sent to the AI provider. Lead, Contact, Deal, and other record data is never part of the context.
  • Change log. Every AI-driven write is logged to localStorage with timestamp, action, and status. View the last 10 entries in the Recent Changes panel at the top of the AI view.

Known limitations

Layout auto-placement is not available. After AI Assist creates a field, the field exists in your module but does not automatically appear on a page layout. This is a Zoho Widget SDK limitation: ZOHO.CRM.CONNECTION.invoke does not honour method: 'PUT', so the PUT /settings/layouts endpoint cannot be called from within a widget. AI Assist shows a clear manual step: Setup → Modules & Fields → [Module] → Layouts → [Layout] → drag [Field] from Available Fields.

  • No undo from inside the widget. Deletes and creates are applied directly in Zoho and cannot be rolled back from the AI. Use the Zoho CRM recycle bin for accidental field deletes.
  • No record-level operations. AI Assist works with metadata only (modules, fields, workflows, etc.). It does not create, update, or delete Leads, Contacts, Deals, or any record data.
  • Schema freshness depends on collection. Answers are grounded in the last audit collection. If you changed the Zoho config outside AI Assist, click Refresh Now at the top of the widget to re-collect and keep answers accurate.
  • Workflow/blueprint creation not supported yet. AI Assist can create modules and fields today. Full workflow, blueprint, and custom function generation is on the roadmap.

Troubleshooting

"No CRM connection configured"

Open Connection Setup from the top bar, enter your connection link name (default crmauditconnector), and re-authorise. Make sure AI Assist Mode is enabled and the write scopes are added.

"INVALID_REQUEST_METHOD" on a delete

Indicates the connection is missing a required DELETE scope. Add ZohoCRM.settings.fields.DELETE and re-authorise.

"DUPLICATE_DATA" but I don't see the field

The audit cache is stale. Click Refresh Now at the top of the widget to re-collect and check again. Zoho considers label matches (even case-insensitive) as duplicates.

Chat becomes blank mid-conversation

Should not happen in the current build. If it does, hit Clear on the chat toolbar and retry. Open DevTools (Cmd+Opt+I) and share the [AI-*] console logs for diagnosis.

AI says "cannot access" data that exists

Some data (e.g., creation timestamps on certain entity types) is stripped during audit collection. Refresh the audit and try again. If the data is genuinely unavailable, the AI will now say so and suggest alternatives instead of making things up.

Troubleshooting

Most issues are related to the OAuth connection or browser cache. Work through these in order before raising a support request.

Widget shows "Connection not found"

The OAuth connection was not created with the exact name crmauditconnector. Go to Settings → Connections, find your connection, and confirm the link name matches exactly. Alternatively, click the gear icon in CRM Explorer's top bar to enter your custom connection name.

Data seems outdated

CRM Explorer caches data in session storage. Click the Refresh button in the top bar to force a fresh data collection from Zoho's APIs.

Some modules missing from Entity Explorer

Your OAuth connection may be missing a required scope. Re-open the connection in Settings → Connections and verify all 9 scopes from the Connection Setup section are ticked.

Export - Standalone HTML is empty

This export requires data to be loaded first. If you're in cache mode, click Refresh Now on the cache banner before exporting.

Frequently Asked Questions

Does CRM Explorer store my CRM data externally?

No. All data is fetched live from Zoho's APIs via OAuth and stored only in your browser's session storage. No data is sent to Aaxonix servers.

Which Zoho CRM editions are supported?

CRM Explorer works with Professional, Enterprise, and Ultimate editions. Some modules (Blueprints, Scoring Rules) require Enterprise or above.

Can multiple users use CRM Explorer simultaneously?

Yes. Each user installs the widget and sets up their own OAuth connection. There's no shared state between users.

How often should I run a full audit?

For active orgs, monthly. For orgs undergoing major changes (new module, new team, integration project), run an audit before and after the change.

Is the widget compatible with all browsers?

CRM Explorer works in Chrome, Firefox, and Edge. Safari is supported but some D3 visualisations may render slightly differently.

How do I update CRM Explorer?

Upload the new widget package in Setup → Developer Space → Widgets and replace the existing widget. Your OAuth connection persists between updates.