Fix Zoho CRM invalid_code Login Error - Skyvia

Zoho CRM: invalid_code Login Error

Overview

If you encounter the error "An error occurred during login operation. Error: invalid_code" while connecting to Zoho CRM in Skyvia, it means the wrong Domain is selected in your Zoho CRM connection settings.

Resolution

  1. Open your Zoho CRM connection in Skyvia.
  2. Click Edit.
  3. Select the correct Domain that matches your Zoho account region (e.g., .com, .eu, .in, .com.au, .jp).
  4. Save the connection and re-authenticate.

After updating the Domain, the connection should authenticate successfully without errors.

​

    • Related Articles

    • Zoho CRM: Inactive User Cannot Access the API Error

      Overview This error is returned by the Zoho CRM API. Skyvia connects to data sources through their APIs and is therefore subject to their features and limitations. Unfortunately, there are no additional details available beyond what the Zoho CRM API ...

    • Snowflake: invalid_grant Access Token Error

      Overview This error comes from your Snowflake connection because it has become invalid. By default, the Snowflake OAuth refresh token is valid for 90 days. Once it expires, the connection can no longer authenticate and returns the invalid_grant ...

    • Zoho CRM: You can only get the first 2000 records error for Notes

      Overview When backing up or exporting Notes from Zoho CRM through Skyvia, you may encounter the following error: You can only get the first 2000 records without using page_token param. Why This Happens The Zoho CRM API imposes the following ...

    • Google Sheets: Internal error encountered. Error code: 500

      Overview The error "Internal error encountered. Error code: 500" is returned by the Google Sheets API and is typically caused by processing a large volume of data in a single request. Resolution To resolve this issue, reduce the Batch Size value in ...

    • Salesforce Connect: Can't Sync Schema Metadata (Error Code: Null)

      Overview This error occurs because the object used in your endpoint does not have a primary key column. Salesforce requires a primary key for external objects, which is why you encounter an error when validating and syncing your External Data Source ...