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.

Best answer

How to fix filter issues in Zapier to avoid creating looped invites

  • June 16, 2025
  • 5 replies
  • 49 views
K

My company has a calendar for leads to book an appointment, but I only want it looking at one persons calendar for conflicts and not looking at the CEOs calendar. The only option within the calendar settings was to create a Zap to get the action perform how we want it. However, I’m running into an issue with a loop now.

 

When an event is added to the appointment calendar it triggers zapier to create a new event and send it to the CEOs calendar. However, this created a loop, so I put a filter, but the filter isn’t working as I intended. 

 

What suggestions do you have to make this filter work without creating 100 looped invites?

 

Here are my filter settings:

 

Step 3:

 

Best answer by Troy Tessalone

​@KingOfKings 

Here’s why…

In Zap step 3, when you create an Event, it gets a new unique ID.

So in Zap step 3, the Event Subject has the Event ID from Zap step 1, which is different from the Event ID created in Zap step 3.

That means the Filter conditions in Zap step 2, will never be met, because the the Subject has the a different Event ID that being compared when the Zap triggers to run.

 

Instead, try including a common value to use to filter to indicate the GCal Event was created from another Calendar.

e.g. Subject = [SUBJECT] - XXX

Where XXX would be a static value. (Change XXX to whatever you want.)

Then you can Filter by the XXX in the Filter step condition to prevent the looping.

    This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

    5 replies

    Troy Tessalone
    Zapier Orchestrator & Solution Partner
    Forum|alt.badge.img+14
    • Troy TessaloneZapier Orchestrator & Solution Partner
    • Zapier Orchestrator & Solution Partner
    • 34072 replies
    • June 16, 2025

    Hi ​@KingOfKings 

    Can you post screenshots showing how the Zap Filter step conditions are not working in live Zap Runs (DATA IN/OUT)?

    https://zapier.com/app/history/

    ⚡ Troy Tessalone - AutomationAce.com | Platinum Authorized Zapier Solution Partner | #1 Zapier Community Contributor
    K
    • KingOfKings
    • Author
    • New
    • 2 replies
    • June 16, 2025

    Hi ​@KingOfKings 

    Can you post screenshots showing how the Zap Filter step conditions are not working in live Zap Runs (DATA IN/OUT)?

    https://zapier.com/app/history/

     

     

     

     

    Troy Tessalone
    Zapier Orchestrator & Solution Partner
    Forum|alt.badge.img+14
    • Troy TessaloneZapier Orchestrator & Solution Partner
    • Zapier Orchestrator & Solution Partner
    • 34072 replies
    • Answer
    • June 16, 2025

    ​@KingOfKings 

    Here’s why…

    In Zap step 3, when you create an Event, it gets a new unique ID.

    So in Zap step 3, the Event Subject has the Event ID from Zap step 1, which is different from the Event ID created in Zap step 3.

    That means the Filter conditions in Zap step 2, will never be met, because the the Subject has the a different Event ID that being compared when the Zap triggers to run.

     

    Instead, try including a common value to use to filter to indicate the GCal Event was created from another Calendar.

    e.g. Subject = [SUBJECT] - XXX

    Where XXX would be a static value. (Change XXX to whatever you want.)

    Then you can Filter by the XXX in the Filter step condition to prevent the looping.

    ⚡ Troy Tessalone - AutomationAce.com | Platinum Authorized Zapier Solution Partner | #1 Zapier Community Contributor
    K
    • KingOfKings
    • Author
    • New
    • 2 replies
    • June 16, 2025

    ​@KingOfKings 

    Here’s why…

    In Zap step 3, when you create an Event, it gets a new unique ID.

    So in Zap step 3, the Event Subject has the Event ID from Zap step 1, which is different from the Event ID created in Zap step 3.

    That means the Filter conditions in Zap step 2, will never be met, because the the Subject has the a different Event ID that being compared when the Zap triggers to run.

     

    Instead, try including a common value to use to filter to indicate the GCal Event was created from another Calendar.

    e.g. Subject = [SUBJECT] - XXX

    Where XXX would be a static value. (Change XXX to whatever you want.)

    Then you can Filter by the XXX in the Filter step condition to prevent the looping.

    Thank you, a static variable rather than a dynamic indeed fixed it.

    JammerS
    Forum|alt.badge.img+6
    • JammerSZapier Staff
    • Zapier Staff
    • 3527 replies
    • June 17, 2025

    Wow! Thank you for confirming that Troy’s resolution got the Zap running. This will significantly help our Community members to have as a reference for the same issue.

    Terms & ConditionsAccessibility statement