Skip to main content

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

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions 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.

I'm triggering my zap based on the field “SMS to Send” changing in HubSpot. This works fine in the trigger section. But I also want to filter on that field so that I can send a different SMS message based on the field value and cannot see it in the filter field list using the Filter by Zapier action. I see many other custom fields from HubSpot.

SMS to Send started as a dropdown. I then changed to a single line of text - didn’t work. I then removed SMS figuring it may be a reserved word in triggers. No change.

How can a field be visible in Trigger but not in Action/Filter?

 



 

 

Hi @gschare 

Good question.

Try also specifying that fields in the additional properties to retrieve.

 

I somehow got this to work. No idea how. It seemed random as I kept adding fields to retrieve and eventually SMS to Send began to show up in the trigger. 

I just don’t think Zapier can reliably retrieve all my fields from HubSpot so it’s hit or miss if it grabs the one I need. But once it hits, it’s sticky so it seems it’ll be reliable going forward.

@gschare 

Depending on the HubSpot trigger/action, it will return certain specified default fields, otherwise you need to manually specify the other fields to return.

I did that and it still did not work reliably. I’m very interested in hearing from Zapier support on why this happened. I will run another test with a brand new zap in the meantime to see if it still repros. But my primary zap is now working great so I’m unblocked.

Thanks for the assist Troy!

Finally solved this after running into it again with yet another new HubSpot field. It’s a Zapier bug that requires clearing the cache before the field is seen beyond the trigger level of the Zap. It worked instantly in an incognito window. I’ve reported the bug to Zapier.

Hi @gschare,

That's fantastic news! I'm glad to hear that you were able to solve the issue you were facing with the new HubSpot field. Thank you for taking the time to report the bug to our Support team.

Thanks!

Reply


Terms & Conditions