About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

  • Home
  • Updates
  • Changes to the Zap Editor: Trigger Sample Step

Changes to the Zap Editor: Trigger Sample Step

Changes to the Zap Editor: Trigger Sample Step

Hey everyone! Kenyon here from Zapier. We’re very excited to announce some changes we’ve made to the Zap Editor that we hope will make building a Zap even easier!

We’re streamlining the trigger sample step so it’s easier to use. You may know this as the ‘Find Data’ page in step 1. There are two main components to this change. Principally, you’ll notice the number of samples displayed has been reduced to one. You will still be able to access other records if you’re looking for something specific, but they’ll be hidden behind a dropdown. We hope this reduces confusion, removing unnecessary choices but allowing them to be accessed if needed. 

The second piece of this release is an update to the help text displayed in this area. We now use emojis to indicate success and failure. We’re more clear about where the sample was found, and we use language directly from the app—instead of “sample,” we may note a “lead” or a “contact” was found, making it easier to understand what we’re doing along the way. We’ve heard this step can be a substantial source of confusion, particularly for those new to Zapier. These changes were made in response to that feedback. 

You can see these changes on Zapier now! If you have any questions, let us know!

Thanks :)

Hello again! 

We’ve followed up this release with another small change as we continue to improve the trigger testing process. Starting today, when the trigger test is skipped the Editor will display this new interface:

You’ll see this if a fallback sample isn’t available for that particular trigger app. The help text is a bit more useful, describing exactly why a sample doesn’t exist. In this case, we see we would need to send a webhook to the URL provided earlier in the step in order for Zapier to find that sample.

We display 2 options: you can either skip the test again to continue on to the remainder of the Zap, or run the test again after making the necessary changes. 

As usual, let us know if you have any questions or concerns! We’re always here to listen. 

 

Team Editor

Terms & Conditions