Zendesk’s platform is in a constant state of evolution, with new features and enhancements rolling out weekly. We keep our finger on the pulse so you don’t have to. Here’s our expert analysis of a recent, very powerful update from late August 2026.
Unlocking Your Data: Our Take on the New Zendesk Custom Object Search
What We Think:
The new Zendesk Custom Object Search action is a significant leap forward for any team leveraging custom objects. It moves beyond simple ID-based lookups to true, filter-based searching, finally allowing automations and AI agents to access the rich customer context stored in objects like orders, contracts, or assets. This isn’t just a minor tweak; it’s a foundational piece for building genuinely intelligent and personalised workflows. In short, this is a game-changer for automation within Zendesk, and we’re very excited about it.
The Reality Check: What’s Actually Changing?
For a while now, you’ve been able to store almost any kind of business data in Zendesk using custom objects—things like orders, shipments, user licences, or contracts. The challenge has been getting that information into your automated workflows, or “action flows”.
Previously, if you wanted an action flow to access a specific custom object record (like a particular order), you needed to know its unique record ID beforehand. The action flow could “look up” the record using that ID, but it couldn’t find records on its own. This was a major limitation. If you didn’t have the ID, you were stuck.
This update introduces a brand new action: Search for custom object records. The difference is subtle but profound. Instead of needing a specific ID, you can now instruct the action flow to search for records based on criteria you define. It’s the difference between asking for “book #734” and asking for “the five most recent books written by Stephen King”. The second query is infinitely more powerful and flexible.
Our Expert Opinion: The Real-World Impact
The ability to search rather than just look up custom objects opens a new frontier for automation and agent efficiency. Zendesk’s own example of finding a customer’s five most recent returns is a perfect illustration. An action flow can now perform this search automatically when a ticket is created, arming an AI agent or a human agent with immediate context.
Here’s where we see the biggest operational impact:
- Supercharged AI Agents: For AI-powered bots to be truly helpful, they need access to customer context. With this change, a bot can now independently query custom objects to answer complex questions like, “What’s the status of my recent orders?” or “When does my current software licence expire?”. It allows the bot to find the relevant information itself, leading to more sophisticated and complete automated resolutions.
- Smarter Human Agent Workflows: This isn’t just for bots. You can design action flows that run when a ticket is opened, search for relevant custom object data, and present it to the human agent directly in the ticket. Imagine a support agent for a SaaS company opening a ticket and immediately seeing a list of the user’s active subscriptions and entitlements. No more switching tabs or searching in other systems. This reduces handle time and improves the quality of service.
- Proactive, Personalised Experiences: Because you can search based on any field, you can build incredibly personalised automations. For an e-commerce company, you could build a flow that finds all orders over €500 from a specific customer and tags them as a VIP. For a logistics firm, a flow could find all shipments delayed by more than three days and proactively create tickets to notify the affected customers. The **Zendesk Custom Object Search** makes your data actionable in ways it simply wasn’t before.
How We’d Handle the Rollout
While this feature is powerful, a thoughtful implementation is key to getting the most value. Simply turning it on won’t achieve anything. Here is what we’re advising our clients to do:
| Phase | Action Item | Why It’s Important |
|---|---|---|
| Phase 1: Identify Use Cases | Brainstorm 2-3 high-impact scenarios where agents currently spend time manually searching for information that lives in custom objects. Start with the most common and time-consuming queries. | Focusing on clear, high-value use cases ensures your first automations deliver a measurable return and build momentum for broader adoption. |
| Phase 2: Review Your Data Model | Confirm that your custom objects are configured correctly for searching. Do you have the necessary fields to filter on, such as a ‘Status’ field, a relationship to the user, and relevant date fields? | The search is only as good as the data you have. A clean, well-structured data model is the foundation for effective searching and a core part of any successful Zendesk implementation. |
| Phase 3: Build & Test in Sandbox | Create your new action flows incorporating the search step in your Zendesk Sandbox environment. Test with various scenarios: a user with many records, a user with one, and a user with none. | Thorough testing prevents unexpected behaviour in your live environment and ensures the logic works as intended for all possible customer scenarios. |
| Phase 4: Phased Production Rollout | Deploy the new action flow to a small, select group of agents. Gather their feedback on the utility and accuracy of the information provided by the Zendesk Custom Object Search. | A phased rollout minimises risk. It allows you to catch any issues with a smaller user group and refine the process before it impacts your entire team. |
Our Final Word
This update is a critical piece of the puzzle for making Zendesk the central hub for all your customer data. It effectively bridges the gap between the data you store in custom objects and the actions you can automate with flows. By enabling dynamic, filter-based searching, Zendesk is empowering organisations to build smarter, more context-aware, and ultimately more efficient support operations. This is a powerful new tool, and we advise all our clients using custom objects to start exploring its potential immediately.
