Zoho CRM

this connector integrates zoho crm's rest api with swimlane turbine asset setup the connector can be authenticated in one of the following two ways bearer token authentication, which requires an url and an api token oauth 2 0 client credentials flow, which requires the following inputs url api token url client id client secret redirect uri code (authorization code) capabilities this connector provides the following capabilities get records notes for more information on zoho crm is found at https //www zoho com/en in/crm/ api documentation link for generating the authorization code, please refer https //www zoho com/crm/developer/docs/api/v5/auth request html https //www zoho com/crm/developer/docs/api/v5/get records html configurations http bearer authentication authenticates using bearer token such as a jwt, etc configuration parameters parameter description type required url a url to the target host string required token the api key, token, etc string required verify ssl verify ssl certificate boolean optional http proxy a proxy to route requests through string optional oauth 2 0 client credentials authenticates using oauth 2 0 client credentials configuration parameters parameter description type required url a url to the target host string required api token url api token url string required token url string optional redirect uri redirect uri string required client id the client id provided in the developer portal string required client secret the client secret provided in the developer portal string required code grant token string required verify ssl verify ssl certificate boolean optional http proxy a proxy to route requests through string optional actions get records retrieve the records that match your search criteria endpoint url /crm/v5/leads method get input argument name type required description parameters fields string required to list all the module records with respect to fields note that you can include a maximum of 50 field api names in this parameter parameters cvid number optional to get the list of records based on custom views note that you cannot use this param with the "sort by" param you can get custom view id from custom view meta api parameters ids string optional to retrieve specific records based on their unique id parameters page number optional to get the list of records from the respective pages the default value is 1 note that you cannot use this param with the "page token" param parameters per page number optional to get the list of records available per page the default and the maximum possible value is 200 parameters page token string optional you can use the "page" param to fetch up to 2000 records without "page token" to fetch more than 2000 records, you must include the "page token" param in the request this param takes the value from the key "next page token" in the response of the first get records call note that this token value is user specific if you use another user's token, the system throws an error note that you cannot use this param with the "page" param parameters sort order string optional to sort the available list of records in either ascending or descending order parameters sort by string optional to sort the records based on the fields id, created time, and modified time the default value is 'id' note that you cannot use this param with the "cvid" param parameters converted string optional to get the list of converted records default value is false possible values are as follows 1 true get only converted records, 2 false get only non converted records, both get all records parameters territory id number optional to get the list of records based on the territory parameters include child boolean optional to include records from the child territories default value is false possible values are 1 true includes child territory records, 2 false does not include child territory records input example {"parameters" {"fields" "last name,email,converted s,converted date time","cvid" 12345678,"ids" "4150868000001944196","page" 1,"per page" 5,"page token" "c8582xx9e7c7","sort order" "desc","sort by" "id","converted" "false","territory id" 1234567890,"include child"\ false}} output parameter type description status code number http status code of the response reason string response reason phrase data array response data data converted date time string response data data email object response data data last name string response data data id string response data data converted s boolean response data info object output field info info call boolean output field info call info per page number output field info per page info next page token string output field info next page token info count number count value info sort by string output field info sort by info page number output field info page info previous page token object output field info previous page token info page token expiry string output field info page token expiry info sort order string output field info sort order info email boolean output field info email info more records boolean output field info more records output example {"status code" 200,"response headers" {"content length" "140","accept" "application/json","content type" "application/json","date" "wed, 13 dec 2023 20 37 23 gmt"},"reason" "ok","json body" {"data" \[{"converted date time" "2022 11 21t15 12 13+05 30","email"\ null,"last name" "test8000","id" "3652397000009851001","converted s"\ true},{"converted date time" "2022 11 21t15 12 13+05 30","email"\ null,"last name" "test7000","id" "3652397000009850001","converted s"\ true},{"converted date time" "2022 11 response headers header description example accept http response header accept application/json content length the length of the response body in bytes 140 content type the media type of the resource application/json date the date and time at which the message was originated wed, 13 dec 2023 20 37 23 gmt