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 manage a list of students and courses in Airtable and use Mailerlite for email marketing. I have two zaps connecting AT and ML:

  1. When a student joins a course, add them to the relevant ML group.
  2. When a student leaves a course, remove them from the relevant ML group.

Each Zap watches its own “last modified” field, and each “last modified” field is watching its own linked field.

The problem is that when a student joins, the ‘add to group’ zap fires - AND the ‘remove from group’ zap fires. I can’t for the life of me figure out why.

I’ve checked and double checked the AT fields and that the Zap triggers are definitely connected to the right fields, and I’ve tried reconnected my Airtable to Zapier. Nothing.

Any ideas out there?

Hi @Sigurdur130! 👋

That’s very strange. Are both Zaps looking at records in the same View in Airtable?

If so, perhaps you could try adding a Filter (Add conditions to Zaps with filters) to the Zaps to check whether the student has either joined or left the course. Presumably this whether they’ve joined or left the course would be noted somewhere in the record, right?

Do you think that could work at all?

If you do give that a try, let us know how you get on. Always happy to help further if you run into any issues!

Hi @Sigurdur130 

Good question.

We’d need more detailed screenshots with how each of your Zap steps are configured along with how each of the related Airtable fields are configured in order for us to have enough context, thanks.

Also, best to outline a specific example to trace the data involved.

Thanks for the replies.

Sam: yes, both zaps are looking at the same view, or rather, neither zap has a view restriction.

Troy: Here are the relevant screenshots. I hope we can work this out! 

 

 

 

@Sigurdur130 

Good question.

As part of the Zap trigger config, you may want to indicate a View to filter on.

Otherwise, the Zap trigger is for NEW or UPDATED records, meaning it will trigger BOTH Zaps for NEW records.

 

@Troy Tessalone, SUCH an obvious answer as soon as you say it X.x Thanks so much!

Hi @Sigurdur130 

You’re welcome! Great to hear that Troy was able to help you!

 

 

Terms & Conditions