Zendesk support

Last updated date:

Connect, reconnect, and troubleshoot Zendesk without sharing credentials or customer content through support channels.

1. Before you start

  • Choose the exact Zendesk subdomain and OAuth user whose support records Seedling should read.
  • Create a Zendesk OAuth client and complete the authorization-code flow with read access and refresh-token support.
  • Use a dedicated integration identity when organizational audit and lifecycle ownership require it.
  • Do not send Zendesk credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Zendesk OAuthZendesk's official OAuth authentication and token guidance.

2. Connect Zendesk

  1. Create the Zendesk OAuth client and obtain the access and refresh tokens for the intended subdomain.
  2. In Seedling, open Connections, select Zendesk, and choose personal or workspace scope.
  3. Enter the normalized subdomain without protocol or .zendesk.com, then paste both tokens.
  4. Connect, confirm the verified Zendesk account, and allow ticket and Help Center synchronization to complete.

3. Authorization and connection problems

Subdomain rejected
Enter only the account prefix, such as company, and confirm the OAuth tokens were issued by that same Zendesk account.
Refresh token missing or expired
Repeat the authorization-code flow with refresh-token support and replace both tokens.
Ticket or article forbidden
Confirm the OAuth user retains the required Zendesk role, group, brand, ticket, and Help Center permissions.

4. Missing or delayed data

  1. Confirm the OAuth user can open the affected ticket, internal comment, attachment, or Help Center article in Zendesk.
  2. Check ticket groups, organizations, brands, restricted Help Center sections, archived articles, and role changes.
  3. Confirm the record remains in the verified subdomain and the refresh token remains valid.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Complete a new Zendesk authorization-code flow for the same subdomain, OAuth client, read scope, and intended user.
  2. Replace both access and refresh tokens on the exact Seedling connection.
  3. Revoke the old OAuth token after Seedling verifies the replacement.