Retrieving connectors in Zoho CRM means accessing the authentication links that allow your CRM account to communicate with third-party services — and understanding how to reference them correctly inside your Deluge functions.
Why this matters
Connectors (also called Connections) serve as the authentication bridge between Zoho CRM and external applications. When you build a function that calls an outside service, you need to know the connector's link name and its current status before you can invoke it reliably. [8] Whether you're pulling campaign data from MailChimp or querying an external REST API, the connector must be set up and retrievable before any integration code will work. [1]
> Note: Beam Help is independent expert support for Zoho — we are not official Zoho support.
---
Step-by-step
Step 1. Log in to your Zoho CRM account and navigate to Setup. From there, locate the Developer Space (or Developer Hub) section in the left-hand menu. This is where all connector and function configuration lives. [1]
Step 2. Inside the developer area, select Connections (sometimes labelled Connectors depending on your CRM version). This section lists every authentication link your organisation has already created, along with its current status. [8]
Step 3. In the Connections list, locate the connector you want to retrieve. Each entry displays three key pieces of information: the Link name, the Service name (the third-party application it authenticates against), and the Status of the connection (active or inactive). [1]
Step 4. Click on a specific connector to open its detail view. Here you will find the auto-generated code snippet that shows you exactly how to reference this connector inside a Deluge function. The Connection field in that snippet corresponds directly to the link name you saw in the list. [1]
Step 5. Copy the link name from the detail view. This string is what you will pass as the connection parameter whenever you use an Invoke URL task in a Deluge function to call the third-party service. [1]
Step 6. If you need the connector to be used as a source for the Queries feature, navigate to Setup → Developer Space → Queries, then add a new REST API source. In that form, you can specify the base URL, default parameters, headers, and — critically — select the existing connection (connector) from a dropdown to authenticate the query. [7]
Step 7. To verify the connector is working end-to-end, reference it inside a test function using the Invoke URL task. The function editor will show you the connection link name in context, and you can run a test call to confirm the third-party service responds as expected. [1]
---
Common pitfalls
- Wrong link name casing: The link name is case-sensitive when referenced in Deluge code. Copy it exactly as shown in the connector detail page — do not retype it manually. [1]
- Inactive status: If the connector's status shows as inactive or expired, the authentication token may have lapsed. You will need to re-authorise the connection before any function referencing it will succeed. [8]
- Missing trusted domains for database sources: If you are using the Queries feature with a REST API connector and the host is not in IP address format, you must add it to Trusted Domains in your CRM settings, and whitelist Zoho CRM IPs on the relay server side. Skipping this step will cause connection timeouts even when the connector itself appears active. [7]
- Connector scope vs. function scope: Connections can be invoked from functions and widgets, but the connector must have been granted the correct OAuth scopes for the third-party service at creation time. Retrieving a connector that was set up with insufficient scopes will result in authorisation errors at runtime, not at the retrieval stage. [8]
---
What to check
- Link name is exact: Confirm the link name copied from the connector detail view matches character-for-character what appears in your Deluge function's
connectionparameter. [1] - Status is active: In the Connections list, verify the connector's status column shows an active/connected state before deploying any function that depends on it. [1]
- Source is configured for Queries (if applicable): If you are using the connector as a REST API source inside the Queries feature, confirm the base URL, headers, and connection reference are all populated correctly in the source configuration. [7]