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.

Hi Community,

I’m running into an issue with a Zap that pulls multiple rows from Google Sheets and then routes them into different Paths based on the subscription plan (column D).

Here’s the structure:

* Step 5: **Google Sheets – Get Many Spreadsheet Rows** (tab: Facturation).
* Step 6: **Paths by Zapier** (Path A = “Starter”, Path B = “Pro”).
* Step 8: **Looping by Zapier – Create Loop from Text** (to iterate through the rows).
* Later steps: update subscriptions in Pennylane.

The problem:
When one row contains “Starter,” the Starter Path triggers correctly, but the **Loop still iterates over all rows returned from Google Sheets (Starter + Pro)**, not just the rows that match the Path condition. This causes Starter subscriptions to be created with Pro data, which is not the intended behavior.

My questions:

* Do **Path conditions** only decide if the Zap continues, or are they also supposed to filter the line items passed to a Loop?
* How can I limit the Loop to only the rows that match the Path condition (e.g. Starter Path → only Starter rows)?
* Is it necessary to preprocess and split the arrays (via Code/Formatter) before looping, or is there a native way to do this in Zapier?

Thanks a lot for your guidance,
 

Hi ​@Zoubeuh 

For us to have true context, post screenshots showing how your Zap steps are outlined and configured in the CONFIGURE tab with the field mappings visible.

Help links for using Looping: https://zapier.com/apps/looping/integrations#help

Help links for using Paths: https://zapier.com/apps/paths/integrations#help

Hi Troy,

Thanks again for your quick reply earlier. As requested, here’s the full outline of my Zap with the exact steps and mappings. I’ve also attached screenshots of the CONFIGURE tabs for context.

Zap Steps

  1. Schedule by Zapier – Trigger every day.

  2. Formatter by Zapier (Date/Time) – First date formatting step.

  3. Formatter by Zapier (Date/Time) – Second date formatting step.

  4. Filter by Zapier – Apply date conditions.

  5. Google Sheets – Get Many Spreadsheet Rows – Pull rows from the “Facturation” tab (includes Plan in column D).

  6. Paths by Zapier – Split into paths – Branch logic depending on subscription plan.

    • Path A (Starter):
      7. Paths by Zapier – Path conditions – Check if column D contains “Starter”.
      8. Filter by Zapier – Additional filtering.
      9. Looping by Zapier – Create Loop from Text – Iterate over fields (ID, Abo, SMS, Quantité).
      10. Pennylane – Update Billing Subscription – Send billing data into Pennylane.

    • Path B (Pro):
      (to be built similarly with its own conditions and actions).

The issue:
Even when the Starter path is triggered, the Looping step still iterates over all rows returned from Google Sheets (Starter + Pro), instead of only the rows that match the Path condition.

My question:

  • Do Path conditions only decide whether the Zap continues, or should they also filter which line items go into the Loop?

  • If not, what’s the best practice to make sure each Path only processes its relevant rows (e.g., Starter path → only Starter rows)?

Thanks a lot for your guidance,
Zoubeuh

 

​@Zoubeuh 

Screenshots only show how your Zap steps are outlined, but we need to see how your Zap steps are configured in the CONFIGURE tab while in EDIT mode so we can see the field mappings.

Reply


Terms & Conditions