> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/integrations/crm/zoho/setup-guide.md). # Zoho setup guide Mobly's Zoho CRM integration syncs every captured-and-enriched lead into your Zoho Leads (and optionally Contacts and Accounts), with field mapping, qualifier mapping, and per-event campaign sync. Connection runs through Mobly's new integration platform. ## What you can do * **Sync leads to Zoho Leads** — every Mobly-captured lead becomes a Lead in Zoho, matched by Lead ID first, then Email * **Sync to Contacts and Accounts** — if configured, Mobly can write to Contacts (with linked Accounts) instead of or in addition to Leads * **Map any Mobly field to any Zoho field** — standard or custom, across modules * **Use Zoho picklists** for qualifier mapping — Zoho enforces picklist values, so each Mobly qualifier value needs a matching option (or map to an open-text field) * **Log lead activities as Zoho Notes** — outreach actions in Mobly (Pulse emails, calls, meetings, LinkedIn touches, SMS, manual notes) appear on the matching Lead as Notes. The Note title is the activity type; the body is whatever notes were attached to the activity in Mobly. See [Finding Mobly activities in your CRM](/help-center/integrations/crm/finding-activities-in-your-crm.md) for the per-action breakdown * **Toggle Automatic vs Manual sync** — see [Sync modes](/help-center/integrations/crm/sync-modes.md) ## What's not supported (yet) * **Custom modules beyond Leads/Contacts/Accounts** — Mobly maps to standard modules. Custom modules can be added if the new Mapping tab surfaces them, but most setups stick with standard * **Deal sync** — Mobly doesn't create or update Deals * **Workflow Rule automation** — Mobly writes data; downstream automation (alerts, conversions, assignment rules) needs to be built in Zoho's Workflow Rules keyed off Mobly-touched fields * **Multi-integration** — running Zoho alongside another CRM in the same Mobly org isn't supported today (one CRM per org) ## Before you connect You'll need: * A **Zoho CRM user** with: * **Administrator** or **Developer** profile (or a custom profile with create/edit access to Leads, Contacts, Accounts, and any custom modules you've mapped) * Read access to all fields in the planned mapping (Field-Level Permissions on the user's profile) * A **Mobly admin account** to view and configure Integrations Zoho's profile-based permissions can hide fields from specific users. Confirm the connecting user can see every field you plan to map under **Setup → Users and Control → Profiles**. ## Connect the integration 1. Go to **Integrations → Zoho** in Mobly 2. Click **Connect** on the Connect tab 3. Sign in to Zoho in the OAuth window and approve the permissions Mobly requests Detailed walkthrough: see [Connecting your CRM](/help-center/integrations/crm/connecting.md). ## Configure data flow Work through the tabs in order: 1. [**Mapping**](/help-center/integrations/crm/field-mapping.md) — match Mobly fields to Zoho fields. Persona section maps to Lead (or Contact, depending on your configuration); Company section maps to Account. 2. [**Qualifiers**](/help-center/integrations/crm/qualifiers.md) — define qualifiers and map values to Zoho picklist options. 3. [**Campaigns**](/help-center/integrations/crm/campaign-mapping.md) — link Mobly events to Zoho Campaigns. 4. [**Sync mode**](/help-center/integrations/crm/sync-modes.md) — Automatic by default; switch to Manual on the Connect tab if needed. ## Zoho-specific configuration tips **Module-based architecture.** Zoho organizes records as Modules (Leads, Contacts, Accounts, Deals, plus customs). Mobly's Persona section maps to one module — typically Leads — and the Company section maps to Accounts. If you want to write to Contacts instead of Leads, that's set during integration configuration. **Field types.** Match Mobly's TEXT/EMAIL/URL/PHONE badges to Zoho's field types (Single Line, Email, URL, Phone). Misaligned types surface as `DATA_FORMAT_VALIDATION` errors in Reconciliation. **Picklist enforcement.** Zoho picklists strictly enforce their option list — sending an unrecognized value triggers `DATA_VALUE_VALIDATION` errors. Either pre-add every Mobly qualifier value to the matching Zoho picklist, or map Mobly to an open-text field. **Long values.** Zoho single-line text fields default to 255 characters. For longer Mobly fields (notes, descriptions), use **Multi-line** or **Large** text types under **Setup → Customization → Modules and Fields → \[module] → \[field]**. **Layouts and Field Visibility.** Zoho has Layouts that can hide fields from specific users or roles. The connecting user's Layout must include every field in the Mobly mapping, or Mobly will silently skip those fields. **Custom modules.** If you've mapped Mobly to a custom module in Zoho, every change to the module's structure (field rename, field deletion, new required field) can break the mapping. Plan structure changes carefully and revisit Mobly's Mapping tab afterward. ## Troubleshooting If a synced lead shows up in **Reconciliation → Failed**, see [Fixing Zoho sync errors](/help-center/integrations/crm/zoho/troubleshooting.md) — there's a section per error category with the fix. ## Related articles * [Connecting your CRM](/help-center/integrations/crm/connecting.md) * [Sync modes](/help-center/integrations/crm/sync-modes.md) * [Field mapping](/help-center/integrations/crm/field-mapping.md) * [Qualifiers](/help-center/integrations/crm/qualifiers.md) * [Mapping campaign fields](/help-center/integrations/crm/campaign-mapping.md) * [Reconciliation](/help-center/integrations/crm/reconciliation.md) * [Fixing Zoho sync errors](/help-center/integrations/crm/zoho/troubleshooting.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.getmobly.com/help-center/integrations/crm/zoho/setup-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.