chore(source-zendesk-support, source-zendesk-chat, source-zendesk-talk): add missing external documentation URLs

[devin-ai-integration]

What

Adds missing externalDocumentationUrls entries to the three Zendesk source connectors so API-deprecation monitoring has vendor changelog, auth, and removal-announcement coverage for each of them.

Found while running the API Deprecation Monitoring playbook for the Zendesk API family (requested by Devin Bot / Danylo Jablonski, gl_danylo.jablonski@airbyte.io). source-zendesk-chat and source-zendesk-talk only listed a changelog and a (mostly empty) "Developer updates" section — no API reference, auth guide, or deprecation page. None of the existing URLs 404, so nothing was removed.

Resolves https://github.com/airbytehq/oncall/issues/13224
Resolves https://github.com/airbytehq/oncall/issues/13225

• https://github.com/airbytehq/oncall/issues/13224
• https://github.com/airbytehq/oncall/issues/13225

How

Metadata-only edits. Added, per connector:

• source-zendesk-support: Zendesk feature removal announcements (api_deprecations)
• source-zendesk-chat: Chat API reference (api_reference), Chat authentication (authentication_guide), feature removal announcements (api_deprecations), status page (status_page)
• source-zendesk-talk: Talk API reference (api_reference), Zendesk authentication (authentication_guide), feature removal announcements (api_deprecations), rate limits (rate_limits), status page (status_page)

The removal-announcements page (https://support.zendesk.com/hc/en-us/articles/4408843026714-What-is-being-removed-updated-April-2026) is the vendor's canonical feature-removal table; it is where the API-token removal (all tokens dead 2027-04-30) and similar sunsets are tracked.

Review guide

1. airbyte-integrations/connectors/source-zendesk-{support,chat,talk}/metadata.yaml

All added URLs were verified to return HTTP 200. No dockerImageTag bump or docs changelog entry, matching prior metadata-only external-docs PRs (#78389, #82265, #83262).

User Impact

None — no connector behavior, spec, or version change.

Can this PR be safely reverted and rolled back?

• YES 💚
• NO ❌

Link to Devin session: https://app.devin.ai/sessions/8e8c24de9ec24f29b52fc17cda363f18

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[octavia-bot]

Note

📝 PR Converted to Draft

More info...

Thank you for creating this PR. As a policy to protect our engineers' time, Airbyte requires all PRs to be created first in draft status. Your PR has been automatically converted to draft status in respect for this policy.

As soon as your PR is ready for formal review, you can proceed to convert the PR to "ready for review" status by clicking the "Ready for review" button at the bottom of the PR page.

To skip draft status in future PRs, please include [ready] in your PR title or add the skip-draft-status label when creating your PR.

[github-actions]

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

💡 Show Tips and Tricks

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

• 🛠️ Quick Fixes
  • /format-fix - Fixes most formatting issues.
  • /bump-version - Bumps connector versions, scraping changelog description from the PR title.
    • Bump types: patch (default), minor, major, major_rc, rc, promote.
    • The rc type is a smart default: applies minor_rc if stable, or bumps the RC number if already RC.
    • The promote type strips the RC suffix to finalize a release.
    • Example: /bump-version type=rc or /bump-version type=minor
  • /bump-progressive-rollout-version - Alias for /bump-version type=rc. Bumps with an RC suffix and enables progressive rollout.
• ❇️ AI Testing and Review (internal link: AI-SDLC Docs):
  • /ai-prove-fix - Runs prerelease readiness checks, including testing against customer connections.
  • /ai-canary-prerelease - Rolls out prerelease to 5-10 connections for canary testing.
  • /ai-review - AI-powered PR review for connector safety and quality gates.
• 📝 AI Documentation:
  • /ai-docs-review - AI-powered documentation review for PRs with connector changes.
  • /ai-create-docs-pr - Creates a documentation PR for connector changes, stacked on the current PR.
• 🚀 Connector Releases:
  • /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
  • /enable-autopilot-rollouts - Enables autopilot progressive rollouts for the modified connector(s) in the PR, remediating "autopilot rollouts not enabled for {connector-name}" auto-merge blockers. Sets defaultRolloutMode: autopilot and enableProgressiveRollout: true, preserving any existing autopilotConfig.
    • Optional args: connector=<CONNECTOR_NAME> (defaults to the modified connectors in the PR), strategy=fast|slow|default (defaults to fast).
    • Example: /enable-autopilot-rollouts or /enable-autopilot-rollouts connector=source-faker strategy=slow
• ☕️ JVM connectors:
  • /update-connector-cdk-version connector=<CONNECTOR_NAME> - Updates the specified connector to the latest CDK version.
    Example: /update-connector-cdk-version connector=destination-bigquery
• 🐍 Python connectors:
  • /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
  • /poe source example lock - Alias for /poe connector source-example lock.
  • /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
  • /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.
• ⚙️ Admin commands:
  • /force-merge reason="<REASON>" - Force merges the PR using admin privileges, bypassing CI checks. Requires a reason.
    Example: /force-merge reason="CI is flaky, tests pass locally"

📚 Show Repo Guidance

Helpful Resources

• Breaking Changes Guide - Breaking changes, migration guides, and upgrade deadlines
• Developing Connectors Locally
• Managing Connector Secrets
• On-Demand Regression Tests
• #connector-ci-issues
• #connector-publish-updates
• #connector-build-statuses

📝 Edit this welcome message.

[github-actions]

Note

Autopilot progressive rollouts are not enabled for the following modified connector(s):

• source-zendesk-chat
• source-zendesk-support
• source-zendesk-talk

This is a courtesy heads-up only — it does not block merge or fail any check.
To enable automatic progressive rollouts for the connector(s) above, comment
/enable-autopilot-rollouts on this PR. This sets defaultRolloutMode: autopilot
and enableProgressiveRollout: true in each connector's metadata.yaml,
preserving any existing autopilotConfig.

[github-actions]

source-zendesk-talk Connector Test Results

31 tests   27 ✅  12s ⏱️
 2 suites   4 💤
 2 files     0 ❌

Results for commit 9431e69.

[github-actions]

source-zendesk-chat Connector Test Results

45 tests   41 ✅  32s ⏱️
 2 suites   4 💤
 2 files     0 ❌

Results for commit 9431e69.

[github-actions]

source-zendesk-support Connector Test Results

224 tests   218 ✅  8m 10s ⏱️
  2 suites    5 💤
  2 files      1 ❌

For more details on these failures, see this check.

Results for commit 9431e69.

[devin-ai-integration]

CI status on this metadata-only change:

source-zendesk-{support,chat,talk} Pre-Release Checks — failing: The dockerImageTag in metadata.yaml was not incremented. Intentional — this PR changes only externalDocumentationUrls, so bumping dockerImageTag would trigger three connector releases for a documentation change. Precedent: #83262 (also an externalDocumentationUrls-only change) was merged on 2026-07-30 with the same source-amazon-ads Pre-Release Checks failure as its only failing check.

Test source-zendesk-support Connector — failing on expired credentials, not on this diff. The logs show 401 ... 'invalid_token' / The access token provided is expired, revoked, malformed or invalid for other reasons. across every stream (tickets, users, ticket_events, ticket_metrics, ticket_skips, ...). The diff touches no code or spec, so this looks like the integration-test OAuth credential for Zendesk needing to be refreshed — worth noting that Zendesk began enforcing OAuth access/refresh token expiration for global OAuth clients on 2026-02-02 (see https://github.com/airbytehq/oncall/issues/13049).

Connector CI Checks Summary is the aggregate of the above.