When building a Zap with Chili Piper as the trigger, Zapier only surfaces the first meeting ever scheduled in the instance as test data. Admins can't test against different scenarios, such as a lead vs. a contact, different Meeting Types, or varied form submissions, without live data happening to match.

Update the Chili Piper Zapier integration to allow users to choose from multiple recent meetings when selecting test data during Zap setup, rather than being locked to a single historical record.

Zap configurations that can only be tested against one static record are brittle. Admins building scenario-specific automations either ship untested logic or wait for the right live event to occur, both of which increase the risk of silent failures in production.