Zoho CRM Connector for SSIS

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.

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

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

Download Documentation

Zoho CRM Connector for SSIS is based on ZappySys API Connector Framework which is a part of SSIS PowerPack. It is a collection of high-performance SSIS connectors that enable you to integrate data with virtually any data provider supported by SSIS, including SQL Server. SSIS PowerPack supports various file formats, sources and destinations, including REST/SOAP API, SFTP/FTP, storage services, and plain files, to mention a few (if you are new to SSIS and SSIS PowerPack, find out more on how to use them).

Connect to Zoho CRM in other apps

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 Informatica

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

Video Tutorial - Integrate Zoho CRM data in SSIS

This video covers the following topics and more, so please watch carefully. After watching the video, follow the steps outlined in this article:

How to download and install the required PowerPack for Zoho CRM integration in SSIS
How to configure the connection for Zoho CRM
Features of the ZappySys API Source (Authentication / Query Language / Examples / Driver UI)
How to use the Zoho CRM in SSIS

Watch this video on YouTube

Prerequisites

Before we begin, make sure the following prerequisites are met:

SSIS designer installed. Sometimes it is referred as BIDS or SSDT (download it from Microsoft).
Basic knowledge of SSIS package development using Microsoft SQL Server Integration Services.
SSIS PowerPack is installed (if you are new to SSIS PowerPack, then get started!).

Read data from Zoho CRM in SSIS (Export data)

In this section we will learn how to configure and use Zoho CRM Connector in API Source to extract data from Zoho CRM.

Begin with opening Visual Studio and Create a New Project.
Select Integration Service Project and in new project window set the appropriate name and location for project. And click OK.
In the new SSIS project screen you will find the following:
1. SSIS ToolBox on left side bar
2. Solution Explorer and Property Window on right bar
3. Control flow, data flow, event Handlers, Package Explorer in tab windows
4. Connection Manager Window in the bottom
Note: If you don't see ZappySys SSIS PowerPack Task or Components in SSIS Toolbox, please refer to this help link.
Now, Drag and Drop SSIS Data Flow Task from SSIS Toolbox. Double click on the Data Flow Task to see Data Flow designer.
From the SSIS toolbox drag and API Source (Predefined Templates) on the data flow designer surface, and double click on it to edit it:
Select New Connection to create a new connection:
Use a preinstalled Zoho CRM Connector from Popular Connector List or press Search Online radio button to download Zoho CRM Connector. Once downloaded simply use it in the configuration:

Zoho CRM

Proceed with selecting the desired Authentication Type. Then select API Base URL (in most cases default one is the right one). Finally, fill in all the required parameters and set optional parameters if needed. You may press a link Steps to Configure which will help set certain parameters. More info is available in 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.

Configuring authentication parameters

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

Select the desired endpoint, change/pass the properties values, and click on Preview Data button to make the API call.

API Source - 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.
That's it! We are done! Just in a few clicks we configured the call to Zoho CRM using Zoho CRM Connector.

You can load the source data into your desired destination using the Upsert Destination, which supports SQL Server, PostgreSQL, and Amazon Redshift. We also offer other destinations such as CSV, Excel, Azure Table, Salesforce, and more. You can check out our SSIS PowerPack Tasks and components for more options. (*loaded in Trash Destination)

Write data to Zoho CRM using SSIS (Import data)

In this section we will learn how to configure and use Zoho CRM Connector in the API Destination to write data to Zoho CRM.

Video tutorial

This video covers following and more so watch carefully. After watching this video follow the steps described in this article.

How to download SSIS PowerPack for Zoho CRM integration in SSIS
How to configure connection for Zoho CRM
How to write or lookup data to Zoho CRM
Features about SSIS API Destination
Using Zoho CRM Connector in SSIS

Watch this video on YouTube

Step-by-step instructions

In upper section we learned how to read data, now in this section we will learn how to configure Zoho CRM in the API Source to POST data to the Zoho CRM.

Read the data from the source, being any desired source component. In example we will use ZappySys Dummy Data Source component.
From the SSIS Toolbox drag and drop API Destination (Predefined Templates) on the Data Flow Designer surface and connect source component with it, and double click to edit it.
Select New Connection to create a new connection:

API Destination - 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.
Use a preinstalled Zoho CRM Connector from Popular Connector List or press Search Online radio button to download Zoho CRM Connector. Once downloaded simply use it in the configuration:

Zoho CRM

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.

Configuring authentication parameters

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

Select the desired endpoint, change/pass the properties values, and go to the Mappings tab to map the columns.

API Destination - 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.
Finally, map the desired columns:

API Destination - 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.
That's it; we successfully configured the POST API Call. In a few clicks we configured the Zoho CRM API call using ZappySys Zoho CRM Connector

Load Zoho CRM data into SQL Server using Upsert Destination (Insert or Update)

Once you configured the data source, you can load Zoho CRM data into SQL Server using Upsert Destination.

Upsert Destination can merge or synchronize source data with the target table. It supports Microsoft SQL Server, PostgreSQL, and Redshift databases as targets. Upsert Destination also supports very fast bulk upsert operation along with bulk delete.

Upsert operation - a database operation which performs INSERT or UPDATE SQL commands based on record's existence condition in the target table. It inserts records that don't have matching records in the target table or updates them, if they do, by matching them by key columns.

Upsert Destination supports INSERT, UPDATE, and DELETE operations, so it is similar to SQL Server's MERGE command, except it can be used directly in SSIS package.

From the SSIS Toolbox drag-and-drop Upsert Destination component onto the Data Flow designer background.
Connect your SSIS source component to Upsert Destination.
Double-click on Upsert Destination component to open configuration window.
Start by selecting the Action from the list.
Next, select the desired target connection or create one by clicking <New [provider] Connection> menu item from the Target Connection dropdown.
Then select a table from the Target Table list or click New button to create a new table based on the source columns.
Continue by checking Insert and Update options according to your scenario (e.g. if Update option is unchecked, no updates will be made).
Finally, click Map All button to map all columns and then select the Key columns to match the columns on:
Click OK to save the configuration.
Run the package and Zoho CRM data will be merged with the target table in SQL Server, PostgreSQL, or Redshift:
Done!

Deploy and schedule SSIS package

After you are done creating SSIS package, most likely, you want to deploy it to SQL Server Catalog and run it periodically. Just follow the instructions in this article:

How to design, debug, deploy, schedule SSIS Package (In SQL Agent and Catalog)

Running SSIS package in Azure Data Factory (ADF)

To use SSIS PowerPack in ADF, you must first prepare Azure-SSIS Integration Runtime. Follow this link for detailed instructions:

Preparing ADF instance to use SSIS PowerPack

Advanced topics

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) using either raw file data (i.e., POST raw file data) or send data using the multi-part encoding method (i.e. Content-Type: multipart/form-data). A multi-part request allows you to mix key/value pairs and upload files in the same request. On the other hand, raw upload allows only a single file to be uploaded (without any key/value data). ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload a single file in raw mode, check this option and specify the full file path starting with the @ 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 in the RequestData field (i.e., Body). Each key/value pair should be entered on a new line, and key/value are separated using an equal sign (=). Leading and trailing spaces are ignored, and blank lines are also ignored. If a field value contains any special character(s), use escape sequences (e.g., for NewLine: \r\n, for Tab: \t, for at (@): @). When the value of any field starts with the at sign (@), it is automatically treated as a file you want to upload. By default, the file content type is determined based on the file extension; however, you can supply a content type manually for any field using this format: [YourFileFieldName.Content-Type=some-content-type]. By default, file upload fields always include Content-Type in the request (non-file fields do not have Content-Type by default unless you supply it manually). If, for some reason, you don't want to use the Content-Type header in your request, then supply a blank Content-Type to exclude this header altogether (e.g., SomeFieldName.Content-Type=). In the example below, we have supplied Content-Type for file2 and SomeField1. All other fields are using the default content type. See the example below 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 start with multipart/ or it 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) using either raw file data (i.e., POST raw file data) or send data using the multi-part encoding method (i.e. Content-Type: multipart/form-data). A multi-part request allows you to mix key/value pairs and upload files in the same request. On the other hand, raw upload allows only a single file to be uploaded (without any key/value data). ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload a single file in raw mode, check this option and specify the full file path starting with the @ 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 in the RequestData field (i.e., Body). Each key/value pair should be entered on a new line, and key/value are separated using an equal sign (=). Leading and trailing spaces are ignored, and blank lines are also ignored. If a field value contains any special character(s), use escape sequences (e.g., for NewLine: \r\n, for Tab: \t, for at (@): @). When the value of any field starts with the at sign (@), it is automatically treated as a file you want to upload. By default, the file content type is determined based on the file extension; however, you can supply a content type manually for any field using this format: [YourFileFieldName.Content-Type=some-content-type]. By default, file upload fields always include Content-Type in the request (non-file fields do not have Content-Type by default unless you supply it manually). If, for some reason, you don't want to use the Content-Type header in your request, then supply a blank Content-Type to exclude this header altogether (e.g., SomeFieldName.Content-Type=). In the example below, we have supplied Content-Type for file2 and SomeField1. All other fields are using the default content type. See the example below 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 start with multipart/ or it 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

Conclusion

In this article we showed you how to connect to Zoho CRM in SSIS and integrate data without any coding, saving you time and effort. It's worth noting that ZappySys API Driver allows you to connect not only to Zoho CRM, but to any Java application that supports JDBC (just use a different JDBC driver and configure it appropriately).

We encourage you to download Zoho CRM Connector for SSIS 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 SSIS Documentation

More integrations

Other connectors for SSIS

All

Big Data & NoSQL

Database

CRM & ERP

Marketing

Collaboration

Cloud Storage

Reporting

Commerce

API & Files

Amazon Ads

Amazon Athena

Amazon Selling Partner (SP-API)

ManagedEngine ServiceDesk Plus (Zoho)

MariaDB

OData

OneDrive

Outlook Mail (Office 365)

Build your own Custom API Connector

Other application integration scenarios for Zoho CRM

All

Data Integration

Database

BI & Reporting

Productivity

Programming Languages

Automation & Scripting

ODBC applications

Azure Data Factory (Pipeline)

Azure Data Factory (SSIS)

Download Zoho CRM Connector for SSIS Documentation

Common Searches:

How to connect Zoho CRM in SSIS?
How to get Zoho CRM data in SSIS?
How to read Zoho CRM data in SSIS?
How to load Zoho CRM data in SSIS?
How to import Zoho CRM data in SSIS?
How to pull Zoho CRM data in SSIS?
How to push data to Zoho CRM in SSIS?
How to write data to Zoho CRM in SSIS?
How to POST data to Zoho CRM in SSIS?
Call Zoho CRM API in SSIS
Consume Zoho CRM API in SSIS
Zoho CRM SSIS Automate
Zoho CRM SSIS Integration
Integration Zoho CRM in SSIS
Consume real-time Zoho CRM data in SSIS
Consume real-time Zoho CRM API data in SSIS
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 SSIS
Load Zoho CRM in SSIS
Load Zoho CRM data in SSIS
Read Zoho CRM data in SSIS
Zoho CRM API Call in SSIS

Zoho CRM Connector for SSIS

Video Tutorial - Integrate Zoho CRM data in SSIS

Prerequisites

Read data from Zoho CRM in SSIS (Export data)

OAuth [OAuth]

Write data to Zoho CRM using SSIS (Import data)

Video tutorial

Step-by-step instructions

OAuth [OAuth]

Load Zoho CRM data into SQL Server using Upsert Destination (Insert or Update)

Deploy and schedule SSIS package

Running SSIS package in Azure Data Factory (ADF)

Advanced topics

Actions supported by Zoho CRM Connector

Conclusion

More integrations

Other connectors for SSIS

Other application integration scenarios for Zoho CRM

How to connect Zoho CRM in SSIS?

How to get Zoho CRM data in SSIS?

How to read Zoho CRM data in SSIS?

How to load Zoho CRM data in SSIS?

How to import Zoho CRM data in SSIS?

How to pull Zoho CRM data in SSIS?

How to push data to Zoho CRM in SSIS?

How to write data to Zoho CRM in SSIS?

How to POST data to Zoho CRM in SSIS?

Call Zoho CRM API in SSIS

Consume Zoho CRM API in SSIS

Zoho CRM SSIS Automate

Zoho CRM SSIS Integration

Integration Zoho CRM in SSIS

Consume real-time Zoho CRM data in SSIS

Consume real-time Zoho CRM API data in SSIS

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 SSIS

Load Zoho CRM in SSIS

Load Zoho CRM data in SSIS

Read Zoho CRM data in SSIS

Zoho CRM API Call in SSIS