That is definitely a strange way for the CSV file to be pulled in. After a fair bit of testing on our end, I’m led to believe that the issue is still the file type of the CSV file.
This appears to be the issue because:
A) When I try to pull in the same file through the same link (with your permission), I am still being met with the following error message:
The API response couldn’t be parsed: Data with Content-Type “application/vnd.ms-excel” could not be parsed.
I’m surprised that you were able to temporarily get around this message in your “Enrich with an API” step! I think if you tried to refresh the data, you’d likely hit the same error. While the URL that you’re trying to pull in does end in .CSV, it looks like the Excel file being uploaded to Bubble is not properly being saved in CSV format. I’d recommend researching the potential cause of this issue further.
B) Every other CSV file I’ve tested returns the data in multiple rows as opposed to one giant string. It looks like your comma-separated list in the
api column is missing a line-break character, which I can tell because your last column header and your first value in row 1 are separated by a space instead of a comma.
If you are able to consistently pull in data in this current format as seen in your screenshot, you can use these steps to unpack the data into standard rows and columns:
Feel free to paste this snippet directly into your flow to use these steps: parabola:cb:e04a39fe22b842e48074b5674513e1b6
Hope this helps!