ManagedEngine ServiceDesk Plus (Zoho) Connector for PowerShell

In this article you will learn how to integrate ManagedEngine ServiceDesk Plus (Zoho) data in PowerShell without coding in just a few clicks (live / bi-directional connection to ManagedEngine ServiceDesk Plus (Zoho)). ManagedEngine (Zoho) ServiceDesk Plus Connector can be used to integrate ServiceDesk Plus data in your App / BI Tools. You can read/write Requests, Tasks, Comments, Worklogs and many other items..

Using ManagedEngine ServiceDesk Plus (Zoho) Connector you will be able to connect, read, and write data from within PowerShell. Follow the steps below to see how we would accomplish that.

Download Documentation

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

Step-by-step instructions

To get data from ManagedEngine ServiceDesk Plus (Zoho) using PowerShell we first need to create a DSN (Data Source) which will access data from ManagedEngine ServiceDesk Plus (Zoho). We will later be able to read data using PowerShell. 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 User 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 "ManagedEngine ServiceDesk Plus (Zoho)" from the list of Popular Connectors. If "ManagedEngine ServiceDesk Plus (Zoho)" 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:

    ManagedEngineServiceDeskPlus(Zoho)DSN
    ManagedEngine ServiceDesk Plus (Zoho)
    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 Connection for ManageEngine ServiceDesk Plus API [API Help..]

    Steps to get ManagedEngine ServiceDesk Plus (Zoho) 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:

    ManagedEngineServiceDeskPlus(Zoho)DSN
    ManagedEngine ServiceDesk Plus (Zoho)
    OAuth [OAuth]
    https://sdpondemand.manageengine.com/api/v3
    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.

Video instructions

Read ManagedEngine ServiceDesk Plus (Zoho) data in PowerShell

Sometimes, you need to quickly access and work with your ManagedEngine ServiceDesk Plus (Zoho) data in PowerShell. Whether you need a quick data overview or the complete dataset, this article will guide you through the process. Here are some common scenarios:

Viewing data in a terminal
  • Quickly peek at ManagedEngine ServiceDesk Plus (Zoho) data
  • Monitor data constantly in your console
Saving data to a file
  • Export data to a CSV file so that it can be sliced and diced in Excel
  • Export data to a JSON file so that it can ingested by other processes
  • Export data to an HTML file for user-friendly view and easy sharing
  • Create a schedule to make it an automatic process
Saving data to a database
  • Store data internally for analysis or for further ETL processes
  • Create a schedule to make it an automatic process
Sending data to another API
  • Integrate data with other systems via external APIs

In this article, we will delve deeper into how to quickly view the data in PowerShell terminal and how to save it to a file. But let's stop talking and get started!

Reading individual fields

  1. Open your favorite PowerShell IDE (we are using Visual Studio Code).
  2. Then simply follow these instructions:
    "DSN=ManagedEngineServiceDeskPlus(Zoho)DSN"
    Read API data with PowerShell using ODBC DSN in Visual Code

    For your convenience, here is the whole PowerShell script:

    # Configure connection string and query
    $connectionString = "DSN=ManagedEngineServiceDeskPlus(Zoho)DSN"
    $query = "SELECT * FROM Customers"
    
    # Instantiate OdbcDataAdapter and DataTable
    $adapter = New-Object System.Data.Odbc.OdbcDataAdapter($query, $connectionString)
    $table = New-Object System.Data.DataTable
    
    # Fill the table with data
    $adapter.Fill($table)
    
    # Since we know we will be reading just 4 columns, let's define format for those 4 columns, each separated by a tab
    $format = "{0}`t{1}`t{2}`t{3}"
    
    # Display data in the console
    foreach ($row in $table.Rows)
    {
        # Construct line based on the format and individual ManagedEngine ServiceDesk Plus (Zoho) fields
        $line = $format -f ($row["CustomerId"], $row["CompanyName"], $row["Country"], $row["Phone"])
        Write-Host $line
    }
    
    Access specific ManagedEngine ServiceDesk Plus (Zoho) table field using this code snippet:
    $field = $row["ColumnName"]
    You will find more info on how to manipulate DataTable.Rows property in Microsoft .NET reference.
    For demonstration purposes we are using sample tables which may not be available in ManagedEngine ServiceDesk Plus (Zoho).
  3. To read values in a console, save the script to a file and then execute this command inside PowerShell terminal: Read API data in PowerShell using ODBC DSN
    You can also use even a simpler command inside the terminal, e.g.:
    . 'C:\Users\john\Documents\dsn.ps1'

Retrieving all fields

However, there might be case, when you want to retrieve all columns of a query. Here is how you do it:

"DSN=ManagedEngineServiceDeskPlus(Zoho)DSN"
Read all API columns from ODBC data source in PowerShell

Again, for your convenience, here is the whole PowerShell script:

# Configure connection string and query
$connectionString = "DSN=ManagedEngineServiceDeskPlus(Zoho)DSN"
$query = "SELECT CustomerId, CompanyName, Country, Phone FROM Customers"

# Instantiate OdbcDataAdapter and DataTable
$adapter = New-Object System.Data.Odbc.OdbcDataAdapter($query, $connectionString)
$table = New-Object System.Data.DataTable

# Fill the table with data
$adapter.Fill($table)

# Display data in the console
foreach ($row in $table.Rows) {
    $line = ""
    foreach ($column in $table.Columns) {
        $value = $row[$column.ColumnName]

        # Let's handle NULL values
        if ($value -is [DBNull])
        {
            $value = "(NULL)"
        }
        $line += $value + "`t"
    }
    Write-Host $line
}
You can limit the numbers of lines to retrieve by using a LIMIT keyword in the query, e.g.:
SELECT * FROM Customers LIMIT 10

Using a full ODBC connection string

In the previous steps we used a very short format of ODBC connection string - a DSN. Yet sometimes you don't want a dependency on an ODBC data source (and an extra step). In those times, you can define a full connection string and skip creating an ODBC data source entirely. Let's see below how to accomplish that in the below steps:

  1. Open ODBC data source configuration and click Copy settings:
    ZappySys API Driver - ManagedEngine ServiceDesk Plus (Zoho)
    ManagedEngine (Zoho) ServiceDesk Plus Connector can be used to integrate ServiceDesk Plus data in your App / BI Tools. You can read/write Requests, Tasks, Comments, Worklogs and many other items.
    ManagedEngineServiceDeskPlus(Zoho)DSN
    Copy connection string for ODBC application
  2. The window opens, telling us the connection string was successfully copied to the clipboard: Successful connection string copying for ODBC application
  3. Then just paste the connection string into your script: Paste ODBC connection string in PowerShell to read API data
  4. You are good to go! The script will execute the same way as using a DSN.

Have in mind that using a full connection string has length limitations.

Proceed to the next step to find out the details.

Limitations of using a full connection string

Despite using a full ODBC connection string may be very convenient it comes with a limitation: it's length is limited to 1024 symbols. It usually happens when API provider generates a very long Refresh Token when OAuth is at play. If it happens you use such API, you may get this error:

"Connection string exceeds maximum allowed length of 1024"

But there is a solution to this by storing the Refresh Token in a file instead of directly in ODBC connection string. Follow the steps below to achieve this.

  1. Open your ODBC data source
  2. Hit Advanced tab and enter a file path:
    ZappySys API Driver - ManagedEngine ServiceDesk Plus (Zoho)
    ManagedEngine (Zoho) ServiceDesk Plus Connector can be used to integrate ServiceDesk Plus data in your App / BI Tools. You can read/write Requests, Tasks, Comments, Worklogs and many other items.
    ManagedEngineServiceDeskPlus(Zoho)DSN
    Configure Refresh Token in ODBC data source
    If you cannot find the Advanced tab, try looking for Click to Configure link in Properties tab, under URL text box. Click it, and then configure the file path in OAuth Grant Options tab.
  3. Then click Copy settings button to copy a full connection string and paste it into your script.
  4. Proceed by pasting the connection string into your C# code as an argument when calling the OdbcConnection object's constructor.
  5. Before using it we still have to shorten it manually like this: Shorten ODBC connection string to read API data in PowerShell
  6. Our troubles are over, now you should be able to execute the script with no problems.

Write ManagedEngine ServiceDesk Plus (Zoho) data to a file in PowerShell

Save data to a CSV file

Export data to a CSV file so that it can be sliced and diced in Excel:

# Configure connection string and query
$connectionString = "DSN=ManagedEngineServiceDeskPlus(Zoho)DSN"
$query = "SELECT * FROM Customers"

# Instantiate OdbcDataAdapter and DataTable
$adapter = New-Object System.Data.Odbc.OdbcDataAdapter($query, $connectionString)
$table = New-Object System.Data.DataTable

# Fill the table with data
$adapter.Fill($table)

# Export table data to a file
$table | ConvertTo-Csv -NoTypeInformation -Delimiter "`t" | Out-File "C:\Users\john\saved-data.csv" -Force

Save data to a JSON file

Export data to a JSON file so that it can ingested by other processes (use the above script, but change this part):

# Export table data to a file
$table | ConvertTo-Json | Out-File "C:\Users\john\saved-data.json" -Force

Save data to an HTML file

Export data to an HTML file for user-friendly view and easy sharing (use the above script, but change this part):

# Export table data to a file
$table | ConvertTo-Html | Out-File "C:\Users\john\saved-data.html" -Force
Check useful PowerShell cmdlets other than ConvertTo-Csv, ConvertTo-Json, and ConvertTo-Html for other data manipulation scenarios.

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

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

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

  3. 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>';
    

    ZappySys Driver - Create Custom Stored Procedure

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

    ZappySys Driver - Execute Custom Stored Procedure

  5. 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([MY_API_SERVICE], 'EXEC usp_get_orders @fromdate=''1996-07-30''')

    ZappySys Driver - Generate SQL Server Query

  6. Now go to SQL served and execute that query and it will make the API call using stored 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.

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.

  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 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([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 stored procedure and provide you the response.
    ZappySys Driver - Generate SQL Server Query

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
 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
 Delete Request
   [Read more...]
Parameter Description
RequestId
 Test Connection
   [Read more...]
 Get Changes
   [Read more...]
Parameter Description
 Get Change Details
   [Read more...]
Parameter Description
ChangeId
 Get Change Tasks
   [Read more...]
Parameter Description
ChangeId
 Get Change Task Details
   [Read more...]
Parameter Description
ChangeId
TaskId
 Get Change Task Comments
   [Read more...]
Parameter Description
ChangeId
TaskId
 Get Change Task Comment Details
   [Read more...]
Parameter Description
ChangeId
TaskId
CommentId
 Get Change Notes
   [Read more...]
Parameter Description
ChangeId
 Get Change Note Details
   [Read more...]
Parameter Description
ChangeId
NoteId
 Get Change Worklogs
   [Read more...]
Parameter Description
ChangeId
 Get Change Worklog Details
   [Read more...]
Parameter Description
ChangeId
WorklogId
 Get Change Task Worklogs
   [Read more...]
Parameter Description
ChangeId
TaskId
 Get Change Task Worklog Details
   [Read more...]
Parameter Description
ChangeId
TaskId
WorklogId
 Get Problems
   [Read more...]
Parameter Description
 Get Problem Details
   [Read more...]
Parameter Description
ProblemId
 Get Problem Tasks
   [Read more...]
Parameter Description
ProblemId
 Get Problem Task Details
   [Read more...]
Parameter Description
ProblemId
TaskId
 Get Problem Task Comments
   [Read more...]
Parameter Description
ProblemId
TaskId
 Get Problem Task Comment Details
   [Read more...]
Parameter Description
ProblemId
TaskId
CommentId
 Get Problem Notes
   [Read more...]
Parameter Description
ProblemId
 Get Problem Note Details
   [Read more...]
Parameter Description
ProblemId
NoteId
 Get Problem Worklogs
   [Read more...]
Parameter Description
ProblemId
 Get Problem Worklog Details
   [Read more...]
Parameter Description
ProblemId
WorklogId
 Get Problem Task Worklogs
   [Read more...]
Parameter Description
ProblemId
TaskId
 Get Problem Task Worklog Details
   [Read more...]
Parameter Description
ProblemId
TaskId
WorklogId
 Get Projects
   [Read more...]
Parameter Description
 Get Project Details
   [Read more...]
Parameter Description
ProjectId
 Get Project Tasks
   [Read more...]
Parameter Description
ProjectId
 Get Project Members
   [Read more...]
Parameter Description
ProjectId
 Get Project Milestones
   [Read more...]
Parameter Description
ProjectId
 Get Project Milestone Tasks
   [Read more...]
Parameter Description
ProjectId
MilestoneId
 Get Project Task Details
   [Read more...]
Parameter Description
ProjectId
TaskId
 Get Project Task Comments
   [Read more...]
Parameter Description
ProjectId
TaskId
 Get Project Task Comment Details
   [Read more...]
Parameter Description
ProjectId
TaskId
CommentId
 Get Project Notes
   [Read more...]
Parameter Description
ProjectId
 Get Project Note Details
   [Read more...]
Parameter Description
ProjectId
NoteId
 Get Project Worklogs
   [Read more...]
Parameter Description
ProjectId
 Get Project Worklog Details
   [Read more...]
Parameter Description
ProjectId
WorklogId
 Get Project Task Worklogs
   [Read more...]
Parameter Description
ProjectId
TaskId
 Get Project Task Worklog Details
   [Read more...]
Parameter Description
ProjectId
TaskId
WorklogId
 Get Releases
   [Read more...]
Parameter Description
 Get Release Details
   [Read more...]
Parameter Description
ReleaseId
 Get Release Tasks
   [Read more...]
Parameter Description
ReleaseId
 Get Release Task Details
   [Read more...]
Parameter Description
ReleaseId
TaskId
 Get Release Task Comments
   [Read more...]
Parameter Description
ReleaseId
TaskId
 Get Release Task Comment Details
   [Read more...]
Parameter Description
ReleaseId
TaskId
CommentId
 Get Release Notes
   [Read more...]
Parameter Description
ReleaseId
 Get Release Note Details
   [Read more...]
Parameter Description
ReleaseId
NoteId
 Get Release Worklogs
   [Read more...]
Parameter Description
ReleaseId
 Get Release Worklog Details
   [Read more...]
Parameter Description
ReleaseId
WorklogId
 Get Release Task Worklogs
   [Read more...]
Parameter Description
ReleaseId
TaskId
 Get Release Task Worklog Details
   [Read more...]
Parameter Description
ReleaseId
TaskId
WorklogId
 Get Assets
   [Read more...]
Parameter Description
 Get Asset Details
   [Read more...]
Parameter Description
AssetId
 Get Tasks
   [Read more...]
Parameter Description
 Get Task Details
   [Read more...]
Parameter Description
TaskId
 Get Contracts
   [Read more...]
Parameter Description
 Get Contract Details
   [Read more...]
Parameter Description
ContractId
 Get Purchase Orders
   [Read more...]
Parameter Description
 Get Purchase Order Details
   [Read more...]
Parameter Description
PurchaseOrderId
 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
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 PowerShell 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.

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)

List projects    [Read more...]

This example shows how to list projects.

SELECT * FROM Projects

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

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

SELECT * FROM Projects Where id=111112345

List assets    [Read more...]

This example shows how to list assets.

SELECT * FROM Assets

Read asset by ID    [Read more...]

This example shows how to read extended information about an asset

SELECT * FROM Assets Where id=111112345

List purchase orders    [Read more...]

This example shows how to list purchase orders.

SELECT * FROM PurchaseOrders

Read purchase order details by ID    [Read more...]

This example shows how to read extended information about a single purchase order

SELECT * FROM PurchaseOrders Where id=111112345

List changes    [Read more...]

This example shows how to list changes.

SELECT * FROM Changes

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

This example shows how to read extended information about a change

SELECT * FROM Changes Where id=111112345

List contracts    [Read more...]

This example shows how to list contracts.

SELECT * FROM Contracts

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

This example shows how to read extended information about a contract

SELECT * FROM Contracts Where id=111112345

List tasks    [Read more...]

This example shows how to list tasks.

SELECT * FROM Tasks

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

This example shows how to read extended information about a task

SELECT * FROM Tasks Where id=111112345

Conclusion

In this article we discussed how to connect to ManagedEngine ServiceDesk Plus (Zoho) in PowerShell and integrate data without any coding. Click here to Download ManagedEngine ServiceDesk Plus (Zoho) Connector for PowerShell 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 ManagedEngine ServiceDesk Plus (Zoho) Connector for PowerShell Documentation 

More integrations

Other application integration scenarios for ManagedEngine ServiceDesk Plus (Zoho)

Other connectors for PowerShell


Download ManagedEngine ServiceDesk Plus (Zoho) Connector for PowerShell Documentation

  • How to connect ManagedEngine ServiceDesk Plus (Zoho) in PowerShell?

  • How to get ManagedEngine ServiceDesk Plus (Zoho) data in PowerShell?

  • How to read ManagedEngine ServiceDesk Plus (Zoho) data in PowerShell?

  • How to load ManagedEngine ServiceDesk Plus (Zoho) data in PowerShell?

  • How to import ManagedEngine ServiceDesk Plus (Zoho) data in PowerShell?

  • How to pull ManagedEngine ServiceDesk Plus (Zoho) data in PowerShell?

  • How to push data to ManagedEngine ServiceDesk Plus (Zoho) in PowerShell?

  • How to write data to ManagedEngine ServiceDesk Plus (Zoho) in PowerShell?

  • How to POST data to ManagedEngine ServiceDesk Plus (Zoho) in PowerShell?

  • Call ManagedEngine ServiceDesk Plus (Zoho) API in PowerShell

  • Consume ManagedEngine ServiceDesk Plus (Zoho) API in PowerShell

  • ManagedEngine ServiceDesk Plus (Zoho) PowerShell Automate

  • ManagedEngine ServiceDesk Plus (Zoho) PowerShell Integration

  • Integration ManagedEngine ServiceDesk Plus (Zoho) in PowerShell

  • Consume real-time ManagedEngine ServiceDesk Plus (Zoho) data in PowerShell

  • Consume real-time ManagedEngine ServiceDesk Plus (Zoho) API data in PowerShell

  • ManagedEngine ServiceDesk Plus (Zoho) ODBC Driver | ODBC Driver for ManagedEngine ServiceDesk Plus (Zoho) | ODBC ManagedEngine ServiceDesk Plus (Zoho) Driver | SSIS ManagedEngine ServiceDesk Plus (Zoho) Source | SSIS ManagedEngine ServiceDesk Plus (Zoho) Destination

  • Connect ManagedEngine ServiceDesk Plus (Zoho) in PowerShell

  • Load ManagedEngine ServiceDesk Plus (Zoho) in PowerShell

  • Load ManagedEngine ServiceDesk Plus (Zoho) data in PowerShell

  • Read ManagedEngine ServiceDesk Plus (Zoho) data in PowerShell

  • ManagedEngine ServiceDesk Plus (Zoho) API Call in PowerShell