Zoho CRM integration: sync form submissions to Leads or Contacts
Connect Zoho CRM to Panther Hook, choose Leads or Contacts, map fields and track delivery results for approved form submissions.
What the Zoho CRM integration does
Panther Hook sends eligible approved production submissions to your connected Zoho CRM as Leads or Contacts. It creates or updates a record using its email address, without creating a separate queue or changing your other integration destinations.
Choose Leads or Contacts for each form destination. Missing optional mapped values are skipped. Required Zoho fields and duplicate policies can differ across Zoho organizations and layouts.
Connection availability depends on your environment and Zoho OAuth application configuration. A connection test checks access but does not create a CRM record.
Connect Zoho CRM
Open your formsStep 1: Select your form
Sign in to Panther Hook, choose the intended workspace, open Forms, select your form and open its Integrations tab. Choose Zoho CRM from the provider list.
Step 2: Authorize your Zoho account
A workspace Owner or Admin clicks Connect Zoho CRM and completes the secure authorization in the Zoho browser window. Zoho may route authorization to your account data center (for example, EU or US). Return to Panther Hook and verify the connection status.
Panther Hook stores the resulting OAuth tokens securely. Never send refresh tokens, client secrets or authorization codes to an AI assistant or paste them into a destination mapping.
Step 3: Choose Leads or Contacts and map fields
Choose Zoho Leads or Contacts, then map Panther Hook form sources to Zoho properties. Email is required for record matching. First name, last name, phone and company are available as standard mappings. Writable custom fields can be discovered for your connected Zoho module.
Zoho requires Last Name, and also Company for Leads. Map these fields to real submitted values: records missing mandatory properties are rejected rather than filled with fabricated company or person names. Save and enable the integration only after reviewing its fields.
Step 4: Verify the actual delivery
The Test connection control checks Zoho OAuth access but does not create a lead or contact. For a full end-to-end test, submit a clearly synthetic approved production-mode form entry and verify the resulting record inside the selected Zoho CRM module.
Repeat with the same email and an updated field to check that Zoho updates the existing record instead of creating another. Inspect Panther Hook Integration delivery history for the exact delivery status, errors and retry attempts. Remove only your synthetic CRM test records afterward.
Field mapping example
This is Panther Hook destination configuration, not a raw Zoho API request. Choose Contacts instead of Leads if you want Contacts synchronized. Map writable custom Zoho property API names using the fields returned by your authorized account.
Dashboard test submissions do not trigger production CRM delivery. To test end-to-end, use a safe synthetic approved production-mode submission and a CRM test account.
{
"module": "Leads",
"mapping": {
"email": "fields.email",
"firstname": "fields.first_name",
"lastname": "fields.last_name",
"company": "fields.company"
}
}Delivery errors, retries and disconnecting
- If Connect is unavailable, check your workspace permissions and whether Zoho CRM is enabled in Panther Hook.
- If a Zoho record does not appear, verify the destination is enabled, the submission was approved, mapped email is valid, and account permissions cover the selected Leads or Contacts module.
- Zoho layout-required fields, duplicate checks or custom property validation can reject a delivery. Examine sanitized error and attempts in the integration history.
- Expired OAuth access tokens are refreshed automatically. Temporary failures and rate limits use the existing integration retry mechanism. A successful connection test does not prove record delivery.
- Disconnecting Zoho disables that workspace’s Zoho destinations and suppresses pending deliveries. To connect a different Zoho CRM organization, disconnect first.
- Zoho has region-specific account and API endpoints. Authorization can redirect to the correct regional data center; the connection remains associated with that region.
- Through Panther Hook MCP and compatible plugins, you can discover the CRM connection and fields, inspect mappings, and propose changes subject to human approval. Browser OAuth is required for authorization.
Official Zoho developer documentation
Zoho documents the OAuth flow, data centers, Leads/Contacts upsert behavior, field metadata and API permissions. Review them if your organization uses custom layouts or regional data centers.
Zoho CRM API v8 reference