Is there an API for instructing Zendesk to update a GitHub-linked Guide Theme from GitHub?
API Endpoint to trigger GitHub-linked theme update?
Hi @eric27, yes that is the idea. I am trying to create a pipeline (on GitHub Actions) that would automatically increment the version and make Zendesk update the theme to the latest version.
Hi @eric27, I've read the link but it doesn't tell me how to trigger the Update from GitHub action available in the Theme settings page.
Hey Timothy,
This endpoint hooks into the backend endpoint that handles the upload. There isn't an endpoint that hooks into that frontend controller. Though the concept is the same:
Have your action create the update theme job on push to main, then you'll receive the endpoint to upload to. Zip the repo, add it to the payload and create the update request.
If you'd like my team can put this on our backlog of things to make a tutorial for.
@eric27 so how does Zendesk manage to hide the manual zip-file uploading step from the user when they press "Update from GitHub"? Shouldn't the API also be able to bypass this step?
Hi Timothy,
I'll need to check with the corresponding dev team to confirm. Though if I'm not mistaken, the "Update from Github" hooks into the Github OAuth flow to access your repository and perform this process. Though this isn't something that is possible from the API as the relationship between the services isn't the same (i.e. we can control the full OAuth flow from the UI, while we can't via API) from a security perspective. Due to that we aren't able to handle the cloning, zipping and uploading ourselves if it were to be initiated from API.
If I hear from the dev team that the reason is something else, I'll touch base here.
I'll need to check with the corresponding dev team to confirm. Though if I'm not mistaken, the "Update from Github" hooks into the Github OAuth flow to access your repository and perform this process. Though this isn't something that is possible from the API as the relationship between the services isn't the same (i.e. we can control the full OAuth flow from the UI, while we can't via API) from a security perspective. Due to that we aren't able to handle the cloning, zipping and uploading ourselves if it were to be initiated from API.
If I hear from the dev team that the reason is something else, I'll touch base here.
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
I'm not sure I fully follow. Are you wanting to create a CD pipeline so when you push against your repo it updates your Zendesk Theme in Guide?