Zendesk
Zendesk is a unified customer service platform. It features a common user interface, single login, and a platform for sharing customer data.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 168: Supported operations for Users
Create User |
POST |
Update User |
PUT |
Delete User |
DELETE |
Get User |
GET |
Get All Users |
GET |
Get All Users with Pagination |
GET |
Groups
Table 169: Supported operations for Users
Create Group |
POST |
Update Group |
PUT |
Delete Group |
DELETE |
Get Groups |
GET |
Get All Groups |
GET |
Get All Users with Pagination |
GET |
Update Membership |
PUT |
Mandatory fields
Users
Groups
DisplayName
NOTE: Additional features supported: Zendesk connector supports attribute selection for the response based on the attributes mentioned in the query parameters ?attributes=.
User and Group mapping
The user and group mappings are listed in the tables below.
Table 170: User mapping
Id |
id |
UserName |
email |
DisplayName |
name |
Timezone |
time_zone |
Locale |
locale |
PhoneNumbers[].Value |
phone |
Emails[].Value |
email |
Active |
active |
Meta.Created |
created_at |
Meta.LastModified |
updated_at |
Groups
Table 171: Groups mapping
Id |
id |
DisplayName |
name |
Meta.Created |
created_at |
Meta.LastModified |
updated_at |
Connector limitations
-
A user with Agent role only can be added to group membership.
-
Get resource by pagination will always return the resources in multiples of hundred. For example, if the count is specified as 126, 200 records are returned.
-
If any value for startIndex is passed when using get resources by pagination parameter, the result from the connector is always the nearest 100 records from the requested number.
-
Users can be deleted multiple times as the cloud application supports soft delete.
-
APIs are rate limited and for more details refer Usage limits.
Supervisor configuration parameters
Zendesk is a unified customer service platform. It features a common user interface, single login, and a platform for sharing customer data.
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 168: Supported operations for Users
Create User |
POST |
Update User |
PUT |
Delete User |
DELETE |
Get User |
GET |
Get All Users |
GET |
Get All Users with Pagination |
GET |
Groups
Table 169: Supported operations for Users
Create Group |
POST |
Update Group |
PUT |
Delete Group |
DELETE |
Get Groups |
GET |
Get All Groups |
GET |
Get All Users with Pagination |
GET |
Update Membership |
PUT |
Mandatory fields
Users
Groups
DisplayName
NOTE: Additional features supported: Zendesk connector supports attribute selection for the response based on the attributes mentioned in the query parameters ?attributes=.
User and Group mapping
The user and group mappings are listed in the tables below.
Table 170: User mapping
Id |
id |
UserName |
email |
DisplayName |
name |
Timezone |
time_zone |
Locale |
locale |
PhoneNumbers[].Value |
phone |
Emails[].Value |
email |
Active |
active |
Meta.Created |
created_at |
Meta.LastModified |
updated_at |
Groups
Table 171: Groups mapping
Id |
id |
DisplayName |
name |
Meta.Created |
created_at |
Meta.LastModified |
updated_at |
Connector limitations
-
A user with Agent role only can be added to group membership.
-
Get resource by pagination will always return the resources in multiples of hundred. For example, if the count is specified as 126, 200 records are returned.
-
If any value for startIndex is passed when using get resources by pagination parameter, the result from the connector is always the nearest 100 records from the requested number.
-
Users can be deleted multiple times as the cloud application supports soft delete.
-
APIs are rate limited and for more details refer Usage limits.
Supported objects and operations
Zendesk is a unified customer service platform. It features a common user interface, single login, and a platform for sharing customer data.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Users
Table 168: Supported operations for Users
Create User |
POST |
Update User |
PUT |
Delete User |
DELETE |
Get User |
GET |
Get All Users |
GET |
Get All Users with Pagination |
GET |
Groups
Table 169: Supported operations for Users
Create Group |
POST |
Update Group |
PUT |
Delete Group |
DELETE |
Get Groups |
GET |
Get All Groups |
GET |
Get All Users with Pagination |
GET |
Update Membership |
PUT |
Mandatory fields
Users
Groups
DisplayName
NOTE: Additional features supported: Zendesk connector supports attribute selection for the response based on the attributes mentioned in the query parameters ?attributes=.
User and Group mapping
The user and group mappings are listed in the tables below.
Table 170: User mapping
Id |
id |
UserName |
email |
DisplayName |
name |
Timezone |
time_zone |
Locale |
locale |
PhoneNumbers[].Value |
phone |
Emails[].Value |
email |
Active |
active |
Meta.Created |
created_at |
Meta.LastModified |
updated_at |
Groups
Table 171: Groups mapping
Id |
id |
DisplayName |
name |
Meta.Created |
created_at |
Meta.LastModified |
updated_at |
Connector limitations
-
A user with Agent role only can be added to group membership.
-
Get resource by pagination will always return the resources in multiples of hundred. For example, if the count is specified as 126, 200 records are returned.
-
If any value for startIndex is passed when using get resources by pagination parameter, the result from the connector is always the nearest 100 records from the requested number.
-
Users can be deleted multiple times as the cloud application supports soft delete.
-
APIs are rate limited and for more details refer Usage limits.
Mandatory fields
Zendesk is a unified customer service platform. It features a common user interface, single login, and a platform for sharing customer data.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 168: Supported operations for Users
Create User |
POST |
Update User |
PUT |
Delete User |
DELETE |
Get User |
GET |
Get All Users |
GET |
Get All Users with Pagination |
GET |
Groups
Table 169: Supported operations for Users
Create Group |
POST |
Update Group |
PUT |
Delete Group |
DELETE |
Get Groups |
GET |
Get All Groups |
GET |
Get All Users with Pagination |
GET |
Update Membership |
PUT |
Users
Groups
DisplayName
NOTE: Additional features supported: Zendesk connector supports attribute selection for the response based on the attributes mentioned in the query parameters ?attributes=.
User and Group mapping
The user and group mappings are listed in the tables below.
Table 170: User mapping
Id |
id |
UserName |
email |
DisplayName |
name |
Timezone |
time_zone |
Locale |
locale |
PhoneNumbers[].Value |
phone |
Emails[].Value |
email |
Active |
active |
Meta.Created |
created_at |
Meta.LastModified |
updated_at |
Groups
Table 171: Groups mapping
Id |
id |
DisplayName |
name |
Meta.Created |
created_at |
Meta.LastModified |
updated_at |
Connector limitations
-
A user with Agent role only can be added to group membership.
-
Get resource by pagination will always return the resources in multiples of hundred. For example, if the count is specified as 126, 200 records are returned.
-
If any value for startIndex is passed when using get resources by pagination parameter, the result from the connector is always the nearest 100 records from the requested number.
-
Users can be deleted multiple times as the cloud application supports soft delete.
-
APIs are rate limited and for more details refer Usage limits.