Informatica Zoho CRM Connector

In this article you will learn how to integrate Zoho CRM data to Informatica without coding in just a few clicks (live / bi-directional connection to Zoho CRM). 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..

Using Zoho CRM Connector you will be able to connect, read, and write data from within Informatica. Follow the steps below to see how we would accomplish that.

Download  Help File  Buy 

See also
Zoho CRM Connector Connect Zoho CRM in SSIS SSIS
Connect Zoho CRM in SSIS
Zoho CRM Connector Connect Zoho CRM in SQL Server SQL Server
Connect Zoho CRM in SQL Server
Zoho CRM Connector Connect Zoho CRM in Power BI Power BI
Connect Zoho CRM in Power BI
Zoho CRM Connector Connect Zoho CRM in SSRS SSRS
Connect Zoho CRM in SSRS
Zoho CRM Connector Connect Zoho CRM in MS Access MS Access
Connect Zoho CRM in MS Access
Zoho CRM Connector Connect Zoho CRM in MS Excel MS Excel
Connect Zoho CRM in MS Excel
Zoho CRM Connector Connect Zoho CRM in SSAS SSAS
Connect Zoho CRM in SSAS
Zoho CRM Connector Connect Zoho CRM in C# C#
Connect Zoho CRM in C#
Zoho CRM Connector Connect Zoho CRM in Python Python
Connect Zoho CRM in Python
Zoho CRM Connector Connect Zoho CRM in JAVA JAVA
Connect Zoho CRM in JAVA
Zoho CRM Connector Connect Zoho CRM in Tableau Tableau
Connect Zoho CRM in Tableau
Zoho CRM Connector Connect Zoho CRM in SAP Crystal Reports SAP Crystal Reports
Connect Zoho CRM in SAP Crystal Reports
Zoho CRM Connector Connect Zoho CRM in Azure Data Factory (ADF) Azure Data Factory (ADF)
Connect Zoho CRM in Azure Data Factory (ADF)
Zoho CRM Connector Connect Zoho CRM in ODBC ODBC
Connect 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)

Read / Write Zoho CRM data in Informatica

Introduction

Informatica PowerCenter LogoJSON / 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 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  JSON File 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.

  1. Download Install ZappySys ODBC PowerPack (API Driver for Zoho CRM included)
  2. Install Informatica PowerCenter Client Tools (e.g. Workflow and Mapping Designers)
  3. 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 JSON Files or REST API in Informatica.

  1. Download and Install ZappySys API Driver (for connecting to Zoho CRM)
  2. Create ODBC DSN using ZappySys API driver and choose Zoho CRM Connector during Wizard
  3. Create Relational > ODBC Connection in Informatica Workflow designer (Point to DSN we created in the previous step)
  4. Import JSON Source Definition in the Informatica Mapping Designer > Sources Tab
  5. Import Target Table Definition in the Informatica Mapping Designer > Targets Tab
  6. Create source to target mapping in Mappings tab
  7. Save mapping (name m_API_to_SQL_Load )
  8. Create Session using the mapping we created in the previous step
  9. Save Workflow and execute to load Zoho CRM data into SQL Table. Verify your data and 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)

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.

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

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

  1. Install ZappySys ODBC PowerPack.

  2. Open ODBC Data Sources (x64):
    Open ODBC Data Source

  3. Create a User Data Source (User DSN) based on ZappySys API Driver

    ZappySys API Driver
    Create new System DSN for ZappySys API Driver
    You should create a System DSN (instead of a User DSN) if the client application is launched under a Windows System Account, e.g. as a Windows Service. If the client application is 32-bit (x86) running with a System DSN, use ODBC Data Sources (32-bit) instead of the 64-bit version.

  4. 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
    ODBC DSN Template Selection

  5. 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 [Read more..]

    Steps to get Zoho CRM Credentials : OAuth [OAuth]
    To register custom App, perform the following steps (Detailed steps found in the help link at the end)
    1. Go to Zoho API Console
    2. Click Add Client link
    3. Select Server-based Applications option
    4. Enter desired client name (Display purpose only)
    5. Enter some URL for Company homepage
    6. 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.
    7. Click CREATE.
    8. 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/v2
    Required Parameters
    Optional Parameters
    ClientId Fill in the parameter...
    ClientSecret Fill in the parameter...
    Permissions Fill in the parameter...
    AccountUrl Fill in the parameter...
    RedirectUrl Fill in the parameter...
    RetryMode Fill in the parameter...
    RetryStatusCodeList Fill in the parameter...
    RetryCountMax Fill in the parameter...
    RetryMultiplyWaitTime Fill in the parameter...
    ODBC DSN Oauth Connection Configuration

  6. 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:
    ODBC ZappySys Data Source Preview

  7. Click OK to finish creating the data source.

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.

  1. Open Workflow designer [W] icon
  2. Goto Connections > Relational
    Create new connection for JSON in Informatica

    Create a new connection for Zoho CRM in Informatica

  3. Click New and select ODBC
    Select ODBC connection type in Informatica (Using ZappySys JSON ODBC DSN)

    Select ODBC connection type in Informatica (Using ZappySys API ODBC DSN)

  4. Now on the ODBC connection setup enter connection name, some fake userid / password (this is a required field but its ignored by JSON Driver)
  5. 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 ODBC Driver

    Configure Zoho CRM connection in Informatica for REST API – Using ZappySys API Driver

  6. 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.

  1. Open Informatica Mapping Designer (Click [D] icon)
  2. Click on Source Icon to switch to Sources designer
  3. From the top menu > Click on Sources > Import from Database …
    Import JSON Source definition in Informatica Mapping Designer (JSON file or REST API)

    Import Zoho CRM Source definition in Informatica Mapping Designer (JSON file or REST API)

  4. Select ODBC data source from the dropdown (Find out DSN we created earlier to use as JSON Source)
  5. 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 JSON Source Table in Informatica Mapping Designer (JSON file or REST API)

    Select Zoho CRM Source Table in Informatica Mapping Designer (JSON file or REST API)

  6. Select Table you wish to get (You can filter rows by custom SQL query. We will see later in this article how to do)
  7. Optionally once table structure is imported you can rename it
    Rename imported table definition in Informatica Source Designer

    Rename imported table definition in Informatica Source Designer

  8. 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.

  1. In the Mapping Designer, Click on Target Icon to switch to Target designer
  2. From the top menu > Click on Targets > Import from Database …
  3. 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

    Import target Table Definition in informatica

  4. Enter your userid , password and Schema name and click Connect to see tables
  5. Select Table name to and click OK import definition.
    Import Target SQL Table Definition in Informatica - Select table from the list

    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.

  1. First open Mapping Designer (Click [D] icon)
  2. Drag JSON Source from sources folder
  3. Drag SQL Table from Targets folder
  4. Map desired columns from Source to target
    Define Source to Target mapping for JSON to SQL Table load in Informatica

    Define Source to Target mapping for Zoho CRM to SQL Table load in Informatica

  5. 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 JSON to SQL Table Mapping - Datatype conversion (nstring to datetime)

    Informatica Zoho CRM to SQL Table Mapping – Datatype conversion (nstring to datetime)

  6. Once you done with mapping save your mapping and name it (i.e. m_Api_To_SQL)
  7. 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.

  1. Open workflow designer by click [W] icon.
  2. 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 JSON data to SQL Table)

    Creating Informatica Workflow – Wizard UI (Import Zoho CRM data to SQL Table)

  3. Finish the wizard and double-click the Session to edit some default properties.
  4. First change Error settings so we fail session on error (By default its always green)
    Fail Informatica Session on error (JSON to SQL Load)

    Fail Informatica Session on error (Zoho CRM data to SQL Load)

  5. Select JSON connection for Source
    Select JSON Source Connection in Informatica - JSON File / REST API Load to SQL Table

    Select Zoho CRM Source Connection in Informatica – Load Zoho CRM data to SQL Table

  6. Change default Source query if needed. You can pass parameters to this query to make it dynamic.
    Modify JSON Source SQL query - Pass parameters, change URL, set filter etc

    Modify Zoho CRM Source SQL query – Pass parameters, change URL, set filter etc

  7. Select Target connection of SQL Target Table
    Select SQL Target Connection in Informatica - JSON File / REST API Load to SQL Table

    Select SQL Target Connection in Informatica – Load Zoho CRM data to SQL Table

  8. Save workflow
  9. 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 REST API 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

 

Keywords

how to import Zoho CRM in informatica | how to read Zoho CRM data in informatica powercenter | how to test json from informatica | how to use Zoho CRM data as source in informatica power center | how to connect Zoho CRM in informatica 10 | informatica how to import data from Zoho CRM | informatica jtx to import Zoho CRM (use of java transformation) | informatica plugin for restful api using json | informatica power center and Zoho CRM support | informatica read Zoho CRM | informatica rest api | informatica Zoho CRM connector | json parser import informatica

Create Custom Store 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 Store Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here

  1. Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
    ZappySys Driver - Add Store Procedure

  2. Enter the desired Procedure name and click on OK:
    ZappySys Driver - Add Store Procedure Name

  3. Select the created Store Procedure and write the your desired store procedure and Save it and it will create the custom store 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>';

    ZappySys Driver - Create Custom Store Procedure

  4. That's it now go to Preview Tab and Execute your Store 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';

    ZappySys Driver - Execute Custom Store Procedure

  5. Let's generate the SQL Server Query Code to make the API call using store 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([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')

    ZappySys Driver - Generate SQL Server Query

  6. Now go to SQL served and execute that query and it will make the API call using store procedure and provide you the response.
    ZappySys Driver - Generate SQL Server Query

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.

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.

  1. Go to Custom Objects Tab and Click on Add button and Select Add Table:
    ZappySys Driver - Add Table

  2. Enter the desired Table name and click on OK:
    ZappySys Driver - Add Table Name

  3. And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.

  4. 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'

    ZappySys Driver - Create Custom Table

  5. 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"

    ZappySys Driver - Execute Custom Virtual Table Query

  6. Let's generate the SQL Server Query Code to make the API call using store 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([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')

    ZappySys Driver - Generate SQL Server Query

  7. Now go to SQL served and execute that query and it will make the API call using store procedure and provide you the response.
    ZappySys Driver - Generate SQL Server Query

Conclusion

In this article we discussed how to connect to Zoho CRM in Informatica and integrate data without any coding. Click here to Download Zoho CRM Connector for Informatica and try yourself see how easy it is. If you still have any question(s) then ask here or simply click on live chat icon below and ask our expert (see bottom-right corner of this page).

Download Zoho CRM Connector for Informatica Documentation 

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)
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
Parameter Description
 List Territories
 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.
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.
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).
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).
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.
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
Parameter Description
module Module name for which you like to get all views
 Read [$parent.module_name$]
Parameter Description
Last Modified Date - Read data modified after it Supply this DateTime (ISO 8601 format) - To get the list of recently modified records
Custom View ID To get the list of records based on custom views.
fields 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 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)
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}:{value})and/or({api_name}:{starts_with|equals}:{value}))
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$]
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$]
Parameter Description
Triggers
 Update [$parent.module_name$]
Parameter Description
Triggers
 Upsert [$parent.module_name$] (Update or Insert)
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.
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 Check 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 =&gt; 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

Other App Integration scenarios for Zoho CRM

Zoho CRM Connector for SSIS
SSIS
Zoho CRM Connector for SQL Server
SQL Server
Zoho CRM Connector for Power BI
Power BI
Zoho CRM Connector for SSRS
SSRS
Zoho CRM Connector for MS Access
MS Access
Zoho CRM Connector for MS Excel
MS Excel
Zoho CRM Connector for SSAS
SSAS
Zoho CRM Connector for C#
C#
Zoho CRM Connector for Python
Python
Zoho CRM Connector for JAVA
JAVA
Zoho CRM Connector for Tableau
Tableau
Zoho CRM Connector for SAP Crystal Reports
SAP Crystal Reports
Zoho CRM Connector for Azure Data Factory (ADF)
Azure Data Factory (ADF)
Zoho CRM Connector for ODBC
ODBC

Other Connectors for Informatica

Zendesk Connector
Zendesk
Azure DevOps Connector
Azure DevOps
ManagedEngine ServiceDesk Plus (Zoho) Connector
ManagedEngine ServiceDesk Plus (Zoho)
Zoho CRM Connector
Zoho CRM
Hubspot Connector
Hubspot
Google Sheets Connector
Google Sheets
Stripe Connector
Stripe
YouTube Connector
YouTube
Google BigQuery Connector
Google BigQuery
OneDrive Connector
OneDrive
OData Connector
OData
Amazon Ads Connector
Amazon Ads
Mailchimp Connector
Mailchimp
Jira Connector
Jira
Outlook Mail (Office 365) Connector
Outlook Mail (Office 365)
Zoom Connector
Zoom
Cosmos DB Connector
Cosmos DB
Shopify Connector
Shopify
Nativo Connector
Nativo
Google Drive Connector
Google Drive
SharePoint Online Connector
SharePoint Online
Amazon MWS Connector
Amazon MWS
ServiceNow Connector
ServiceNow
ElasticSearch Connector
ElasticSearch
Google Calendar Connector
Google Calendar
DropBox Connector
DropBox
REST API Connector
REST API
JSON Connector
JSON
JSON File Connector
JSON File
XML Connector
XML
SOAP Connector
SOAP
XML File Connector
XML File
JDBC-ODBC Bridge Connector
JDBC-ODBC Bridge
Salesforce Connector
Salesforce
CSV Connector
CSV
Amazon S3 JSON File Connector
Amazon S3 JSON File
Amazon S3 XML File Connector
Amazon S3 XML File
Amazon S3 CSV File Connector
Amazon S3 CSV File
Azure Blob JSON File Connector
Azure Blob JSON File
Azure Blob XML File Connector
Azure Blob XML File
Azure Blob CSV File Connector
Azure Blob CSV File
FTP/SFTP JSON File Connector
FTP/SFTP JSON File
FTP/SFTP XML File Connector
FTP/SFTP XML File
FTP/SFTP CSV File Connector
FTP/SFTP CSV File


Download Zoho CRM Connector for Informatica Documentation 

  • 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 realtime 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