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 Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

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.

Best answer

Push trigger custom input (in Chrome extension) not visible when testing (or running) newly loaded push

  • 8 November 2022
  • 3 replies
  • 145 views
VanDan

Hi All,

The custom field in the Chrome trigger extension is not being found when trying to load Test trigger data. 

The zap has been published and has worked in the past. It broke while I was making adjustments to the sheet where Zapier uses the pushed input field to find the row (the Job ID). I have loaded new pushes but it only finds the example data as shown in the screenshot below.

The only other change that feels relevant is that I combined an existing email with a new email in my google account. So the email I signed up to zapier with is now different (but linked by Google) to the chrome account email.

Any help would be awesome :) 

 

icon

Best answer by Danvers 8 November 2022, 10:05

View original

3 replies

Danvers
Userlevel 7
Badge +12

 Hi @VanDan!

There’s currently an issue with the Zapier Chrome extension where Zaps aren’t pulling in real sample data when you test the trigged step. That means that when you test the Zap, you’ll see example text rather than something that you really ‘pushed’ with the extension. When the Zap is turned on, it will work the way it should and use data entered in the Chrome extension to trigger the Zap. 

 

I’m sorry that this issue makes things more confusing when you’re building your Zap. If you need any more help, don’t hesitate to ask!

VanDan

Thanks for the heads up @Danvers, I’m all sorted now. I’m not sure how hard it is to implement but an error window explaining that sure would have made me happier 😎

christina.d
Userlevel 7
Badge +9

Totally hear you, @VanDan. I passed along your feedback to the team - thanks for sharing it! 🤗

Reply


Terms & Conditions