Short answer
Check Zendesk connections marked Legacy or Deprecated with a 1.x.x version in Zapier. Migrate affected Zaps to the current OAuth-based integration before April 30, 2027. Give infrequent workflows an earlier check: Zendesk already deactivates tokens left unused for 30 days.
What changed
Zendesk announced the retirement on June 1, 2026. Its rollout began July 28 with unused-token deactivation and restrictions for new accounts. New token creation ends October 27, 2026; remaining tokens are permanently disabled April 30, 2027. Zapier updated its migration instructions on September 3.
Affected product, plan, or suite
Zendesk Ticketing, Help Center and Voice APIs that use Support API tokens; this article focuses on legacy Zendesk connections used by Zapier Zaps.
Date and timing
April 30, 2027
Why now
The September update provides a reason to inspect existing connections now, rather than wait for next spring. Zendesk's notice makes clear that token inactivity can interrupt a workflow before the final retirement date.
Who should care
Small support and operations teams whose ticket updates, customer handoffs or periodic reports depend on a Zendesk connection in Zapier. Assign the check to whoever owns the workflow, even if another person originally built it.
Why it matters
A successful reconnection does not prove that the entire workflow still works. A later step can receive the wrong field or no data after an integration-version change. Test the business result: did the intended ticket, handoff or report actually reach its destination?
What this does not change
Zendesk excludes Messaging, Chat and other products from this Support-token change. Zapier says an untagged connection is likely current; that is not proof about a particular account. The cited notices give no exact shutdown hour. Schedule migration before the deadline.
Worthd take
Treat the deadline as a small maintenance project with an owner and a checked result. It is a reason to budget migration time, not evidence that you need to replace Zendesk or buy a more expensive Zapier plan.
What to check next
- Find legacy 1.x.x Zendesk connections in Zapier and list their dependent Zaps.
- Assign an owner and a test case to each important support workflow, including monthly or quarterly jobs.
- Upgrade affected Zendesk steps and authorize an OAuth connection using Zapier's migration instructions.
- Check downstream field mappings, test each affected step, then publish and turn the Zap back on.
- Confirm the resulting ticket or record and record the migration's completion before the retirement date.
Open the primary source ยท Read the supporting source
Published and sources checked September 5, 2026. Confirm current contract terms and vendor documentation before acting. How Worthd works.