Adding a search feature to a couple of dashboard Zaps, we found that GET /v1/orders?search= — and the same for refunds, bookings and escalations — returned a bare "Internal server error" whenever a search term was included. This is the documented way to search those endpoints, so any integration that tried it would have hit the same error, with nothing in the response saying why. It's fixed now, and confirmed against real orders, refunds, bookings and escalations before being shipped.
Off the back of it, the Zapier app can now find records, not just create or log them. "Find an Order", "Find a Refund", "Find a Booking" and "Find an Escalation" join the existing "Find a Customer", so a Zap can look something up by name, email, phone or reference before deciding what to do with it. See the full list of triggers, actions and searches