From what I understand, Xano is returning the data you’re interested in the first action. You could then use the Download CSV action in your workflow to download that data in a CSV format.
Not sure what the differences/benefits of the different methods are, but I changed the endpoint back to standard response (rather than csv formatted) and added the Download CSV action which works fine.
@MichaelLovell do you mind expanding upon how you got it to work? our csv download works fine when run within xano. but when we map the data to the WW csv download step, its not properly formatting the header and individual rows. feels like what you were originally experiencing but i dont quite follow what you did to fix it.
@Alexis can you please confirm this csv download is working properly? i manually returned my data from Xano to ensure it properly is split per the doc @Joyce linked above
but the exported file is reflecting each row in column A. is this expected behavior?
What I did is to create a file/attachment resource of the CSV data in Xano and return the URL of that file in the API response. Then I use download file by URL in Weweb