SharePoint Online Connectors

ZappySys connectors for SharePoint Online provide read / write capability inside your app (see list below), using these drag and drop , high performance connectors you can perform many SharePoint Online operations without any coding. You can use this connector to integrate SharePoint Online API 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)

Documentation 

Video Tutorial - SharePoint Online Connectors - REST API Integration

Click on your App below to get started with SharePoint Online Integration

Choose your App / Scenario for which you like to integrate SharePoint Online

API Actions for SharePoint Online

SharePoint Online Connectors 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 Main Site
 List Sites
 List Drives
Parameter Description
SiteId Specify a site
 Read Drive
Parameter Description
SiteId Specify a site
DriveId Specify a drive
 List Folders
Parameter Description
SiteId Specify a site
DriveId Specify a drive
 List Files
Parameter Description
SiteId Specify a site
DriveId Specify a drive
 List Excel Files
Parameter Description
SiteId Specify a site
DriveId Specify a drive
 List SharePoint Lists
Parameter Description
SiteId Specify a site
 Read List Fields
Parameter Description
SiteId Specify a site
ListId Specify a list id to search items for
 Read List
Parameter Description
SiteId Specify a site
ListId Specify a list id to search items for
 Read List Items
Parameter Description
SiteId Specify a site
ListId Specify a list id to search items for
 Read List Item (By ID)
Parameter Description
SiteId Specify a site
ListId Specify a list id to search items for
ListItemId Specify a list item id (Record ID)
 Create List Item
Parameter Description
SiteId Specify a site
ListId Specify a list id to search items for
 Update List Item
Parameter Description
SiteId Specify a site
ListId Specify a list id to search items for
ListItemId Specify a list item id
 Delete List Item
Parameter Description
SiteId Specify a site
ListId Specify a list id to search items for
ListItemId Specify a list item id
 List Excel Worksheets
Parameter Description
SiteId Specify a site
DriveId Specify a drive Id to search items in
FileId Specify a drive Id to search items in
 Read Excel Worksheet
Parameter Description
SiteId Specify a site
DriveId Specify a drive Id
FileId Specify a file id
SheetId Specify a sheet name
Range
 Download File
Parameter Description
SiteId Specify a site
DriveId Specify a drive Id
FileId Specify a file id
 Upload File
Parameter Description
SiteId Specify a site
DriveId Specify a drive Id
DiskFilePath Specify a disk file path
SharePointFilePath Specify SharePoint file path
 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. 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