Zendesk Help Center
Keep Zendesk Help Center articles in sync for agents
- Publisher
- By Connic
- Syncs
- Articles, Translations, Labels and sections
- Set up in
- Retrieval → Sources
- Documentation
- Retrieval Docs
How the Zendesk Help Center source works
Support teams keep their best answers in the Zendesk Help Center. The Zendesk source syncs those articles into Connic retrieval, so support and back-office agents answer from the published article instead of paraphrasing it.
Connect with the Zendesk subdomain and the locales to sync. Articles are read through the Help Center API instead of the rendered site, so custom domains and bot protection in front of the help center do not get in the way. Public help centers need no credentials, and an agent email with an API token adds articles restricted to signed-in users. Every article becomes one entry per locale and refreshes on the configured schedule.
What gets synced
- Articles
- Published article bodies, converted to clean text before chunking. Drafts are skipped.
- Translations
- Each configured locale is synced separately, so agents can answer in the customer's language.
- Labels and sections
- Article labels, section, and locale are kept in entry metadata so retrieval can be filtered.
Set up the Zendesk Help Center source
Add the source under Retrieval → Sources in the environment your agents run in. Each environment keeps its own sources.
Enter the Zendesk subdomain, e.g. example for example.zendesk.com. Help centers on a custom domain still use this subdomain.
List the help center locales to sync, e.g. en-us, de.
For a public help center, leave the email and API token empty.
To include articles restricted to signed-in users, create an API token in Admin Center under Apps and integrations → APIs, and enter it with the email of an agent who can see those articles.
Optionally limit the sync to category or section IDs, shown in the URL of each category or section page.
Configuration, in depth
Every available control for connecting Zendesk Help Center to a project.
Connection
- Subdomain*
- The Zendesk subdomain or its zendesk.com URL.
- Agent email
- Optional. Email of the agent the API token belongs to. Leave empty for a public help center.
- API token
- Optional. Zendesk API token. The sync only reads articles this agent can see.
Content scope
- Locales*
- Comma-separated help center locales to sync.
- Category IDs
- Only sync articles in these categories, comma-separated. Leave empty to sync the whole help center.
- Section IDs
- Only sync articles in these sections, comma-separated. Combines with the category IDs.
Sync behavior
Where synced content lands and how often it refreshes.
- Target namespace
- Retrieval namespace the synced entries are filed under. Use dots to nest, e.g. sources.notion.
- Sync interval
- How often the source is checked for changes. Each run only reprocesses content that changed.
- When content is deleted at the source
- Articles deleted, unpublished, or moved out of scope in Zendesk can be removed from the retrieval on the next sync, or kept as they were last synced.
Search it from an agent
Agents search synced content with the retrieval_query tool. A small tool that pins the namespace keeps an agent to this source.
from connic.tools import retrieval_query
async def search_zendesk(question: str) -> dict:
return await retrieval_query(
question, namespace="sources.zendesk"
)version: "1.0"
name: support-agent
type: llm
model: connic/gemini-3.7-flash
system_prompt: |
Answer only from what search_zendesk returns.
tools:
- knowledge.search_zendeskZendesk Help Center retrieval source FAQ
More retrieval sources
Notion
By ConnicConnect a Notion workspace and keep pages and databases synced in retrieval. Agents retrieve the current version, not a stale export.
Auto-syncSuperhuman Docs (Coda)
By ConnicSync Superhuman Docs pages and table rows into retrieval, so agents answer from the doc the team actually edits.
Auto-syncWebsite Crawler
By ConnicPoint the crawler at documentation, a help center, or a blog. Pages are converted to clean markdown and re-crawled on the configured schedule.
Auto-sync