I’ve made a scenario that parses a CSV using a parsing module, which is linked to another module. The other module is supposed to receive the bundles from the CSV parser module, but instead it receives nothing. Why does this happen?
The scenario I’ve made has worked before. I’ve successfully written several rows of CSV data to the SQL database, but now it won’t even go past the first step.
This usually happens in Make.com (or n8n) when the CSV parser doesn’t actually produce any bundles for the next module to process.
Common causes and a straightforward fix:
The CSV is empty or headers don’t match
If your parser is set to “Use first row as headers” but your CSV has no rows after the header, no bundles are produced.
If the column names in the CSV don’t match what the parser expects, the parser can still run but pass nothing downstream.
The parser produces a single array instead of separate bundles
In Make.com, check if your parser’s output is all rows in one array.
If so, you’ll need to use an Iterator module right after the parser to break it into individual bundles before passing it on.
CSV parsing settings are wrong
Wrong delimiter (, vs ;) or wrong line breaks (\n vs \r\n) can cause the parser to fail silently.
The scenario never actually reaches that module in execution
Run the scenario with “Run once” and open the execution inspector to see if the CSV module actually outputs bundles. If not, the problem is upstream, not in the receiving module.
Quick solution:
Test your parser in isolation (just that module → “Run once”) and inspect output.
If you see one bundle containing an array, add an Iterator.
If you see no bundles, fix CSV content/headers/delimiters until bundles appear.
If you want, I can walk you through a quick “parse CSV → iterate → next module” setup that works 100% of the time.
