- Newest
- Most votes
- Most comments
Hello.
According to the documentation below, Zendesk is moving toward the phased enforcement of OAuth access token expiration in 2026; the current defaults are 30 minutes for access tokens and 30 days for refresh tokens.
Implementing the refresh token flow is recommended for long-running integrations.
https://developer.zendesk.com/documentation/authentication/refresh-token/
Based on the AppFlow documentation below, it is possible that automatic token renewal using Zendesk's refresh-token grant is not supported.
Given the absence of a refreshToken in ZendeskConnectorProfileCredentials and the fact that AppFlow is currently returning a 401 error after the access token expires, I suspect the current connector may not be compatible with the new Zendesk token lifecycle.
https://docs.aws.amazon.com/appflow/1.0/APIReference/API_ZendeskConnectorProfileCredentials.html
Can the existing connection can be reauthorized to obtain a refresh token?
You can obtain a new access token by re-authenticating; however, since AppFlow may not be storing the refresh token, I expect the same issue to recur after 30 minutes.
Relevant content
asked 2 years ago
asked 5 years ago
- AWS OFFICIALUpdated 4 years ago

Thanks very much for the response Riku.
Do you know if AWS is or will be providing a Zendesk connector update to support this refresh token change?
If not are you aware of any alternative recommended way to replace/fix an existing Zendesk AppFlow Oauth connection?
I am not an AWS employee, so I do not know whether the issue is being addressed.
I can't say for sure if this will avoid the issue without testing it, but how about trying to set up an AppFlow Custom Connector? Since the AppFlow Custom Connector supports refresh tokens, it may be possible to avoid the issue. https://docs.aws.amazon.com/appflow/1.0/APIReference/API_OAuth2Credentials.html https://aws.amazon.com/jp/blogs/compute/building-custom-connectors-using-the-amazon-appflow-custom-connector-sdk/