Ask questions, share tips, and discuss best practices about apps and integrations, APIs, SDKs, ZAF, and Sunshine
Recently active
Hello, Using Zendesk Conversation Extensions, can we create an extension that uses the Camera or the File Explorer on the device for them to select a file.Android and iOS have a permission system that requires users to grant access to these features. How can we do this? When trying to attempt this, I'm getting some error regarding accessing the hardware or the button do nothing. If not, is it on your product timeline? Thanks,
We've been developing a Zendesk sidebar app and want it to use the full available sidebar screen space, both in width and height. While setting the width to 100% works as expected, setting height: '100%' viaclient.invoke('resize', { width: '100%', height: '100%'});has no effect – the height simply isn't respected unless we provide a fixed pixel value. But hardcoding a value doesn't adapt to the dynamic space available, which is essential for our app since it displays live contextual data. We’ve also tried using CSS to enforce full height, including height: 100% and min-height: 100vh on the body and root elements, but that didn’t solve the issue either. We noticed that Zendesk’s own demo apps (e.g. https://github.com/zendesk/demo_apps/blob/master/v2/support/basic_ticket_sample_app/assets/iframe.html) navigate around this by setting small fixed heights, but that’s not sufficient for real-world use cases like ours. We’re looking for a reliable and flexibl
I am following this link https://developer.zendesk.com/documentation/marketplace/publishing-to-the-marketplace/set-up-paid-app-or-theme/ . It asks me for my Pan Id and bank account or other personal questions but I don't want to share these for my test account . I just want to first integrate stripe and test all the process by stripe test mode then switch on real payments. How can I do this? Please help me out from this?
Hi everyone!I have a question regarding the Help Center Manager app.I'd like to use it to perform a bulk update of article titles, but before making changes to our official Knowledge Center site, I'd like to test the process first.Does anyone know if Zendesk provides a testing, sandbox, or staging environment where I can safely try these changes before applying them in production?Any guidance or best practices would be greatly appreciated.Thanks in advance!
As you may already know, Zendesk is retiring API tokens in favor of OAuth. Unused tokens will begin deactivating automatically on July 28, 2026, and all API tokens will completely stop working on April 30, 2027. Why the change?API tokens are being replaced with OAuth to deliver safer, short-lived, and precisely scoped access for API-driven workflows. As an industry standard, OAuth provides critical security capabilities that simply cannot be retrofitted into the existing API token architecture. What this means for youIf integrations aren't migrated to OAuth before the deadline, they will stop functioning. The level of impact depends on how heavily your daily workflows rely on legacy API tokens. Join the discussion & upcoming meetup Whether you're currently mapping out your migration, have run into roadblocks, or have discovered best practices that could help fellow developers, we want to hear from you!@Ahmed Zaid , Leader of the Developer User Group, is hosting an upcoming meetup
Hello, Following your announcement of the removal of API tokens as an authenticationmethod (article 10851263566234: auto-deactivation of unused tokens on2026-07-28, no new tokens after 2026-10-27, full EOL on 2027-04-30), we haveproactively migrated our integrations to OAuth. Our main server-to-serverapplication now authenticates exclusively with client_credentials accesstokens, and we are migrating our remaining API tokens one by one. However, we have identified one integration paths for which no OAuthmigration option currently exists, and we need your guidance on both. We provision our Zendesk users and groups from Microsoft Entra ID using theofficial Zendesk connector from the Microsoft Entra application gallery. Asdocumented by Microsoft(https://learn.microsoft.com/entra/identity/saas-apps/zendesk-provisioning-tutorial),this connector only supports Admin Username + Secret Token (a Zendesk APItoken) for authentication. There is no OAuth option on the Microsoft side. This means that
Refund requests outside your standard policy can require a review of the conversation, order details and eligibility for an exception. This recipe brings that assessment, a recommendation, human approval and a public reply to the requester into one workflow. This recipe uses one Custom Agent within one Action Flow. The agent first assesses the request and records its findings in custom fields on a Refunds ticket form. After an approver approves or denies the recommendation, the flow calls the same agent again to notify the requester. A tags input selects which section of the agent's instructions runs at each handoff. How this recipe works Component or role Responsibility in this recipe Custom Agent During assessment, reviews the request and policies, verifies the evidence, records a recommendation in the Refunds form fields, and completes the first three tasks. During notification, reads the approval decision recorded by the flow, sends a public reply, and comp
What are the implications of the deprecation of API tokens for local development of themes and apps?Currently, I have a `ZENDESK_API_TOKEN` env var set, along with `ZENDESK_EMAIL` and `ZENDESK_SUBDOMAIN`, so that when I run `zcli themes:preview` or `zcli apps:server` it does its magic and I can develop these things locally.How will this work with OAuth? I’ve implemented the new OAuth workflow for the actual apps that I need to so that production environments work, but how am I expected to continue to develop locally once api tokens are fully deprecated? I’d rather get this taken care of now rather than after it stops working.
This recipe uses a Custom Agent to review a support ticket, classify the customer's current request, and update the ticket itself. The agent sets a Ticket category field and assigns the ticket to the matching support group.If the agent cannot confidently select a supported category, it adds a private note and assigns the ticket to a review group. The Action Flow invokes the agent and provides a separate error path if the handoff cannot start. Before you startBefore configuring this recipe, create the following:A drop-down ticket field named Ticket category. Create option tags that are relevant to your support process. The support groups that will receive each category of ticket, plus a group for manual review. An Action Flow with a Ticket event trigger configured to run when a ticket is created.This example uses the categories below. Replace them with categories, field tags, and group names that match your own use case. The agent needs the exact ticket field ID and exact group names fr
This can happen when the API request successfully creates a Zendesk ticket, but some submitted field values aren't mapped or formatted as Zendesk expects. For example, the ticket may contain the requester's name and email, while custom fields such as company name, phone number, product type, or issue category remain blank.I'd check these three things first: Custom field IDs and mapping: Zendesk expects custom ticket fields in a specific structure, using each field's ID and value. Make sure the fields from your Contact Form 7 form are mapped to the correct Zendesk custom field IDs. Field value formats: Dropdown fields may require the option's tag value rather than its display label. Also check that dates, numbers, checkboxes, and multi-select fields use the expected format. Actual API request and response: Don't rely only on the success message displayed after form submission. Inspect the outgoing payload and API response, then check the created ticket in Zendesk to confirm which va
Hi, would like to ask if what authentications are currently available for uploading ZIS Bundles using API? Since API tokens are slowly being phased out, I’m trying to authenticate using oAuth client. For now, I’m invoking the APIs through Insomnia.Here are the steps I’ve done so far:Created an oAuth client to get Bearer Token via API request Created an integration key for the bundle via API request using the Bearer token from step 1 Attempt to upload a ZIS bundle via API request This is where I’m having issues. I am encountering this 401-error message when I’m invoking the request. I’ve leveraged the Bearer Token from step 1 and encountered this message I’ve tried to retrieve the full_token from the integration key using its client_id but unfortunately, the same message can be seen. I even applied tweaks to the integration key itself such as setting its “client kind” parameter to “confidential” but I’m still blocked. Response says “Authorization failed due to OAuth being disabled
Full disclosure: I'm the co-founder of Rulebase, so I'm biased here. We shipped an MCP server for Zendesk. Zendesk itself is an MCP client (Copilot can call external tools), but there's no first-party MCP server - so if you want Claude, Cursor, or any MCP client to read your tickets, there's no native way to do it. What it does: - Syncs a read-only copy of your Zendesk conversations into one canonical schema. Zendesk stays the system of record.- Finds repeat contacts from the conversation text itself, not just agent-set fields.- Measures actual complaints, not just the ones agents remembered to tag. We also open-sourced 150 agent skills for CX ops (QA, complaints, churn signal, forecasting, coaching). MIT licensed and vendor-neutral: https://github.com/rulebase-co/rulebase-skills Details: https://www.rulebase.co/mcp/zendesk Happy to answer questions on the schema or the tradeoffs. And if this kind of post isn't welcome here, tell me and I'll take it down.
Curious how other admins handle this: we have "Category / Subcategory" style dropdown fields on our ticket forms. By default Zendesk shows every subcategory option no matter what category the agent picked. Agents end up scrolling through irrelevant options, and keeping this in sync via triggers gets messy as the field list grows.I ended up building a small app for this called Conditional Dropdown Filter. It's a free app on the Marketplace that connects a parent and child dropdown field with a visual rule builder. No code, no triggers needed.What it does:Pick which child options are allowed for each parent value Agents instantly see the filtered list in the ticket form Flags rules that reference deleted field options so they don't go stale Runs on Zendesk Custom Objects in your own account, nothing leaves Zendeskhttps://www.zendesk.com/marketplace/apps/support/1275479/conditional-dropdown-filter/Genuinely curious: is everyone else solving this with triggers/conditional fields, or is the
Like many people, I have been using triggers + webhooks to the Zendesk API, authenticated by API token, to make ticket modifications when there is no native action for what I need. The upcoming elimination of API tokens in favor of OAuth is forcing a change to this configuration, and it looks like Custom Actions & Action Flows might be a good path forward.For example: we have a process where a customer fills out a web form, and the information is sent to Zendesk via email for our agents to process. The ticket is created with the form data in the ticket description (first comment) as a public note. We want to change this to private so it is not visible to the customer when we reply to the ticket.Currently the trigger that runs when these tickets are created notifies the following API-token-authenticated webhook:https://xxx.zendesk.com/api/v2/tickets/{{ticket.id}}/comments/{{ticket.latest_public_comment.id}}/make_private Here is my current approach to replace this. All suggestions fo
Hello,Some of our groups just changed their primary email address. The API update the email address by adding a secondary and keeping their primary as is. Is there a way to update primary via the API?
We are using oauth with our api to sync data into zendesk and are looking to limit the scope of our tokens.For the most part this has been fine, however it seems like there are a couple of endpoints we are using that don’t have write scopes (at least documented): organisation_field and custom_objectsThis suggests that we have to use the global write scope for this, which wouldnt be ideal.Is this correct, or did I miss it somewhere? If so, is there a solution/workaround to this?Thanks
Ciao a tutti,sto cercando un consiglio tecnico riguardo a un'integrazione Zendesk per un sito basato su calcoli dinamici.Gestiamo una piattaforma astrologica dove gli utenti inseriscono dati di nascita e ottengono risultati personalizzati. Una situazione piuttosto frequente è che gli utenti eseguano più calcoli del proprio ascendente prima di contattare l'assistenza, modificando più volte i dati inseriti per verificare eventuali differenze nei risultati.Durante l'integrazione con Zendesk abbiamo riscontrato alcune problematiche legate alla gestione dei ticket.Flusso attualeL'utente completa un processo di calcolo multi-step. Il risultato viene generato in tempo reale. Alcuni utenti effettuano più ricalcoli consecutivi. Successivamente inviano una richiesta di supporto. Zendesk può ricevere più ticket relativi allo stesso utente e alla stessa problematica.Problemi riscontratiCreazione di ticket duplicati dopo invii ripetuti. Difficoltà nel mantenere lo storico delle modifiche effettuate
Hello,I am Sakar from Kathmandu , Nepal. Recently started SaaSPal a Product focused company. The biggest challenge I face as a builder is validating my idea and testing with beta users. I have tried cold reaching and cold messaging some but I think should try more.How did you find your first customers ? How did you make your beta tester groups ?
Our Azure Function App fails to connect to Zendesk with the following error:ConnectionResetError(104, 'Connection reset by peer')This happens on every request to our Zendesk subdomain — including a simple unauthenticated GET request:requests.get("https://{subdomain}.zendesk.com/api/v2/tickets.json", timeout=10) The same code with the same credentials works fine locally Our Azure NSG allows all outbound internet traffic No IP Restrictions are configured in Zendesk Admin Center (confirmed by our Zendesk admin) Our Zendesk admin confirmed OAuth is configured correctly and tokens can be generated Other third-party APIs (e.g. ZOHO) work perfectly from the same Azure environment using the same requests library Even a basic unauthenticated GET to Zendesk fails — ruling out any OAuth or credential issueHas anyone experienced this before? Is there a known solution or a way to get Azure datacenter IPs whitelisted on Zendesk's infrastructure level?
I have been creating a flow with Power Automate to automatically download all attached files from tickets in Zednesk and save them into specific folders.So far the flow works perfectly, but for some reason it does not download the files for Whatsapp tickets.I have read most of the documentation that talks about API usage, but I could not find anything that talks about this.I can even see in the in DevTools where the files are stored, but I do not know how to get that information with the API.What I see in DevToolsHow can I get this with the API?Your Premium trial has ended
If you've been trying to authenticate a Custom Action using your own Zendesk account as the OAuth provider, here's a step-by-step guide on how to get it working that I got from support. I couldn’t find a good single resource on how to do this especially with the announcement of API Tokens going away so wanted to share with the larger community. This is for how to get the “Connection” setup for Action flows but would likely work for other areas to be used to replace webhook actions as well. Step 1: Create the Zendesk OAuth ClientGo to Admin Center > Apps and Integrations > APIs > OAuth clients and click "Add OAuth client".Configure it with the following:Set Client kind to Confidential Set the Redirect URL to: https://zis.zendesk.com/api/services/zis/connections/oauth/callback(Note: the subdomain is always zis, not your own account's subdomain) Copy the Secret value and store it somewhere safe — you'll need it in Step 2(For a full reference on each field, see: Using OAuth authen
Hi,One thing I've learned while working with Zendesk is that agents often spend more time on small, repetitive tasks than they realize. Updating fields, adding tags, changing priorities, and following the same process for every ticket can quickly become time-consuming.I used App Builder to create a simple workflow that reduced some of these manual steps.The goal wasn't to build a complex application. I wanted to make the process faster and more consistent for agents.My approach was simple:Identify a task that agents repeat every day. Break the process into smaller steps. Automate only the repetitive actions. Keep the workflow easy to understand.One lesson I learned is that it's better to start small. Trying to automate everything at once usually creates unnecessary complexity. A simple workflow is easier to maintain, easier to test, and much easier for teams to adopt.
Have you tried building something in App Builder that you couldn’t accomplish and need help with? Welcome to this special edition of Zendesk Voices, where we dive into your experiences with extending and integrating Zendesk in real world scenarios!Have you hit a roadblock while building something in App Builder?We want to hear your story. Tell us about the challenges you faced, what didn’t work as expected, and how you’re working through those hurdles. Your insights can help others overcome similar obstacles—and you could earn Spark points for your contributions!🤓We’d love to know:What you attempted: Describe the project or feature you were building. The challenge: Share what you found difficult or what couldn’t be accomplished. Your approach: Let us know how you went about troubleshooting or what alternative solutions you considered. Outcome & learnings: Explain what worked, what didn’t, and what you learned through the process.👀Helpful tips:Be specific and share real examples.
Hello all,Three days ago I got an email that tomorrow our API tokens will get deactivated because they weren’t used recently.Our OpsGenie token hasn’t been recently used, because thankfully we didn’t have a customer incident in the last few months.Unfortunately there isn’t a clear way to force keep an API token activated. So tomorrow, our OpsGenie integration stops working unless we keep rotating our API tokens? Is there any other way to do it?This is one of the most critical systems for us. Not responding to a ticket within an SLA means we breach our contractual obligations. And all these happen with just 4 days of notice in advance!Thank you for any help you migh be able to provide regarding this.
We have the Sunshine Conversations V2 Messages API working, but when we try to use the Passthrough API, we are getting a "should have required property 'content'" error. Here is the request, payload, and the response: POST: https://api.smooch.io/v2/apps/62d2b047fa1d7700ef4bc9f1/conversations/a63b416485367d8a768f6c6a/messages{"author": {"type": "business"},"content": {"type": "text","text": "Test"},"override": {"apple": {"payload": {"body": "https://smooch.io/","type": "richLink","richLinkData": {"url": "https://smooch.io/","title": "Title","assets": {"video": {"url": "https://images.apple.com/media/us/homepod/2018/98e6cc1a_37ec_4e69_b717_9e58c71e1937/films/expand/homepod-expand-tpl-cc-us-20180306_1280x720h.mp4","mimeType": "video/mp4"}}}}}}}{"errors":[{"code":"bad_request","title":"should have required property 'content'"}]} According to the documentation, the V2 API does support the "override" / passthrough APIs for Apple Business Chat: https://docs.smooch.io/rest/#o
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.