The ZenDesk Connector is available for any ZenDesk instance that uses version 2 of the REST API.
The user must have full/admin level access to the ZenDesk instance.
There are 2 ways to connect to ZenDesk. However, the authentication method depends on whether you have OAuth enabled for ZenDesk or not. This Connector is forZenDesk instances. It interacts with ZenDesk through the REST API version 2
- Username: Zendesk username
- Password: Zendesk password
- Zendesk Sub Domain: Zendesk Sub Domain (without the .zendesk.com attached (e.g. simflofy.zendesk.com becomes simflofy))
Here is ZenDesk's document for registering an application. You will generate the ClientId and Secret from this process
- Name: Unique name for this auth connector.
- Client ID: App Client ID of the app Zendesk will Authenticate with.
- Client Secret: App Client Secret Key for the app Zendesk will Authenticate with.
- ZenDesk Sub Domain: Zendesk Sub Domain (without the .zendesk.com attached (e.g. simflofy.zendesk.com becomes simflofy))
- Name: Unique Name for the Discovery Connection to identify it in the UI.
- Authentication Connection: The Zendesk authentication connection
- Ignore Types (comma delimited list): Not applicable, as the connector only returns tickets
- Connection Name: This is a unique name given to the connector instance upon creation.
- Description: A description of the connector to help identify it better.
- Authentication Connector - The Authentication connector to use based on your Zendesk instance type
The Zendesk connector only has job configuration while in repository (read) mode. In output mode it will push tickets to the authenticated subdomain.
Do not include date ranges as those are taken in by the start/end date of the Job configuration in the Details tab.
- ZenDesk Query: Written in the Zendesk Query Language
Content Service Connection
Content Service Connection is not available for Zendesk