I’ve looked at this thread and note it is a similar question with no answer that helps for the development period of the Zap: Possible to enter search string to filter ConnectWise tickets by instead of selecting previous ticket? | Zapier Community
I have an initial node that I’m trying to build a more complex Zap from, but can’t get it to show the newly created single ticket from the Specific service board I’m filtering to (selected from list, not typed manually). The test data being presented is from all boards, not just the one specified in the filter. I have to assume this trigger grabs all, then post filters based on this behavior rather than pre-filtering to grab only data from the subset of new tickets defined by the filter. This prevents me from using that ticket as test data for creating the nodes that follow it.
Is there a better way to get test data that is useful to the Zap development process?
I’m new here, but have been writing code since the 70s with 30 years in the Industry and 15 years pushing more toward toolset integration devleopment. As such, I make assumptions about the code behind these “no code” interfaces based on how I would have written them.
Based on the RestAPI for CW, you should be able to pre-filter which would also have the benefit of reducing amount of data to transfer and reducing CPU/MEM load on your systems which would also make them faster.
