This example shows how to configure and test the Zendesk Search REST API activity to look up tickets by requester, then pass the results into a dynamic UI.
2️⃣ Select Requester
3️⃣ Save Results
Save Results In: ReturnedInfo
Tip: Use the Query Preview to see the exact query being constructed. Enable Customize Query for advanced scenarios.
Run a Test
Use the Run Test on Search window to simulate an input—no need for live ticket data.
4️⃣ Review Output:
After running the test: You’ll see execution logs confirming the activity has run.
The ReturnedInfo variable will contain the results—two tickets were found in this example.
The returned data can be passed to a Dynamic UI or Data Table to display relevant ticket details to agents in the interface.
1. Pre-Fill Agent View with Customer Info
Search for a user by email or phone number to retrieve and display profile details (e.g., name, org, recent tickets) before the agent engages with the customer.
2. Find and Display Open Tickets by Organization
Search all open tickets tied to a customer's organization and display them in a Data Table, giving agents context across related issues.
3. Trigger Escalation Checks
Search for tickets with the same tags or requester across multiple tickets. If more than 3 exist with a “priority” tag, escalate or flag for review.
4. Check Ticket Ownership Before Routing
Before reassigning or updating a ticket, run a search to confirm if the assigned agent is already overloaded or owns related tickets.
5. Populate Custom Actions Based on User Attributes
Search user details by name or ID, then drive PopFlows based on attributes like organization type, status, or user role.
6. Identify and Surface Duplicate Tickets
Use ticket fields like subject, requester, or tags to find similar tickets and surface them for agent review before taking action.