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.

Hey everyone,

 

I’m having an issue with my workflow, which is as follows:

 

I’ve got three zaps running to:

  1. create item in Webflow/Airtable
  2. Update item in Airtable/Webflow
  3. Update live item in Webflow

So far things have been running smoothly and when a new Item is triggered a new airtable line is created housing all the datafields, which in turn are then used to populate a new CMS item being created in Webflow. Then the next trigger also works and updates things like: selling fast: true or sold out: false on the live item no worries. However, if an item is changed back to Selling fast: FALSE it doesn’t trigger the Zap and therefore nothing gets changed in airtable etc.

 

This is causing myself and my client a lot of headaches and I was wondering what might be happening that changing the RSS feed back to an old state wouldn’t result in the update item zap triggering.

 

Any help would be appreciated :)

 

Adam

Hi @Adam Shires 

Good question.

Please post detailed screenshots with how each of your Zap steps are configured in order for us to have more context, thanks.

Hey @Adam Shires! Just wanted to follow up here, were you able to figure out what was preventing your Zap from firing after updating back to FALSE? Also, you mentioned 

...

This is causing myself and my client a lot of headaches and I was wondering what might be happening that changing the RSS feed back to an old state wouldn’t result in the update item zap triggering.

 

I have a theory that might be the issue, since it might not be registering it as an “update” when its being reverted, and thus not triggering the Zap properly. 

If you’re still having issues, then like Troy mentioned, detailed screenshots would help us troubleshoot better! And if not, I’d love to hear what your solution was 🤗

 

Terms & Conditions