Overview
This article catalogs the error messages a subscriber can encounter when synchronizing data between iPaaS.com and Zoho CRM. Each error carries a stable code in the form ZCRM-{CATEGORY}-{NUMBER} (for example, ZCRM-VALD-1001). The code is shown at the start of the message in the error log and is the fastest way to find an entry here — use your browser's Find (Ctrl+F / ⌘F) to search this page for the code. Each entry gives the message as it appears in the 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.
Some resolutions below refer to your Managed Integration Service Provider (MiSP) — the party that manages your iPaaS.com integration on your behalf, including your mappings, connection credentials, and configuration. Where a resolution calls for a change you do not manage yourself, raise it with your MiSP first; if they cannot resolve it, contact iPaaS.com Support.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Connection and Authentication
Custom Fields (Contact, Sales Order, and Product transfers)
Sales Order Transfers
Contact Transfers
Zoho CRM API and Rate Limits
Manual Sync
Error Collection
Connection and Authentication
Missing connection credentials
ZCRM-AUTH-1001 - Unable to connect to Zoho CRM: the Client ID 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. The same code is raised for a missing Client Secret, with the wording changed accordingly.
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
ZCRM-AUTH-1002 - Unable to authorize the Zoho CRM connection: the Client ID is not set in the subscription settings.
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 — Client ID, Client Secret, or Redirect URL — is missing, or when Zoho CRM does not return a usable token for the code supplied. The wording in the message names which of these conditions applied.
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, raise it with your MiSP; if they cannot resolve it, 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
ZCRM-VALD-1001 - 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
ZCRM-VALD-1002 - 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
Order has no line items
ZCRM-VALD-1004 - The order has no line items, so it cannot be transferred to Zoho CRM.
Description: Applies to Add/Update Zoho CRM Sales Order FROM iPaaS.com. A Zoho CRM Sales Order must contain at least one line item. When the order being transferred has no lines, the integration cannot build a valid Sales Order and the transfer fails.
Resolution: Confirm the source transaction in iPaaS.com has at least one line item, and that the mapping populates the order's lines. Correct the source data or the mapping so the order carries its lines, then re-run the transfer.
Product not found for a line
ZCRM-NFND-1001 - 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.
Contact Transfers
Contact not found
ZCRM-NFND-1002 - The contact with ID '{id}' was not found in Zoho CRM.
Description: Applies to inbound contact transfers (Add/Update Zoho CRM Contact TO iPaaS.com). When a contact is synced by its Zoho CRM id — for example a Manual Sync, or a webhook-triggered transfer — the integration fetches that contact from Zoho CRM. If no contact exists for the id supplied, the record cannot be retrieved and the transfer fails.
Resolution: Confirm the Zoho CRM contact id is correct and that the contact still exists in Zoho CRM (it may have been deleted or merged). For a Manual Sync, re-enter the correct Zoho CRM contact id; for a webhook-triggered transfer, confirm the workflow rule is sending the id of a contact that exists. Then retry.
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, so the same code covers a rejected request, a rate-limit rejection, and a failure to reach Zoho CRM.
Zoho CRM API call failed
ZCRM-EXTN-1001 - Error calling Zoho CRM: {message returned by Zoho CRM} (HTTP Code: {code}).
Description: The call to Zoho CRM did not succeed. The bracketed portion is Zoho CRM's own message and code. There are three common shapes:
Request rejected: Zoho CRM refused the request, usually a validation or permission failure (a required Zoho CRM field missing, a value in the wrong format, a lookup id that does not resolve, or a mandatory-field/permission rejection).
Rate limit reached (HTTP Code: 429): 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. Order transfers are most exposed, because each order makes one call per line to resolve products.
Zoho CRM could not be reached: the request did not complete because of a network interruption, a timeout, or Zoho CRM being temporarily unavailable; the underlying transport message is recorded.
Resolution: Read the Zoho CRM message in the log entry — it names the field or condition that failed. For a rejected request, 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. For a rate-limit rejection, re-run the affected transfers once the allowance window has reset, and to avoid recurrence lengthen the poll interval, stagger bulk loads rather than running them in one burst, and use the supported bulk-sync approach in the Zoho CRM Known Limitations article; if limits are reached routinely, consider a higher Zoho CRM edition or add-on credits. For a could-not-be-reached failure, retry — transient network and availability issues usually clear on their own. If a rejected-request message is unclear or points at no subscriber-configurable cause, raise it with your MiSP; if they cannot resolve it, contact iPaaS.com Support at support@ipaas.com.
Manual Sync
Invalid record ID format
ZCRM-VALD-1003 - The record ID '{Id}' is not in the expected format for this transfer.
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.