@MutedJam I’ve advanced one step … just added and header with content-type application/vnd.ms-excel to my Respond to Webhook node and now I’m getting 82be0ea4-1c84-4c01-8059-7a03d2260.xlsx instead of .zip via Chrome. So the exention now is correct … one down, one left to go
@MutedJam just found the last problem … there was a space in front of attachment, etc. Safari and Postman apparently can cope with this and Chrome can not. So long story short; problem solved and workflow 100%.
Enjoy your weekend!!!
1 Like
Woah, I would not have guessed that! But that easily explains why I couldn’t see this on my end.
Thanks so much for sharing and have a great weekend as well!
just in case somebody is interested, this is the final code for a simple workflow that I use as a micro service to convert a simple (/flat) JSON array to an Excel file …
2 Likes