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 setup this flow. However, either the delay and/or the postgresSQL find row is not working as expected. It’s been shooting to the end and adding a tag to the MailChimp subscriber, then sending an unwanted email. 

 

Hey @Dan_H ,

 

Can you share the screenshot of action 3?

Hi @Dan_H

For us to have more info, post screenshots with how your Zap steps are configured in EDIT mode.

Hi @Troy Tessalone and @jayeshkumarbhatia here are some more screenshots

Basically:

  1. Finds when a new member as joined the site
  2. The delay is set for 2 hours
  3. Afterward it checks if they have paid to subscribe. If they do pay, it updates their is_subscribed to true. If they did not pay, is_subscribed remains false. The 2 hours takes into account someone idling on a checkout page. I did not want to use Stripe’s webhook feature to watch for checkout expired because someone can also just signup for a free account.
  4. Filters to only allow users with is_subscribed = false to continue. At this point, if they are subscribed they should not go to step 5. In the screenshots, this user is not subscribed so it continues. If they are not subscribed it does show that this step 4 stops them...but that’s not the case.
  5. Updates their tag on MailChimp which then sends them into an email journey.

is_subscribed is always on the row in the table. It’s set to false by default.

 

 

This post has been edited by a moderator to remove personal information. Please remember that this is a public forum and to remove any sensitive information prior to posting.

@Dan_H 

Screenshots do not show how the Delay step is configured in EDIT mode.

Check your Zap Runs history details to see the DATA IN/OUT for each step to help you trace the data flow, see timestamps for steps, and troubleshoot: https://zapier.com/app/history/

Hi there, @Dan_H! 👋

Looks like there’s an issue with that Find Row action. At the moment, it’s searching the users table to find a record where the is_subscribed column contains a value that matches what is in the Is_subscribed field for the row that triggered the Zap. So if a row with an is_subscribed value of false triggers the Zap, after the delay runs it will then search the users table to find any row that also has an is_subscribed value of false not the same row that triggered the Zap. Instead, you’ll want to have it look for the exact same row that triggers the Zap.

To do that, the Find Row action will need to be set to search for an unique value that’s specific to that row. For example, you could set it to search for the email address as that would be unique to that user. That should ensure that it finds the correct row, then the filter will be checking the current is_subscribed value for the same row that triggered the Zap.

Can you give that a try and let me know if that fixes things?

Reply


Terms & Conditions