I’m working on connecting WordPress Gravity Forms with Monday.com through Make (formerly Integromat). My main form includes a nested subform, and when I check the data bundle from Gravity Forms, the subform entry IDs show up as comma-separated values.
The issue happens when I try to use the ‘Get Entry’ module for the subform data. Everything works fine when there’s just one entry, but it breaks down with multiple entries.
I’ve been stuck on this for a while now. I thought maybe using a repeater module would solve it, but I can’t get it configured properly. Also tried working with an array iterator but no luck there either.
Has anyone dealt with a similar situation? What’s the best approach to process multiple subform entries in this kind of setup?
I’m also open to hiring someone for a quick consultation if you have experience with this type of integration.
Ugh, this one drove me crazy too! The iterator approach everyone’s mentioning works well, but heads up - Gravity Forms sometimes sends those IDs with extra spaces around the commas. I had forms randomly failing until I added trim() after splitting. Also watch your Monday.com rate limits - processing multiple entries back-to-back hits their API throttling fast.
Hit this exact issue last month with a client’s event registration form. Those comma-separated subform IDs totally break the standard Get Entry workflow.
Here’s what fixed it: Use Text Parser’s Split Text function right after the Gravity Forms webhook. Set delimiter to comma and it’ll convert your ID string into separate bundles. Then run that through an Iterator module - the regular one, not array iterator.
The mapping’s the tricky bit. Make sure you’re using the iterator’s value field, not the original comma string. Took me three tries to get it right.
Tested with forms up to 8 subentries - works fine. Runs slower with multiple entries but processes everything reliably. You’ll probably want error handling for when subform entries get deleted but the parent form still references them.
Are your subform entries actually getting created properly? Sometimes the problem’s in Gravity Forms, not Make.
Gravity Forms’ comma separated values always trip me up too. I’ve hit this same wall on multiple client projects.
You need to split those IDs first. Drop a “Set Variable” module after your Gravity Forms trigger. Use split() on the comma separated entry IDs - like split(1.subform_entry_ids, “,”).
Next, add an Iterator module (regular Iterator, not array iterator). Feed it your split variable. Each loop gives you one entry ID.
Now your “Get Entry” module processes one ID per iteration. Works for any number of subform entries.
I switched most projects to Latenode after Make’s quirks got annoying. The code approach handles data manipulation way cleaner.
Your repeater idea was close - repeaters work but Iterators are simpler here. Always split first, then process individual items.
Hit this exact nightmare about six months ago with a multi-step registration form. Those comma-separated subform IDs completely mess up Make’s normal flow. Skip the Text Parser module - I found Make’s split function works way better. Just create a Set Variable module and use split({{your_subform_ids}}, ","). You’ll get a much cleaner array. Use a regular Iterator module, not the array iterator you mentioned. Feed it the split array directly instead of running it through a bunch of modules first. Watch out for empty values in that comma string - Gravity Forms loves adding those when users partially fill subforms. Throw a filter after your iterator to skip empty entry IDs before the Get Entry module. You’ll save API calls and avoid random errors. My current setup handles 15+ subentries without timing out. Takes longer to process but it’s rock solid in production.
Been dealing with this for years. Comma separated IDs are a pain with nested forms.
Make gets messy here - you’ve got to split the IDs first, then loop through each one. Your array iterator idea is right, but setting it up is annoying.
Honestly? Skip the hassle and use Latenode instead.
Latenode handles ID splitting and looping way better. Just set up a split function on those comma values, then forEach through each subform entry. Works with actual code blocks instead of fighting GUI modules.
I’ve done this with forms that had 10+ subform entries - Latenode handled them perfectly. Monday.com connection is simple too.
Debugging’s easier when things break. No clicking through modules - you see exactly what’s wrong.
Check it out: https://latenode.com
