Zoho CRM Integration¶

The Zoho CRM integration lets your team send scheduled lead deliveries from Carrier Leads Pipeline into a Zoho CRM module, usually Leads. Deliveries use a saved filter, apply your team's suppression rules, and skip leads that were already delivered to the same Zoho destination.

Before You Start¶

You need:

A Carrier Leads Pipeline account with access to your team's delivery settings.
A Zoho CRM account that can authorize API access.
A Zoho module where lead records should be created or updated. The default module is Leads.
Writable Zoho fields for the lead information you want to send.

Delivery and billing

Zoho delivery itself does not consume credits. Credits are tied to lead unlocks, not to the act of sending a record to Zoho.

Connect Zoho CRM¶

Open Dashboard.
Go to Integrations.
Choose Zoho CRM.
Select Connect Zoho CRM.
Sign in to Zoho and approve the requested access.
After Zoho redirects back to Carrier Leads Pipeline, return to Zoho CRM Integration.

When the connection is active, the Zoho card shows Zoho CRM Connected.

Configure Field Mappings¶

Field mappings tell Carrier Leads Pipeline which Zoho fields should receive each lead field. Mappings are configured per Zoho module. For example, the Leads module can have a different mapping from a custom module.

Open Dashboard.
Go to Integrations.
Choose Zoho CRM.
In Zoho Module, enter the module API name. Use Leads unless your team has a custom destination module.
Select Refresh to load the latest fields from Zoho.
For each Carrier field, choose the matching Zoho field.
Select Save Mapping.

Saving creates a mapping version. Future Zoho delivery schedules use the saved version so that delivery behavior is explainable later, even if mappings change.

Required Mappings¶

At minimum, the following Carrier fields must be mapped:

Carrier field	Why it is required
Company name	Zoho lead records require a company-style identity.
Last name	Zoho lead records usually require `Last_Name`. Carrier Leads Pipeline derives this from the carrier legal name when possible.
Canonical lead key	Used for Zoho upsert duplicate checking and delivery idempotency.

Carrier Leads Pipeline also checks Zoho field metadata and reports any Zoho fields that are marked mandatory by the module metadata.

Layout-specific Zoho requirements

Zoho's field metadata may not show every layout-specific rule. A delivery can still fail if a Zoho layout, workflow, validation rule, or picklist restriction rejects a record. If that happens, update the mapping or Zoho module rules, then retry delivery.

Recommended Default Mappings¶

These are the default mappings Carrier Leads Pipeline suggests when matching fields exist in Zoho:

Carrier field	Suggested Zoho API field
Company name	`Company`
Last name	`Last_Name`
First name	`First_Name`
Lead source	`Lead_Source`
Canonical lead key	`Lead_Source_CLP_Key`
Signal key	`CLP_Signal_Key`
Global lead ID	`CLP_Global_Lead_ID`
Lead type	`CLP_Lead_Type`
Event effective date	`CLP_Event_Effective_Date`
DOT number	`DOT_Number`
Docket number	`Docket_Number`
DBA name	`DBA_Name`
Phone	`Phone`
Email	`Email`
State	`State`
Country	`Country`
Carrier operation	`Carrier_Operation`
Operation classification	`Operation_Classification`
Cargo carried	`Cargo_Carried`
Safety rating	`Safety_Rating`
Insurance company	`Insurance_Company`
Insurance policy number	`Insurance_Policy_Number`
Insurance cancel effective date	`Insurance_Cancel_Effective_Date`

Your Zoho field API names may differ. Use the dropdowns in the mapping page as the source of truth.

Schedule Zoho Delivery¶

Zoho delivery starts from a saved filter.

Go to Dashboard.
Open Delivery.
Select a Saved Filter.
Set Delivery Type to Zoho CRM.
Enter the Zoho module API name, such as Leads.
Choose a frequency:
Run once now queues one delivery job.
Daily creates a recurring schedule.
Weekly creates a recurring schedule.
Choose Lookback Days.
Select Schedule Delivery.

Before the schedule is saved, Carrier Leads Pipeline validates that the selected Zoho module has a usable field mapping. If the mapping is invalid, fix it on the Zoho integration settings page and try again.

How Duplicate Handling Works¶

Carrier Leads Pipeline uses destination-scoped deduplication. A lead is considered already delivered only for the same team, Zoho connection, module, and delivery action.

If the same saved filter runs again:

Leads already sent to that Zoho destination are skipped.
Skipped duplicates are not failures.
Skipped duplicates do not consume credits.
New matching leads are sent to Zoho.

Zoho delivery uses an upsert action. The mapped canonical lead key field is used as the Zoho duplicate-check field.

Editing a Zoho Schedule¶

Open Dashboard.
Go to Delivery.
Find the schedule.
Select the edit button.
Update the saved filter, module, frequency, or lookback days.
Save the schedule.

If the module is changed, Carrier Leads Pipeline validates the mapping for the new module before saving.

Troubleshooting¶

Problem	What to check
Zoho CRM is disabled on the Delivery page	Connect Zoho CRM from Integrations first.
Mapping will not save	Make sure required Carrier fields are mapped and the selected Zoho fields are writable.
A required Zoho field is missing	Add a mapping for that Zoho field, or adjust the Zoho module/layout requirements.
Delivery fails with a Zoho validation error	Check Zoho validation rules, workflows, required layout fields, and picklist values.
Duplicate records appear in Zoho	Confirm the canonical lead key is mapped to a stable Zoho field and saved as the duplicate-check field.
Delivery sends fewer leads than expected	Review skipped duplicate counts and team suppression rules. Suppressed and already-delivered leads are not sent again.

Best Practices¶

Use the standard Leads module unless your sales workflow requires a custom module.
Keep the canonical lead key mapped to a dedicated Zoho field that users do not edit.
Use clear saved-filter names before scheduling delivery.
Refresh Zoho fields after changing fields in Zoho CRM.
Save a new mapping version after changing any field mapping.