> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/integrations/zendesk-knowledge.md).

# Zendesk Knowledge

Connect your Zendesk Help Center so the Agent's Knowledge can learn from your published Zendesk Guide articles.

The Zendesk Knowledge integration connects your Zendesk Help Center to the Agent's Knowledge. You sign in with Zendesk to sync your Knowledge articles into Jimo, then you train the Agent on all your published articles or on a selection.

The Agent learns from Help Center and Guide articles only. Zendesk Support tickets are not used as a source.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2Fx2a7rVEfEmdwRXav1MW6%2FF2-58-zendesk-knowledge-flow.png?alt=media&amp;token=5f5b05b5-3be4-4ac6-ad75-38419ca85f18" alt="Published Zendesk Help Center articles go through the Zendesk Knowledge integration, set up in Settings > Integrations with subdomain, email and API token, into a Knowledge source the Agent is trained on. Support tickets are not read"><figcaption></figcaption></figure>

## Before you start

* A Zendesk account with Help Center or Guide enabled, and published articles.
* A Zendesk agent or admin account to sign in with. An end user account cannot be used.
* A Jimo role with access to the Integrations settings. See [Integration setup](https://help.usejimo.com/docs/integrations/integration-setup.md).

## Connect in Jimo

{% stepper %}
{% step %}

### Open the integration

In [Settings > Integrations](https://i.usejimo.com/settings/integrations), hover the **Zendesk Knowledge** card and click **Enable** to open its settings page. You do this once per project.
{% endstep %}

{% step %}

### Sign in with Zendesk

Under **Sign in with Zendesk**, click **Connect Zendesk** and authorise Jimo from your Zendesk account. Sign in as an agent or admin: an end user cannot write the private notes this integration adds to tickets.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FlzlboajgOLTOIanhB1IF%2FF2-16-zendesk-knowledge.png?alt=media&amp;token=0211b8d6-f2b7-494c-8409-88124269db58" alt="Zendesk Knowledge settings in Jimo. A: Connect Zendesk, under Sign in with Zendesk. B: the Subdomain field and C: the Email field, under Subdomain and Email. D: the Token field, under API token. E: Test connection, under Verify your connection."><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Test the connection

Under **Verify your connection**, click **Test connection**. Run it after you connect or save credentials, and before you train content. A successful test means Jimo can reach your Help Center.
{% endstep %}
{% endstepper %}

## Legacy setup: subdomain, email and API token

Setups that use a Zendesk subdomain, email and API token keep working until Zendesk switches API tokens off on 30 April 2027. Move to **Sign in with Zendesk** before that date. Until then, the settings page keeps the **Subdomain and Email** and **API token** sections for these setups.

{% hint style="warning" %}
Never share API tokens in tickets, chat or email. Treat them like passwords.
{% endhint %}

#### Subdomain

The prefix of your Zendesk URL, without `.zendesk.com`. For `https://jimosupport.zendesk.com`, the subdomain is `jimosupport`.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2Fvt90M8XANyxq41SDXIE7%2Fimage.png?alt=media&amp;token=50a7aaee-7208-48e3-b231-37f7b29e8b3a" alt="Zendesk URL with the subdomain highlighted"><figcaption></figcaption></figure>

#### Email

The email of the Zendesk account that authenticates the API calls, for example `agent@company.com`. Follow your organization's access policy.

#### API token

In Zendesk, go to **Admin > Apps and integrations > APIs > Zendesk API > API tokens**, or the equivalent path in your Zendesk Admin. Create a token or copy an existing one, and store it safely. If API tokens are turned off in your workspace, Zendesk Admin shows a warning: turn them on first.

#### Save them in Jimo

Under **Subdomain and Email**, enter the subdomain and the email, then click **Save**. Under **API token**, enter the token, then click **Save** again. Once saved, the token shows as a masked placeholder. Then run **Test connection**.

## Train the Agent on your articles

With the integration connected, add Zendesk Knowledge as a source in the Agent's Knowledge, then choose the scope:

* **All articles:** every published Help Center article.
* **Specific articles:** search and select the articles you want.

See [Sources](https://help.usejimo.com/docs/experiences/agent/knowledge/sources.md) for how sources are trained and refreshed.

**From your assistant:** with the [MCP](https://help.usejimo.com/docs/integrations/mcp.md) connected, ask "Train the Agent on all published articles of our Zendesk help center". The assistant shows how many articles it will read before it adds them. More prompts in [What to ask](https://help.usejimo.com/docs/integrations/mcp/what-to-ask.md).

## Verify

* **Test connection** succeeds on the integration settings page.
* The Zendesk source appears in [Sources](https://help.usejimo.com/docs/experiences/agent/knowledge/sources.md) and reaches the Trained status.

## Maintain the connection

#### Rotate the API token

Legacy setups only. Create or copy the new token in Zendesk, replace the saved token in the Zendesk Knowledge settings in Jimo, save, and run **Test connection** again.

#### Disconnect

Disconnect from the integration settings in Jimo. Jimo stops reading Zendesk content until you configure the integration again.

## Troubleshooting

#### Test connection fails

If you signed in with Zendesk, click **Connect Zendesk** again and sign in as an agent or admin, not as an end user.

For a legacy setup, check, in this order:

* The subdomain: the prefix only, without `.zendesk.com`.
* The email of the Zendesk user.
* The API token: invalid, expired, or changed in Zendesk but not in Jimo.
* The Zendesk user's permissions: it needs access to Help Center content through the API.

## Related

* [Knowledge](https://help.usejimo.com/docs/experiences/agent/knowledge.md)
* [Sources](https://help.usejimo.com/docs/experiences/agent/knowledge/sources.md)
* [Custom answers](https://help.usejimo.com/docs/experiences/agent/knowledge/custom-answers.md)
