Zoho CRM Connector for Informatica

In this article you will learn how to quickly and efficiently integrate Zoho CRM data in Informatica without coding. We will use high-performance Zoho CRM Connector to easily connect to Zoho CRM and then access the data inside Informatica.

Zoho CRM Connector can be used to integrate Zoho CRM API in your App / BI Tools. You can exchange data on Accounts, Leads, Contacts and many other modules.

Let's follow the steps below to see how we can accomplish that!

Download Documentation

Zoho CRM Connector for Informatica is based on ZappySys API Driver which is part of ODBC PowerPack. It is a collection of high-performance ODBC drivers that enable you to integrate data in SQL Server, SSIS, a programming language, or any other ODBC-compatible application. ODBC PowerPack supports various file formats, sources and destinations, including REST/SOAP API, SFTP/FTP, storage services, and plain files, to mention a few.

Connect to Zoho CRM in other apps

Connect to Zoho CRM in SSIS

Connect to Zoho CRM in SQL Server

Connect to Zoho CRM in Power BI

Connect to Zoho CRM in SSRS

Connect to Zoho CRM in MS Access

Connect to Zoho CRM in MS Excel

Connect to Zoho CRM in SSAS

Connect to Zoho CRM in C#

Connect to Zoho CRM in Python

Connect to Zoho CRM in JAVA

Connect to Zoho CRM in Tableau

Connect to Zoho CRM in SAP Crystal Reports

Connect to Zoho CRM in Azure Data Factory (Pipeline)

Connect to Zoho CRM in Azure Data Factory (SSIS)

Connect to Zoho CRM in Talend Studio

Connect to Zoho CRM in UiPath

Connect to Zoho CRM in PowerShell

Connect to Zoho CRM in ODBC

NOTE: If you need to consume API which is not listed on connector library page then please refer to the below article links. It talks about how to read / write pretty much any API and not just Zoho CRM API. It explains various API tips / tricks using our other Universal Drivers not mentioned in this article (i.e. ZappySys JSON / XML and CSV Drivers).
How to read API data in Informatica (Call JSON / XML SOAP Service)
How to write data to API (POST) in Informatica (Call JSON / XML SOAP Service)

Introduction

JSON / REST API is becoming more and more popular each day as everyone embrace cloud-centric services. This article is primarily focused on Informatica users who want to access Zoho CRM data or may be other API Integration in Informatica. However many tips and techniques described in this article will help you to understand how to integrate Zoho CRM / XML SOAP / JSON / REST API in other ETL / Reporting apps such as Tableau, Power BI, SSRS, Talend, Excel and many more.

After going through this article you will learn how to Read Zoho CRM / JSON / REST API data in Informatica and understand the concept of JSON / REST API. We will go through many screenshots and step-by-step examples to demonstrate Zoho CRM or REST API integration in Informatica PowerCenter.

XML / JSON can come from a local file or REST API service (internal or public) so we will include both examples in this article (i.e. Read JSON files in Informatica, Import REST API in Informatica). So let’s get started. Next article will focus on how to write data to API in Informatica (POST / PUT data)

Requirements

This article assumes that you have full filled following basic requirements.

Download Install ZappySys ODBC PowerPack (API Driver for Zoho CRM included)
Install Informatica PowerCenter Client Tools (e.g. Workflow and Mapping Designers)
Access to a Relational database such as SQL Server (or use any of your choice e.g. Oracle, MySQL, DB2 ). If nothing available then you can use flat file target.

High level Steps for Import Zoho CRM data using Informatica (Read Zoho CRM API data)

Before we dive deep to learn how to load Zoho CRM data in Informatica (i.e. Zoho CRM to SQL Table), Here the summary of high-level steps you need to perform to import Zoho CRM in Informatica (same steps for Import JSON / XML / REST API).

Download and Install ZappySys API Driver (for connecting to Zoho CRM)
Create ODBC DSN using ZappySys API driver and choose Zoho CRM Connector during Wizard
Create Relational > ODBC Connection in Informatica Workflow designer (Point to DSN we created in the previous step)
Import Zoho CRM Source Definition in the Informatica Mapping Designer > Sources Tab
Import Target Table Definition in the Informatica Mapping Designer > Targets Tab
Create source to target mapping in Mappings tab
Save mapping (name m_API_to_SQL_Load )
Create Session using the mapping we created in the previous step
Save Workflow and execute to load Zoho CRM data into SQL Table. Verify your data and log.
Loading Zoho CRM data to SQL Table in Informatica (Import REST API or JSON Files)

Video Tutorial – Read any API / JSON data in Informatica (Load Zoho CRM to SQL Table)

Below video is not about Zoho CRM API but its showing API access in general (for any API). By watching following ~5 min video can learn steps listed in this article to load JSON API data into SQL Server Table using ZappySys JSON Driver. You can go though full article to learn many useful details not covered in this video.

Watch this video on YouTube

Getting Started – Import Zoho CRM to SQL Server in Informatica

Now let’s get started. For example purpose, we will read data from Zoho CRM and load data into SQL Server Table using Informatica Workflow.

Create ODBC Data Source (DSN) based on ZappySys API Driver

Step-by-step instructions

To get data from Zoho CRM using Informatica we first need to create a DSN (Data Source) which will access data from Zoho CRM. We will later be able to read data using Informatica. Perform these steps:

Install ZappySys ODBC PowerPack.
Open ODBC Data Sources (x64):
Create a User data source (User DSN) based on ZappySys API Driver

ZappySys API Driver
- Create and use User DSN if the client application is run under a User Account. This is an ideal option in design-time, when developing a solution, e.g. in Visual Studio 2019. Use it for both type of applications - 64-bit and 32-bit.
- Create and use System DSN if the client application is launched under a System Account, e.g. as a Windows Service. Usually, this is an ideal option to use in a production environment. Use ODBC Data Source Administrator (32-bit), instead of 64-bit version, if Windows Service is a 32-bit application.
When the Configuration window appears give your data source a name if you haven't done that already, then select "Zoho CRM" from the list of Popular Connectors. If "Zoho CRM" is not present in the list, then click "Search Online" and download it. Then set the path to the location where you downloaded it. Finally, click Continue >> to proceed with configuring the DSN:

ZohoCrmDSN

Zoho CRM

Now it's time to configure the Connection Manager. Select Authentication Type, e.g. Token Authentication. Then select API Base URL (in most cases, the default one is the right one). More info is available in the Authentication section.

OAuth [OAuth]

OAuth Connection for Zoho CRM API [API reference]

Steps how to get and use Zoho CRM credentials : OAuth [OAuth]
To register custom App, perform the following steps (Detailed steps found in the help link at the end)

Go to Zoho API Console
Click Add Client link
Select Server-based Applications option
Enter desired client name (Display purpose only)
Enter some URL for Company homepage
For Authorized Redirect URI enter https://zappysys.com/oauth (Or enter your own but we recommend using ZappySys one if possible). This URL must match on Zoho Connector UI.
Click CREATE.
Copy Client ID and Secret and paste on Zoho Connector UI.

Fill in all required parameters and set optional parameters if needed:

ZohoCrmDSN

Zoho CRM

OAuth [OAuth]

https://www.zohoapis.com/crm/[$Version$]

Optional Parameters
ClientId
ClientSecret
Permissions	ZohoCRM.settings.all ZohoCRM.modules.all ZohoCRM.coql.READ
AccountUrl	https://accounts.zoho.com
RedirectUrl	https://zappysys.com/oauth
API Version	v2
RetryMode	RetryWhenStatusCodeMatch
RetryStatusCodeList	429
RetryCountMax	5
RetryMultiplyWaitTime	True

Once the data source has been configured, you can preview data. Select the Preview tab and use settings similar to the following to preview data:
Click OK to finish creating the data source.

Video instructions

Watch this video on YouTube

Create Connection in Informatica Workflow Designer

Once you create DSN using API Driver our next step is to define a connection for Zoho CRM source in Informatica PowerCenter Workflow designer.

Open Workflow designer [W] icon
Goto Connections > Relational

Create a new connection for Zoho CRM in Informatica
Click New and select ODBC

Select ODBC connection type in Informatica (Using ZappySys API ODBC DSN)
Now on the ODBC connection setup enter connection name, some fake userid / password (this is a required field but its ignored by JSON Driver)
In the Connection String field enter the exact same name of DSN (Open ODBC Data Sources UI to confirm)

Configure Zoho CRM connection in Informatica for REST API – Using ZappySys API Driver
Click OK to close the connection properties.

That’s it. Now we ready to move to next step (define source and target in Mapping Designer).

Import Zoho CRM Source Definition in Informatica Mapping Designer

Now let’s look at steps to import Zoho CRM table definition.

Open Informatica Mapping Designer (Click [D] icon)
Click on Source Icon to switch to Sources designer
From the top menu > Click on Sources > Import from Database …

Import Zoho CRM Source definition in Informatica Mapping Designer (JSON file or REST API)
Select ODBC data source from the dropdown (Find out DSN we created earlier to use as JSON Source)
Click Connect button to get a list of tables. Any array node is listed as a table. Also, you will see array node with parent columns (e.g. value_with_parent). You may get some warning like below but they are harmless so just ignore by clicking OK.

DLL name entry missing from C:\Informatica\PowerCenter8.6.1\client\bin\powrmart.ini Section = ODBCDLL Entry = ZappySys JSON Driver
—————————————————-
Using EXTODBC.DLL to support ZappySys JSON Driver. For native support of ZappySys JSON Driver make an entry in the .ini file.

Select Zoho CRM Source Table in Informatica Mapping Designer (JSON file or REST API)
Select Table you wish to get (You can filter rows by custom SQL query. We will see later in this article how to do)
Optionally once table structure is imported you can rename it

Rename imported table definition in Informatica Source Designer
That’s it, we are now ready to perform similar steps to import Target table structure in the next section.

Import SQL Server Target Definition in Informatica Mapping Designer

Now let’s look at steps to import Target table definition (very similar to the previous section, the only difference is this time we will select DSN which points to SQL Server or any other Target Server).

Now lets look at steps to import target table definition in Informatica mapping designer.

In the Mapping Designer, Click on Target Icon to switch to Target designer
From the top menu > Click on Targets > Import from Database …
Select DSN for your Target server (if DSN doesn’t exist then create one by opening ODBC Sources just like we created one for JSON API source (see the previous section about creating DSN).

Import target Table Definition in informatica
Enter your userid , password and Schema name and click Connect to see tables
Select Table name to and click OK import definition.

Import Target SQL Table Definition in Informatica – Select table from the list

Create Source to Target Mapping in Informatica (Import JSON to SQL Server)

Once you have imported source and target table definition, we can create mapping and transformation to load data from JSON to SQL Table.

First open Mapping Designer (Click [D] icon)
Drag JSON Source from sources folder
Drag SQL Table from Targets folder
Map desired columns from Source to target

Define Source to Target mapping for Zoho CRM to SQL Table load in Informatica
For certain columns you may have to do datatype conversion. For example to convert OrderDate form nstring to DataTime you have to use Expression Transform like below and map it to target. In below example, our JSON has date format (e.g. 2018-01-31 12:00:00 AM ). To import this to DateTime field in SQL server we need to convert it using TO_DATE function. Use double quotes around T to make this format working.
```
TO_DATE(OrderDate,'YYYY-MM-DD H12:MI:SS AM')

 --For ISO use below way
                TO_DATE(OrderDate,'YYYY-MM-DD"T"HH24:MI:SS')
```
Informatica Zoho CRM to SQL Table Mapping – Datatype conversion (nstring to datetime)
Once you done with mapping save your mapping and name it (i.e. m_Api_To_SQL)
Now lets move to next section to create workflow.

Create Workflow and Session in Informatica

Now the final step is to create a new workflow. Perform following steps to create workflow which with a session task to import JSON data into SQL table.

Open workflow designer by click [W] icon.
Launch new workflow creation wizard by click Workflow top menu > Wizard
name your workflow (e.g. wf_Api_Tp_Sql_Table_Import)

Creating Informatica Workflow – Wizard UI (Import Zoho CRM data to SQL Table)
Finish the wizard and double-click the Session to edit some default properties.
First change Error settings so we fail session on error (By default its always green)

Fail Informatica Session on error (Zoho CRM data to SQL Load)
Select JSON connection for Source

Select Zoho CRM Source Connection in Informatica – Load Zoho CRM data to SQL Table
Change default Source query if needed. You can pass parameters to this query to make it dynamic.

Modify Zoho CRM Source SQL query – Pass parameters, change URL, set filter etc
Select Target connection of SQL Target Table

Select SQL Target Connection in Informatica – Load Zoho CRM data to SQL Table
Save workflow
That’s it. We ready to run our first workflow to load JSON data to SQL.

Execute Workflow and Validate Log in Informatica

Now once you are done with your workflow, execute it to see the log.

Loading JSON data to SQL Table in Informatica (Import REST API or JSON Files)

Loading Zoho CRM data to SQL Table in Informatica (Import REST API or JSON Files)

POST data to Zoho CRM in Informatica

There will be a time when you like to send Source data to REST API or SOAP Web Service. You can use below Query for example. For detailed explanation on how to POST data in Informatica check this article.

Video Tutorial – How to POST data to REST API in Informatica

Here is detailed step by step video on REST API POST in informatica PowerCenter

Watch this video on YouTube

Keywords

Advanced topics

Create Custom Stored Procedure in ZappySys Driver

You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.

Steps to create Custom Stored Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here

Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
Enter the desired Procedure name and click on OK:
Select the created Stored Procedure and write the your desired stored procedure and Save it and it will create the custom stored procedure in the ZappySys Driver:
Here is an example stored procedure for ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
```
CREATE PROCEDURE [usp_get_orders]
    @fromdate = '<<yyyy-MM-dd,FUN_TODAY>>'
 AS
    SELECT * FROM Orders where OrderDate >= '<@fromdate>';
```
That's it now go to Preview Tab and Execute your Stored Procedure using Exec Command. In this example it will extract the orders from the date 1996-01-01:
```
Exec usp_get_orders '1996-01-01';
```
Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
```
SELECT * FROM OPENQUERY([LINKED_SERVER_TO_ZOHO_CRM_IN_DATA_GATEWAY], 'EXEC usp_get_orders @fromdate=''1996-07-30''')
```
Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.

Create Custom Virtual Table in ZappySys Driver

ZappySys API Drivers support flexible Query language so you can override Default Properties you configured on Data Source such as URL, Body. This way you don't have to create multiple Data Sources if you like to read data from multiple EndPoints. However not every application support supplying custom SQL to driver so you can only select Table from list returned from driver.

If you're dealing with Microsoft Access and need to import data from an SQL query, it's important to note that Access doesn't allow direct import of SQL queries. Instead, you can create custom objects (Virtual Tables) to handle the import process.

Many applications like MS Access, Informatica Designer wont give you option to specify custom SQL when you import Objects. In such case Virtual Table is very useful. You can create many Virtual Tables on the same Data Source (e.g. If you have 50 URLs with slight variations you can create virtual tables with just URL as Parameter setting.

Go to Custom Objects Tab and Click on Add button and Select Add Table:
Enter the desired Table name and click on OK:
And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.
Select the created table, Select Text Type AS SQL and write the your desired SQL Query and Save it and it will create the custom table in the ZappySys Driver:
Here is an example SQL query for ZappySys Driver. You can insert Placeholders also. Read more about placeholders here
```
SELECT
  "ShipCountry",
  "OrderID",
  "CustomerID",
  "EmployeeID",
  "OrderDate",
  "RequiredDate",
  "ShippedDate",
  "ShipVia",
  "Freight",
  "ShipName",
  "ShipAddress",
  "ShipCity",
  "ShipRegion",
  "ShipPostalCode"
FROM "Orders"
Where "ShipCountry"='USA'
```
That's it now go to Preview Tab and Execute your custom virtual table query. In this example it will extract the orders for the USA Shipping Country only:
```
SELECT * FROM "vt__usa_orders_only"
```
Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
```
SELECT * FROM OPENQUERY([LINKED_SERVER_TO_ZOHO_CRM_IN_DATA_GATEWAY], 'EXEC [usp_get_orders] ''1996-01-01''')
```
Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.

Actions supported by Zoho CRM Connector

Zoho CRM Connector support following actions for REST API integration. If some actions are not listed below then you can easily edit Connector file and enhance out of the box functionality.

Read Data (Query Mode - Max 200 Rows Only)

[ Read more... ]

Parameter	Description
sql_query	Your SQL query for CRM (i.e. COQL (CRM Object Query Language)). Limtation - You can fetch maximum 200 rows using COQL Query. To read all rows use Table mode. (refer to help link to learn more about COQL)

List Modules

[ Read more... ]

Parameter	Description

List Territories

[ Read more... ]

List Module Settings

To get the metadata for a specific module. Specify the API name of the module, such as Leads, Accounts or Deals in your API request. [ Read more... ]

Parameter

Description

module

Module name for which you like to get settings

Option	Value
Accounts	Accounts
Activities	Activities
Calls	Calls
Campaigns	Campaigns
Cases	Cases
Contacts	Contacts
Deals	Deals
Events	Events
Invoices	Invoices
Leads	Leads
Price_Books	Price_Books
Products	Products
Purchase_Orders	Purchase_Orders
Quotes	Quotes
Sales_Orders	Sales_Orders
Solutions	Solutions
Tasks	Tasks
Vendors	Vendors
Your_Custom_Module_Name	Your_Custom_Module_Name

List Tags

List tags for module. [ Read more... ]

Parameter

Description

module

Module name for which you like to get settings

Option	Value
Accounts	Accounts
Activities	Activities
Calls	Calls
Campaigns	Campaigns
Cases	Cases
Contacts	Contacts
Deals	Deals
Events	Events
Invoices	Invoices
Leads	Leads
Price_Books	Price_Books
Products	Products
Purchase_Orders	Purchase_Orders
Quotes	Quotes
Sales_Orders	Sales_Orders
Solutions	Solutions
Tasks	Tasks
Vendors	Vendors
Your_Custom_Module_Name	Your_Custom_Module_Name

Gets record count for specific tag for module

Add tags for specified module and specified record id(s). [ Read more... ]

Parameter

Description

module

Module name for which you like to get settings

Option	Value
Accounts	Accounts
Activities	Activities
Calls	Calls
Campaigns	Campaigns
Cases	Cases
Contacts	Contacts
Deals	Deals
Events	Events
Invoices	Invoices
Leads	Leads
Price_Books	Price_Books
Products	Products
Purchase_Orders	Purchase_Orders
Quotes	Quotes
Sales_Orders	Sales_Orders
Solutions	Solutions
Tasks	Tasks
Vendors	Vendors
Your_Custom_Module_Name	Your_Custom_Module_Name

Tag Id

Use List Tags to findout Id for tag you like to query

Add / Update Tags for records

Add tags for specified module and specified record id(s). [ Read more... ]

Parameter

Description

module

Module name for which you like to get settings

Option	Value
Accounts	Accounts
Activities	Activities
Calls	Calls
Campaigns	Campaigns
Cases	Cases
Contacts	Contacts
Deals	Deals
Events	Events
Invoices	Invoices
Leads	Leads
Price_Books	Price_Books
Products	Products
Purchase_Orders	Purchase_Orders
Quotes	Quotes
Sales_Orders	Sales_Orders
Solutions	Solutions
Tasks	Tasks
Vendors	Vendors
Your_Custom_Module_Name	Your_Custom_Module_Name

Record Id(s) (comma seperated list)

List of Record Id(s) you like to update

Tag Id

List of Tag(s) you like to add

Overwrite

Set this to overwrite exising tags for the record(s)

Option	Value
true	true
false	false

List Module Fields

To get the field meta data for the specified module. The fields displayed are from all layouts for the module and the response does not contain layout-specific fields like mandatory fields or picklist values. [ Read more... ]

Parameter

Description

module

Module name for which you like to get all fields

Option	Value
Accounts	Accounts
Activities	Activities
Calls	Calls
Campaigns	Campaigns
Cases	Cases
Contacts	Contacts
Deals	Deals
Events	Events
Invoices	Invoices
Leads	Leads
Price_Books	Price_Books
Products	Products
Purchase_Orders	Purchase_Orders
Quotes	Quotes
Sales_Orders	Sales_Orders
Solutions	Solutions
Tasks	Tasks
Vendors	Vendors
Your_Custom_Module_Name	Your_Custom_Module_Name

List Views

[ Read more... ]

Parameter	Description
module	Module name for which you like to get all views

Read [$parent.module_name$]

This endpoint reads records using bulk approach. Default API Version is V2 (set connection level) and its almost 2 times faster than higher API version (e.g. V3+) but V2 may return less number of columns compared to new API versions (e.g. v3...v7+). API V2 makes less number of requests and returns more records per call (200 rows), on the other side V3+ has limits of max 50 fields in each Get Records API calls. To avoid this limitation in V3+ API we used /{module}?ids={150 ids} workaround but this is still slower compred to older API (v2) approach. Choose new API if you have a valid reason (e.g. you need additional new columns exposed in v3+) else stick with older version V2 (its default setting) [ Read more... ]

Parameter

Description

Module

Fetch records modified after (local time format: yyyy-MM-ddTHH:mm:ss)

Supply this DateTime (Local Time in ISO 8601 format) - To get the list of recently modified records after this datetime.

Custom View ID

To get the list of records based on custom views.

Fields (Only for V2 API)

To retrieve specific field values. Kepp blank to get all fields.

sort_by

Specify the field name based on which the records must be sorted.

sort_order

To sort the list of records in either ascending or descending order.

Option	Value
asc	asc
desc	desc

territory_id

To get the list of records in a territory. Use get_territories endpoint to list Id and names.

include_child

To include records from the child territories. Default is false.

Option	Value
true	true
false	false

converted

Option	Value
true	true
false	false
both	both

Read [$parent.module_name$] (Use this for fewer than 50 Fields in v3+)

Use this endpoint if you have fewer than 50 fields and you like to utilize newer APi e.g. V3+, If you calling older API V2 then you can use any endpoint (e.g. get_contacts or get_contacts_fast or Contacts table all yeilds same speed in V2). [ Read more... ]

Parameter

Description

Module

Fetch records modified after (local time format: yyyy-MM-ddTHH:mm:ss)

Supply this DateTime (Local Time in ISO 8601 format) - To get the list of recently modified records after this datetime.

Custom View ID

To get the list of records based on custom views.

Fields (Only for V2 API)

To retrieve specific field values. Kepp blank to get all fields.

sort_by

Specify the field name based on which the records must be sorted.

sort_order

To sort the list of records in either ascending or descending order.

Option	Value
asc	asc
desc	desc

territory_id

To get the list of records in a territory. Use get_territories endpoint to list Id and names.

include_child

To include records from the child territories. Default is false.

Option	Value
true	true
false	false

converted

Option	Value
true	true
false	false
both	both

Search [$parent.module_name$]

Search records by criteria or email or phone or word or id (specify only one parameter for search and keep other blank) [ Read more... ]

Parameter

Description

Search By Criteria Expression

You can supply upto 10 criterias. For more complex expression use Query API. Example: ((Last_Name:equals:Burns)and(First_Name:starts_with:Ma)). You can lookup row by ID like (id:equals:1458554000067017001). Here is Syntax for expression (({api_name}:{starts_with|equals|in|between|not_equal|greater_equal|less_equal}:{value})and/or({api_name}:{starts_with|equals|in|between|not_equal|greater_equal|less_equal}:{value}))

Option	Value
None
Example of Equal	(id:equal:11223344)
Example NOT EQUAL	(id:not_equal:11223344)
Example OR (multiple conditions)	(id:equal:1111111)or(id:equal:222222222)
Example IN	(id:in:1111111,222222222,333333333)
Example START_WITH	(Last_Name:starts_with:pat)
Example BETWEEN	(Created_Time:between:2024-02-01T18:52:56+00:00,2024-02-20T18:52:56+00:00)

Search By Email

Search By Phone

Search By any Word

Search By Id

Include only converted records

Option	Value
true	true
false	false
both	both

Include approved records

Option	Value
true	true
false	false
both	both

Delete [$parent.module_name$]

[ Read more... ]

Parameter

Description

Record ID(s) - Use Comma for multiple (e.g. 111,222)

Fire Wordflow Trigger

Option	Value
true	true
false	false

Insert [$parent.module_name$]

[ Read more... ]

Parameter	Description
Triggers

Update [$parent.module_name$]

[ Read more... ]

Parameter	Description
Triggers

Upsert [$parent.module_name$] (Update or Insert)

[ Read more... ]

Parameter

Description

Triggers

Duplicate_Check_Fields

Option	Value
By Email	Email
By Phone	Phone
By Mobile	Mobile

Generic Request

This is generic endpoint. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL. [ Read more... ]

Parameter

Description

Url

API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains

Body

Request Body content goes here

IsMultiPart

Set this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value) ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip ) ==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) ===== To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored. If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type. See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header => Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored). file1=@c:\data\Myfile1.txt file2=@c:\data\Myfile2.json file2.Content-Type=application/json SomeField1=aaaaaaa SomeField1.Content-Type=text/plain SomeField2=12345 SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab SomeFieldStartingWithAtSign=\@MyTwitterHandle

Filter

Enter filter to extract array from response. Example: $.rows[*] --OR-- $.customers[*].orders[*]. Check your response document and find out hierarchy you like to extract

Option	Value
No filter
Example1	$.store.books[*]
Example2 (Sections Under Books)	$.store.books[].sections[]
Example3 (Equals)	$.store.books[?(@author=='sam')]
Example4 (Equals - Any Section)	$..[?(@author=='sam')]
Example5 (Not Equals - Any Section)	$..[?(@author!='sam')]
Example6 (Number less than)	$.store.books[?(@.price<10)] Example7 (Regular Expression - Contains Pattern)=$.store.books[?(@author=~ /sam\|bob/ )]
Example8 (Regular Expression - Does Not Contain Pattern)	$.store.books[?(@author=~ /^((?!sam\|bob).)*$/ )]
Example9 (Regular Expression - Exact Pattern Match)	$.store.books[?(@author=~ /^sam\|bob$/ )]
Example10 (Regular Expression - Starts With)	$.store.books[?(@author=~ /^sam/ )]
Example11 (Regular Expression - Ends With)	$.store.books[?(@author=~ /sam$/ )]
Example12 (Between)	$.store.employees[?( @.hiredate>'2015-01-01' && @.hiredate<'2015-01-04' )]

Headers

Headers for Request. To enter multiple headers use double pipe or new line after each {header-name}:{value} pair

Generic Request (Bulk Write)

This is a generic endpoint for bulk write purpose. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL. [ Read more... ]

Parameter	Description
Url	API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains
IsMultiPart	Set this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value) ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip ) ==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) ===== To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored. If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type. See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header => Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored). file1=@c:\data\Myfile1.txt file2=@c:\data\Myfile2.json file2.Content-Type=application/json SomeField1=aaaaaaa SomeField1.Content-Type=text/plain SomeField2=12345 SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab SomeFieldStartingWithAtSign=\@MyTwitterHandle
Filter	Enter filter to extract array from response. Example: $.rows[] --OR-- $.customers[].orders[*]. Check your response document and find out hierarchy you like to extract
Headers	Headers for Request. To enter multiple headers use double pipe (\|\|) or new line after each {header-name}:{value} pair

Zoho CRM Connector Examples for Informatica Connection

This page offers a collection of SQL examples designed for seamless integration with the ZappySys API ODBC Driver under ODBC Data Source (36/64) or ZappySys Data Gateway, enhancing your ability to connect and interact with Prebuilt Connectors effectively.

Read all rows [ Read more... ]

SELECT * from Accounts

Update Owner of the record(s) - Account, Contacts, Deals, Leads (Update Lookup field) [ Read more... ]

This examples shows how to update a lookup type fields (e.g. Account, Contact, Owner) for any module. Lookup fields are jsonobject type of fields which has id, name and sometimes email (only for Owner). This example shows how to update using unique field (E.g. email, id or name). Below example shows how to set Owner of the Account (e.g.) 1558554000137221573. We will set owner to bob-the-salesman@abc.com (or you can set by id)

UPDATE Accounts 
SET Owner='{email: "bob-the-salesman@abc.com"}'
--SET Owner='{id: "1558554000186378001"}' --you can also use Id
Where Id='1558554000137221573'

Update Account or Contact (Lookup field) by Name or Id for Deals [ Read more... ]

This examples shows how to update Account and Contact field on Deals module. We used name for account and id for contact just to show how unique field can be used.

UPDATE Deals 
SET Account_Name='{"name": "Company ABCD"}',    --by name or id 
    Contact_Name='{"id": "1558554000186378001"}'  --by id 
Where Id='1558554000137221573'

Create a Deal with Lookup fields (e.g. set Account, Contact, Owner etc by Id or Name) [ Read more... ]

This examples shows how to create a new record with Lookup field(s) e.g account, contact or owner.

INSERT INTO Deals(
	Deal_name,
	Amount,
	Lead_Source,
	Account_Name,
	Contact_Name,
	Owner
	)
VALUES
   (
   'My Test Deal Creatyed on <<FUN_NOW>>', --deal name
   1000.50, --amount
   'Cold Call', --lead source
   '{name:"ZappySys"}', --account name or use id '{id:"1558554000030180013"}'
   '{id:"1558554000089352998"}' --contact id 
   '{id:"1558554000089352912"}' --owner id or use email {email: "bob-the-salesman@abc.com"}
   )

Read single row by ID [ Read more... ]

SELECT * from Accounts Where Id=1558554000105110008

Read reacord(s) modified after certain date [ Read more... ]

SELECT * from Accounts WITH(ModifiedSince = '2020-01-07T00:00:00')

Read using COQL (Zoho Serverside Query Language) [ Read more... ]

You can write server side query so you dont have to read full data on client side. For COQL LIMIT clause must be 200 or less. For more information check this URL https://zappysys.com/links?url=https://www.zoho.com/crm/developer/docs/api/COQL-Overview.html

SELECT * from get_module_data_coql WITH(sql_query= 'select Last_Name, First_Name, Company from Leads where Company like ''Test'' limit 200')

Update table for specific record [ Read more... ]

Update Leads SET Designation='VP Sales', Company='Test' Where id=1558554000012181009

Update table for specific record (older version) [ Read more... ]

Update Leads SET id='1558554000012181009' /* id must be supplied */, Designation='VP Sales', Company='Test'

Get accounts modified after certain date [ Read more... ]

SELECT * from Accounts Where Account_Name LIKE 'Test%' WITH(ModifiedSince = '2020-01-07T00:00:00')

Search accounts by specific field (server side filter) [ Read more... ]

You can use criteria listed here https://www.zoho.com/crm/developer/docs/api/v2/search-records.html

SELECT * FROM search_Accounts WITH(criteria='Account_Name:starts_with:test')

Create a new record [ Read more... ]

INSERT INTO Accounts(Account_Name, Phone) VALUES('Company ABC','111-567-8888')

Create a new account record (with show output on / off) [ Read more... ]

INSERT INTO Accounts(Account_Name, Phone) VALUES('Company ABC','111-567-8888') WITH(Output=1)

Delete single record by Id [ Read more... ]

Delete exising record by Id (single row). You can supply upto 100 comma seperated Ids

DELETE FROM Accounts WHERE id=11111111111

Delete multiple records by Ids [ Read more... ]

This example shows how to delete Account Records by multiple Ids. You can supply upto 100 comma seperated Ids

DELETE FROM Accounts WITH(Id='11111,22222,33333')

Upsert account record (Update or Insert - based on unique field(s) for module) [ Read more... ]

UPSERT INTO Accounts(Account_Name, Phone) VALUES('Company ABC','111-567-8888') WITH(Output=1)

Upsert lead record (Update or Insert - based on unique field(s) for module) [ Read more... ]

UPSERT INTO Leads(Last_Name, Email) VALUES('Patel','zpatel@abc.com') WITH(Output=1)

Create new account(s) in BULK (read / write from external source) [ Read more... ]

This examples shows how to use SOURCE clause to read data from MS SQL Server (or other external system) and send data to Zoho using Bulk API

INSERT INTO Accounts
SOURCE(
  'MSSQL' --ODBC or OLEDB
  ,'Data Source=localhost;Initial Catalog=Test;Integrated Security=true'
  ,'select ''Test Account-A'' as Account_Name,''111-111-1111'' as Phone
    UNION
    select ''Test Account-B'' as Account_Name,''222-222-2222'' as Phone
   '
)

UPSERT (Update or insert) account(s) in BULK (read / write from external source) [ Read more... ]

This examples shows how to use SOURCE clause to read data from MS SQL Server (or other external system) and send data to Zoho using Bulk API. Record uniqueness is checked based on Unique field setup for module (i.e. email, account name, phone etc)

UPSERT INTO Accounts
SOURCE(
  'MSSQL' --ODBC or OLEDB
  ,'Data Source=localhost;Initial Catalog=Test;Integrated Security=true'
  ,'select ''Test Account-A'' as Account_Name,''111-111-1111'' as Phone
    UNION
    select ''Test Account-B'' as Account_Name,''222-222-2222'' as Phone
   '
)

Update Tag(s) for exising records (add or overwrite) [ Read more... ]

SELECT * FROM post_tags
WITH(
	  module='Accounts'
	, ids='1558554000105151002'
	, tag_names='mytag1,mytag2'
  , over_write='true'
)

Conclusion

In this article we showed you how to connect to Zoho CRM in Informatica and integrate data without any coding, saving you time and effort. We encourage you to download Zoho CRM Connector for Informatica and see how easy it is to use it for yourself or your team.

If you have any questions, feel free to contact ZappySys support team. You can also open a live chat immediately by clicking on the chat icon below.

Download Zoho CRM Connector for Informatica Documentation

More integrations

Other connectors for Informatica

Amazon Ads

Amazon Selling Partner (SP-API)

Asana

Azure DevOps

Cosmos DB

DropBox

ElasticSearch

FastSpring

Google Ads

Google BigQuery

Google Calendar

Google Drive

Google Sheets

Hubspot

Jira

Mailchimp

ManagedEngine ServiceDesk Plus (Zoho)

OData

OneDrive

Outlook Mail (Office 365)

Power BI

ServiceNow

SharePoint Online

Shopify

Smartsheet

Stripe

YouTube

Zendesk

Zoho SalesIQ

Zoom

REST API

JSON

JSON File

XML

SOAP

XML File

JDBC-ODBC Bridge

Salesforce

CSV

Amazon S3 JSON File

Amazon S3 XML File

Amazon S3 CSV File

Azure Blob JSON File

Azure Blob XML File

Azure Blob CSV File

FTP/SFTP JSON File

FTP/SFTP XML File

FTP/SFTP CSV File

Build your own Custom API Connector

Other application integration scenarios for Zoho CRM

SSIS

SQL Server

Power BI

SSRS

MS Access

MS Excel

SSAS

Python

JAVA

Tableau

SAP Crystal Reports

Azure Data Factory (Pipeline)

Azure Data Factory (SSIS)

Talend Studio

UiPath

PowerShell

ODBC

Download Zoho CRM Connector for Informatica Documentation

Common Searches:

How to connect Zoho CRM in Informatica?
How to get Zoho CRM data in Informatica?
How to read Zoho CRM data in Informatica?
How to load Zoho CRM data in Informatica?
How to import Zoho CRM data in Informatica?
How to pull Zoho CRM data in Informatica?
How to push data to Zoho CRM in Informatica?
How to write data to Zoho CRM in Informatica?
How to POST data to Zoho CRM in Informatica?
Call Zoho CRM API in Informatica
Consume Zoho CRM API in Informatica
Zoho CRM Informatica Automate
Zoho CRM Informatica Integration
Integration Zoho CRM in Informatica
Consume real-time Zoho CRM data in Informatica
Consume real-time Zoho CRM API data in Informatica
Zoho CRM ODBC Driver | ODBC Driver for Zoho CRM | ODBC Zoho CRM Driver | SSIS Zoho CRM Source | SSIS Zoho CRM Destination
Connect Zoho CRM in Informatica
Load Zoho CRM in Informatica
Load Zoho CRM data in Informatica
Read Zoho CRM data in Informatica
Zoho CRM API Call in Informatica