Connect a Zendesk data source
After you set up authentication and store your credentials in an AWS Secrets Manager secret, create the Zendesk data source in your knowledge base. This page describes how to create the data source with the AWS Management Console or the API, followed by a reference for the connector parameters you can configure.
Note
Complete authentication setup first. See Set up OAuth 2.0 Client Credentials authentication for Zendesk. You need the secret ARN.
Create the data source
Connector parameters
The data source configuration uses the following connector parameters. Within
connectorParameters, set both type and
connectorType to ZENDESK and set version
to 1. For the fields that wrap connectorParameters (such as
deletionProtectionConfiguration and
mediaExtractionConfiguration), see Connect a data source.
The following table describes the connectionConfiguration fields.
| Field | Required | Description |
|---|---|---|
secretArn |
Yes | The ARN of the AWS Secrets Manager secret containing your
clientId, clientSecret, and
instanceUrl. |
hostUrl |
Yes | Your Zendesk host URL (for example,
https://).
For multi-brand instances, use the subdomain for the specific brand.
This value must match the instanceUrl in the
secret. |
authType |
Yes | The authentication type. Zendesk supports
OAUTH2. See Authentication method. |
The following table describes the dataEntityConfiguration fields,
which control the entities that the connector crawls. In the console, articles and
their attachments are combined into a single Articles (includes
attachments) option, but the API exposes them as separate
fields.
| Field | Required | Description |
|---|---|---|
crawlArticles |
Yes | Whether to crawl help center articles. |
crawlArticleAttachments |
Yes | Whether to crawl attachments on help center articles. |
crawlCommunityPosts |
Yes | Whether to crawl community posts. |
The following table describes the optional filterConfiguration
fields, which scope the crawl.
| Field | Required | Description |
|---|---|---|
articleFilter |
No | Scopes article crawling. Contains
inclusionCategoryIds (a list of help center category
IDs) and inclusionSectionIds (a list of section IDs).
These IDs are numeric and appear in the help center URL when you view
a category or section (for example, the category ID in
https://
is 200420805). |
communityPostFilter |
No | Scopes community post crawling. Contains
inclusionTopicIds (a list of community topic IDs). A
topic ID is numeric and appears in the URL when you view a community
topic (for example, the topic ID in
https://
is 360001234567). |
inclusionLabelNames |
No | A list of label names. The connector syncs only articles and
community posts that match these labels. Labels are keywords or tags
applied to articles and community posts, found at the bottom of any
article or post in the editor. For example, if an article is tagged
billing and a community post is tagged FAQ,
entering those labels syncs only content matching those tags. Use
alongside the article and community post filters to further refine
synced content. |
maxFileSizeInMegaBytes |
No | Maximum size, in megabytes, of any single file the connector
ingests. Provide as a numeric string (for example,
"10240"). |
Next steps
After you create the data source, sync it to ingest content into your knowledge base. For details, see Sync a data source. Because Zendesk doesn't support document-level access control, all authenticated users who can query the knowledge base can see all crawled content.