Beam Help
Get help now

Error code · Zoho CRM

Cdata Looker Studio Connector Error with Zoho CRM

This error appears when the CData Looker Studio connector fails to complete an authenticated or authorized call into Zoho CRM — Looker Studio shows a connector-level failure rather than an application error. The connector cannot read the CRM data it expects, so dashboards stop populating.


What it means

The CData connector could not complete an OAuth-authenticated request to the Zoho CRM API or the connector lacks the CRM module access it needs to run queries; the failure sits between the connector and Zoho’s CRM endpoints rather than inside Looker Studio itself [1][4]. Many integration failures of this type trace back to authentication, permission, or integration setup problems inside the CRM account [6].


Common causes

  • Expired or revoked OAuth token for the CData connector — the connector loses its authorized session and requests fail [1][4].
  • Connector lacks required CRM permissions or an administrator did not approve the marketplace/extension integration — marketplace apps and connectors must be installed/approved by an admin [6].
  • Connector configuration or credentials point to the wrong CRM account or use the wrong client credentials (misconfigured connector settings) [1].
  • Out-of-date CData connector version or a transient CData service bug preventing proper API calls [1].

How to fix it

  1. Re-authenticate the connector: open the CData connector in Looker Studio, remove the existing Zoho CRM connection, then re-authorize using the correct Zoho account. Verify the OAuth consent screen completes without error [1][4].
  2. Confirm an admin installed/approved the integration: in Zoho CRM sign in as an administrator and go to Setup > Marketplace (Installed Apps) to confirm the connector/extension is installed and allowed for users who need it [6].
  3. Verify connector credentials and account match: check the CData connector settings for the Zoho account/email used, and confirm the same CRM account is used when testing API calls (avoid using a different user or demo org) [1].
  4. Run a direct API check: use Postman or Zoho’s API console to make a simple CRM API or COQL query (for example, a basic select) with the same OAuth token to confirm the CRM API responds and the token scopes include read access to the target modules [6].
  5. Update the connector and collect logs: ensure the CData connector is on the latest build, capture connector logs or the Looker Studio connector error details, then retry. If the error persists, share the logs with CData support and include the exact error text and a timestamp [1].

When to escalate

If re-authentication, admin approval, and credential checks do not restore connectivity, escalate to CData support first with connector logs and steps you already ran; if CData determines the connector issued valid CRM calls but Zoho rejected them, open a ticket with Zoho Support including the same logs and a sample failing API request/response [1][7].

Originally asked in the Zoho community. See the original question →

Sources cited

  1. [1] Cdata - Looker Studio Community Connector Error to Zoho CRM
  2. [2] ZMA shows as already connected to Zoho CRM, but integration not working
  3. [3] Zoho Community | Connect, network, and share on Zoho Forums
  4. [4] Zoho Community | Connect, network, and share on Zoho Forums
  5. [5] Troubleshooting IMAP & POP3 Configuration
  6. [6] CRM | Troubleshooting | Knowledge Base
  7. [7] Troubleshooting integration of Zoho Advanced Analytics with Zoho CRM
  8. [8] Updating your Helpdesk Contacts and Accounts from Zoho CRM - Online Help | Zoho Desk
Cdata Looker Studio Zoho CRM Error | Beam Help