Start with Activity > Prospecting when an export fails. There you can see records created, updated, conflicts and errors.
Zoho shows as connected, but I see no records
Check:
That you connected the right organization.
That you selected the right organization and environment in Zoho.
That the Integration user can see Contacts and Accounts.
That their profile can read the fields being used.
That the Custom View is shared with that user.
That Zoho has not revoked the token.
A permission error can appear as an empty list on some screens. If you expected results, do not assume the organization is empty.
Authentication has expired
If the card shows Reconnect:
Click Reconnect.
Sign in with the same user.
Select the right organization.
Accept the permissions.
Reopen Configure.
If the problem persists, use Disable, revoke access in Zoho, and connect again.
A field is missing from Field Mapping
Check that:
The field belongs to the right module.
The Integration user can see it.
The field is still active.
You have opened the right tab: Contacts, Leads or Companies.
Reopen Zoho Setup after creating or changing the field. If it still does not appear, reconnect.
A warning or an x blocks the mapping
The blue check marks the selected option. It does not guarantee compatibility.
A yellow warning usually flags a type difference or a picklist option. A red x means the option is not available in that selector.
Test the mapping with one record. Enginy does not currently use all the metadata Zoho exposes to reliably detect every read-only field or special type.
Zoho rejects a required field
Zoho requires at least Last_Name for Contacts and Leads, and Account_Name for Accounts.
You must also fill in the custom required fields defined in the layout. Add the value in Enginy, configure a Fixed value, or adjust the mapping before repeating the export.
Zoho can return errors such as MANDATORY_NOT_FOUND or INVALID_DATA.
See the record creation documentation.
A picklist rejects the value
The value must match an option Zoho accepts.
Check that the option is still active.
Reopen Configure.
Select a current option.
Click Save Changes.
Test one record.
Enginy does not create or rename Zoho options. If you use an AI Variable or free text, confirm that the result matches an allowed option exactly.
A Zoho List does not appear
A Zoho List is a Custom View. Check that:
It belongs to Contacts or Accounts.
The Integration user can see it.
It has at least one record.
It is among the recently used views.
Enginy calculates the count for the five most recent Custom Views. Views without a count are hidden in the selector. Open the view in Zoho, come back to Enginy and refresh.
Leads Custom Views are not shown in the current imports.
I cannot import Leads
That is expected. Enginy imports people from Contacts and Companies from Accounts.
You can export a person as a Lead, but you cannot import records from the Leads module.
I get a 429 or an API limit error
Zoho limits credits and concurrency by plan. Enginy temporarily retries some 429 responses.
If the error persists:
Wait a few minutes.
Avoid running several large imports or exports at once.
Review your consumption in the Zoho API Dashboard.
Repeat the operation.
See Zoho's API limits.
The Owner is wrong
Review Identities Mapping, Users Mapping, Default CRM owner, the Owner chosen in Export to CRM, and that the Zoho user is still active.
User Mapping decides the Owner, but it does not change the Integration user or their permissions.
I disconnected Zoho, but Enginy is still authorized
Disable only removes the credential stored in Enginy. Also revoke Enginy from Authorized Websites in Zoho Accounts.
My account uses Australia, China, or Canada
The current connection has limitations with those data centers. Do not connect a production organization without confirming compatibility with Support first.
What to send to Support
Include:
Your Enginy workspace.
The Zoho organization and region.
The module affected.
The operation you were running.
The approximate time.
The error message or a screenshot.
A link to the report, if there is one.
Do not send passwords, access tokens or refresh tokens.