ManagedEngine ServiceDesk Plus (Zoho) Connectors

ZappySys ManagedEngine ServiceDesk Plus (Zoho) Connector provide read / write capability inside your app (see list below), using these drag and drop , high performance connectors you can perform many ManagedEngine ServiceDesk Plus (Zoho) operations without any coding. You can use this connector to integrate ManagedEngine ServiceDesk Plus (Zoho) data inside apps like SSIS, SQL Server or popular ETL Platforms / BI Tools/ Reporting Apps / Programming languages (i.e. Informatica, Power BI, SSRS, Excel, C#, JAVA, Python)

Download for SSIS Download for Other Apps Documentation

Video Tutorial - ManagedEngine ServiceDesk Plus (Zoho) - Connectors REST API Integration

Click on your App below to get started with ManagedEngine ServiceDesk Plus (Zoho) Integration

Choose your App / Scenario for which you like to integrate ManagedEngine ServiceDesk Plus (Zoho)

SSIS

SQL Server

Power BI

SSRS

Informatica

MS Access

MS Excel

SSAS

Python

JAVA

Tableau

SAP Crystal Reports

Azure Data Factory (ADF)

ODBC

Actions supported by ManagedEngine ServiceDesk Plus (Zoho) Connector

ManagedEngine ServiceDesk Plus (Zoho) 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.

Get Requests

[Read more...]

Parameter	Description

Get Request Details

[Read more...]

Parameter	Description
RequestId

Delete Request

[Read more...]

Parameter	Description
RequestId

Test Connection

[Read more...]

Get Request Tasks

[Read more...]

Parameter	Description
RequestId

Get Request Task Details

[Read more...]

Parameter	Description
RequestId
TaskId

Get Request Task Comments

[Read more...]

Parameter	Description
RequestId
TaskId

Get Request Task Comment Details

[Read more...]

Parameter	Description
RequestId
TaskId
CommentId

Get Request Notes

[Read more...]

Parameter	Description
RequestId

Get Request Note Details

[Read more...]

Parameter	Description
RequestId
NoteId

Get Request Worklogs

[Read more...]

Parameter	Description
RequestId

Get Request Worklog Details

[Read more...]

Parameter	Description
RequestId
WorklogId

Get Request Task Worklogs

[Read more...]

Parameter	Description
RequestId
TaskId

Get Request Task Worklog Details

[Read more...]

Parameter	Description
RequestId
TaskId
WorklogId

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	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 => 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

ManagedEngine ServiceDesk Plus (Zoho) Connector Examples (For ODBC PowerPack)

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.

List requests [Read more...]

This example shows how to list requests.

SELECT * FROM Requests

Read request details by ID [Read more...]

This example shows how to read extended information about a single request

SELECT * FROM Requests Where id=111112345

Delete request [Read more...]

This example shows how to delete a request by ID.

DELETE FROM Requests Where id=111112345

List request tasks [Read more...]

This example shows how to read all tasks for a single Request ID

SELECT * FROM get_Request_Tasks WITH (RequestId=111112345)

Read request task details [Read more...]

This example shows how to read request task details by single Request ID and Task ID

SELECT * FROM get_Request_Task_Details  (RequestId=111112345, TaskId=222212345)

List request task comments [Read more...]

This example shows how to read all comment for specific task

SELECT * FROM get_Request_Task_Comments  (RequestId=111112345, TaskId=222212345)

Read request task comment details [Read more...]

This example shows how to read a single comment details for a specific task

SELECT * FROM get_Request_Task_Comment_Details (RequestId=111112345, TaskId=222212345, CommentId=333312345)

List request notes [Read more...]

This example shows how to read all notes for a single Request ID

SELECT * FROM get_Request_Notes WITH (RequestId=111112345)

Read request note details [Read more...]

This example shows how to read request note details by single Request ID and Note ID

SELECT * FROM get_Request_Note_Details (RequestId=111112345, NoteId=222212345)

List request worklog [Read more...]

This example shows how to read all worklogs for a single Request ID

SELECT * FROM get_Request_Worklogs WITH (RequestId=111112345)

Read request worklog details [Read more...]

This example shows how to read request worklog details by single Request ID and Worklog ID

SELECT * FROM get_Request_Worklog_Details (RequestId=111112345, WorklogId=222212345)

List request task worklog [Read more...]

This example shows how to read all worklogs for a single Request Task ID

SELECT * FROM get_Request_Task_Worklogs WITH (RequestId=111112345, TaskId=22222345)

Read request task worklog details [Read more...]

This example shows how to read request task worklog details by single Request Task ID and Worklog ID

SELECT * FROM get_Request_Task_Worklog_Details (RequestId=111112345, TaskId=22222345, WorklogId=333312345)