Zendesk is retiring API tokens. Create an OAuth client as above, connect Zendesk again with it, then disconnect the old connection.
Connect Zendesk
Connect Zendesk so Fern reads your solved and closed Zendesk tickets and finds the questions your docs don't answer.
Owners and admins can connect integrations.
What Fern reads
Solved and closed tickets, read-only. Fern never replies in Zendesk or changes a ticket.
Fern reads the last 90 days of solved and closed tickets first, then keeps reading new ones. They show up as questions in Reporting > Topics, where Fern can draft the article your docs are missing. More on what Fern does with them in Use your support tools as a source.
Connect it
Zendesk no longer issues API tokens, so Ferndesk connects with an OAuth client you create in Zendesk:
In Zendesk Admin Center, add an OAuth client under Apps and integrations > APIs > OAuth clients. Set its client kind to Confidential and allow the
readscope, or leave the scopes empty.Copy the identifier and the secret. Zendesk shows the secret only once.
Connect it from Integrations > Help desks. Enter your Zendesk subdomain with the identifier and secret.
Good to know
Connecting brings in tickets, not articles. To copy your Zendesk help center into Ferndesk, see Switch from another tool.
You can connect more than one Zendesk account. Add each one as its own connection.
To hand widget chats to Zendesk, see Use the widget with another chat tool.
Disconnecting stops the import and deletes the conversations Fern imported from that connection, with the topics built from them.
Common questions
I connected Zendesk with an API token
Connecting fails with "Zendesk didn't accept these credentials"
Check the subdomain, and copy the identifier and secret again. The client kind must be Confidential.
The connection says Sync failed or Sign-in expired
Zendesk refused the OAuth client secret. Check it in Zendesk, then replace it under Configuration on the connection's page.