Several Items with nuremous photo's per item, but not all the same # of photos

@Wasay-Gumloop the following:

  1. I have 150 items in an google sheet
  2. Photo’s have been taken of these items (from different angles)
  3. Every item has 3, 4, 5 or 6 urls to a photo (in this google sheets)
  4. So some items have 4 photos and others 3 or 5
  5. I created a flow where these urls are copied to a google doc; 1 google doc per item
  6. Next step is to import these photo’s (from the respective url) into this Document
  7. And lastly to create a pdf of this document (with these photos)
  8. To then let the Image AI node make a description of these items
  9. (which need to go into a Shoppify environment)
    Problem is as follows:
  10. I created this first flow (for one Google Doc) where I created 11 input (max number of photo’s an Item can have)
  11. I had to give these input nodes a value …
  12. Then I created a second flow (with a subflow of the first flow) which I connected to the Google Sheet with the 150 items
  13. But then I ran into a problem … some of the items only have 4 photo’s … So the flow then selected the url’s from the first flow (for photo 5->10), with the “dummy” urls
    (hope you can still follow me)

So the items with less then 10 photos end up with 10 photos, where 4 are good and the remaining 6 are wrong.

How do I solve this?

Thanks (as always)


Hey @Donna! 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.
    GIF guide

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

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

Solved it myself … :wink:

Nice! What was the solution (if you don’t mind sharing)?

take the value out of the input node … (keep the name) … as simple as that …

Ah okay, thank you for sharing!