...
You enter a meaningful name for the instance and then select "Zendesk Instance URL" from the Web API drop-down list. Then enter your installation's Zendek subdomain and the Server Variables.
Some variables from Zendesk cannot be mapped and therefore server variables must be used for this scope. The needed values are already defined in the installation but they should be overridden with correct values by using the provided text boxes. Below chapters include all defined variables along with an explanation and example for each one.
...
A valid email address and apikey Api key must be set in the corresponding textbox in order for BSS to be able to authenticate itself with Zendesk. On ready-to-use instance only Api token authentication method of Zendesk is supported.
Format of username should be email_address/token and for password the generated apiKey must be used
Check Authorization
...
A valid x-authenticationfull URL should be filled in the JSON transformation in order to be able to check Authentication. The URL must be /organizations/get 
| Rw ui textbox macro | ||
|---|---|---|
| ||
Check Authorization is only available for MS Dynamics with ODataV4 enabled. |
Synchronization Options
...
This table presents all available operations for the supported entities. In order to be able to sync an entity, the corresponding action must be checked.
...
| Push | Pull | ||||
|---|---|---|---|---|---|
| Contact | - | - | |||
| Case | |||||
| rw-ui-text-box | size | medium|
|---|---|---|
| textbox-macro | ||
| ||
Only the following values are allowed from Zendesk API: Zendesk Case status: open, pending, hold, solved or closed Zendesk Type: problem, incident, question or task Zendesk Priority: urgent, high, normal, or low |
...
Below is an example of Case Priority lookup between BSS and Zendesk
| rw-ui-text-box | size | medium|
|---|---|---|
| textbox-macro | ||
| ||
Zendesk lookup |
...