Overview
This article catalogs the error messages a subscriber can encounter when synchronizing data between iPaaS.com and Zoho CRM, grouped by the flow that produces them. Each entry gives the message as it appears in the iPaaS.com error log, what causes it, and how to resolve it. Errors appear under Dashboard / Integration Monitoring / Error Logs.
Some integration behaviours do not raise an error and so are not listed here — for example, a deletion in one system is not propagated to the other. Those are described in the Zoho CRM Known Limitations article and in the individual Mapping Documentation articles.
Supported Flows
Connection and Authentication
Custom Fields (Contact, Sales Order, and Product transfers)
Sales Order Transfers
Zoho CRM API and Rate Limits
Manual Sync
Connection and Authentication
Missing connection credentials
Unable to obtain a Zoho CRM access token because the Client ID or Client Secret is not set in the subscription settings.
Description: The integration authenticates to Zoho CRM with an OAuth Client ID and Client Secret held in the subscription settings. If either is blank when the integration tries to obtain or refresh an access token, the connection cannot be established and the transfer fails.
Resolution: Open the subscription settings for the Zoho CRM integration and confirm the Client_Id and Client_Secret values are present and correct, then retry. See the Zoho CRM Connections and Settings article for where these come from in Zoho CRM.
OAuth authorization could not be completed
The Zoho CRM authorization could not be completed. A required value (Client ID, Client Secret, or Redirect URL) is missing, or the authorization code could not be exchanged for a token.
Description: This occurs during the initial connection of the integration to Zoho CRM, when the authorization step exchanges a temporary code for a lasting token. It fires when one of the required values is missing, or when Zoho CRM does not return a usable token for the code supplied.
Resolution: Confirm the Client ID, Client Secret, and Redirect URL are configured as described in the Zoho CRM Installation Instructions, then re-run the connection. If the values are correct and the error persists, contact iPaaS.com Support at support@ipaas.com.
Custom Fields (Contact, Sales Order, and Product transfers)
These errors apply to the outbound collections that write custom fields to Zoho CRM — Add/Update Zoho CRM Contact FROM iPaaS.com, Add/Update Zoho CRM Sales Order FROM iPaaS.com, and Add/Update Zoho CRM Product FROM iPaaS.com. The message names the Zoho CRM module involved (Contacts, Sales_Orders, or Products).
Custom field not found
No field exists in Zoho CRM by this field label or API name: {field} in the {module} module.
Description: A custom field mapped on the collection could not be matched to any field in the named Zoho CRM module, by either its field label or its API name. This is raised only when the Raise Custom Field Not Found Exception subscription setting is set to True; when it is False, the value is sent anyway and Zoho CRM ignores the unrecognised field silently.
Resolution: Confirm the custom field exists in Zoho CRM under Settings → Customization → Modules and Fields → {module} → Fields, and that the iPaaS.com subscription custom field is named to match the Zoho CRM field label or API name exactly (API names remove spaces and special characters — a label of CF Multi-Select 2 becomes CF_Multi_Select_2). Correct the name, or create the field in Zoho CRM, then retry.
Custom field data type mismatch
Invalid data for custom field '{field}'. Expected datatype '{type}', but received value '{value}'.
Description: A value mapped to a Zoho CRM custom field does not match the field's data type — most often a non-true/false value sent to a checkbox (boolean) field, or a non-numeric value sent to a number field.
Resolution: Either correct the source data in iPaaS.com so it matches the Zoho CRM field's type, or define the matching iPaaS.com subscription custom field with the correct data type (for example, define a boolean field for a Zoho CRM checkbox). Validate the mapping in a staging environment before relying on it in production.
Sales Order Transfers
Product not found for a line
The product with SKU '{sku}' was not found in Zoho CRM.
Description: Applies to Add/Update Zoho CRM Sales Order FROM iPaaS.com. Before writing an order, the integration matches every line's SKU to a Zoho CRM product code. If any one line's SKU has no matching product, the entire order fails — no partial order is created.
Resolution: Transfer the missing product to Zoho CRM first using Add/Update Zoho CRM Product FROM iPaaS.com, confirming the product's code matches the SKU on the iPaaS.com transaction line, then re-run the order. Because one unmatched SKU stops the whole order, check every line if the failing one is not obvious.
Zoho CRM API and Rate Limits
These errors originate at Zoho CRM and reach the error log with the message Zoho CRM returned. They can occur on any flow.
Zoho CRM rejected the request
Error calling Zoho CRM: {message returned by Zoho CRM} (HTTP Code: {code}).
Description: Zoho CRM refused the request and returned an error. The bracketed portion is Zoho CRM's own message and code — common causes are a validation failure (a required Zoho CRM field missing, a value in the wrong format, a lookup id that does not resolve) and a mandatory-field or permission rejection. The transfer stops and the message is recorded in the error log.
Resolution: Read the Zoho CRM message in the log entry — it names the field or condition that failed. Correct the mapped data or the Zoho CRM configuration it points to (for example, create a referenced tax name, supply a valid lookup id, or populate a field Zoho CRM requires), then retry. If the message is unclear or points at no subscriber-configurable cause, contact iPaaS.com Support at support@ipaas.com.
Zoho CRM API limit reached
Error calling Zoho CRM: too many requests (HTTP Code: 429).
Description: Zoho CRM meters API usage against a rolling 24-hour credit allowance and caps how many calls an application may have in flight at once, both varying by Zoho CRM edition. When the allowance or the concurrency cap is reached, Zoho CRM rejects further calls. The transfer is not automatically retried or rescheduled — it fails and is recorded in the error log. Order transfers are most exposed, because each order makes one call per line to resolve products.
Resolution: Re-run the affected transfers once the allowance window has reset. To avoid the limit, lengthen the poll interval, stagger bulk loads rather than running them in one burst, and for large initial loads use the supported bulk-sync approach described in the Zoho CRM Known Limitations article. If limits are reached routinely, consider a higher Zoho CRM edition or add-on credits.
Zoho CRM could not be reached
Error calling Zoho CRM: {transport error message}.
Description: The request to Zoho CRM did not complete — a network interruption, a timeout, or Zoho CRM being temporarily unavailable. The underlying transport message is recorded.
Resolution: Retry the transfer; transient network and availability issues usually clear on their own. If the failures persist, confirm Zoho CRM is reachable and contact iPaaS.com Support at support@ipaas.com if needed.
Manual Sync
Invalid record ID format
The record ID entered for Manual Sync is not in the expected format.
Description: A Manual Sync was started with a record ID that does not match the format the collection expects — for example a non-numeric value where a numeric id is required. The transfer cannot start because the record cannot be identified.
Resolution: Enter the id in the format documented for the collection: the iPaaS.com Customer / Transaction / Product ID for the FROM iPaaS.com collections, and the Zoho CRM contact id for the Contact TO iPaaS.com collection. See the ID Format section of the relevant Mapping Documentation article for the exact shape and an example.