Number of Items in List Not the Same Size But Need to Pass Values Through

[JulieH]

I give up! Can anyone help me figure this out before I beat my head on the keyboard?

Scenario: I have a googlesheet with a list of contact names and companies (along with Company LinkedIn URL).
Flow: Gumloop should:

1. Read the GoogleSheet (working)
2. Search Google to try and find the contact’s linkedIn URL (we grab the first result in google which works great and is cost effective - it generally finds 90% which is good enough)
3. Filter only results that are CONTACT records on LinkedIn (not posts or companies, etc.)
4. Scrape the contact’s LinkedIn URL (working)
5. Write the scraped information back to the GoogleSheet (failing)

The problem is that there might be 10 records that come in, 1 of them gets filtered out and now we have a list size problem between the scrape (contact LinkedIn) and the lookup value (org linkedIn URL) on the GoogleSheet.

I have tried turning on Blank Rows in the filter and it feels like that should work but it doesn’t.

I did look at this help flow but it doesn’t pass values from the top to the bottom so it doesn’t seem like the same scenario.

Any assistance greatly appreciated!

Here is the link to the flow … https://www.gumloop.com/pipeline?workbook_id=e59kuLZEitAyd14MFoqPFa&run_id=8VxJiDLC5kXLCyFPd3Lmod

[Gumloop_Bot]

Hey @JulieH! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.

1. Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}}

2. Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
   

3. Provide details about the issue—more context helps us troubleshoot faster.

You can find your run history here: https://www.gumloop.com/history

[Wasay-Gumloop]

Hey @JulieH – The list size mismatch error usually happens when you’re passing data from two sources that don’t match in list size, which breaks the 1:1 relationship needed for loop mode to run properly. Without that match, the subflow or node doesn’t know how many times it should iterate in loop mode.

The best approach here is to build a subflow that works for a single input — this section of the docs explains it well. Then you can loop that subflow over your full list of inputs and wrap it with an error shield. That way, the 1:1 relation is always preserved, and if anything fails, it safely skips the entire subflow run without breaking the rest of the process.

Here’s your cloned workflow with that setup in place: https://www.gumloop.com/pipeline?workbook_id=iEd5dhQTCHcpRKTNY8KCDa — feel free to clone it on your end.

You can read more about the list size mismatch error here.

Let me know if this makes sense and works for you

[JulieH]

THANK YOU SO MUCH @Wasay-Gumloop!