Hi everyone,
I’m trying to send an email with a CSV file attachment that I generate using the 1T-CSV Creator plugin.
In my workflow, I perform the following actions:
In the File field of the Send Email action, I set:
Result of Step 1 (Create CSV from JSON (SSA)'s Base64 Text)
I do receive the email, but the attachment is missing.
When I run the workflow in step-by-step debug mode, I can see that the File field contains Base64 data that correctly matches the CSV content. However, it doesn’t seem to be converted into an actual attached file.
Does anyone know why the Base64 text isn’t being recognized as a file attachment, or if I’m missing a step to properly convert it into a CSV file?
Thanks in advance for your help!
1 Like
You should use the action “CSV Creator - New file From base64” after the action “Create a CSV from JSON (SSA)”.
So as follow :
Step 1 - Create a CSV from JSON (SSA)
Step 2 - CSV Creator - New file From base64
- WebsiteHomeURL : Website home URL
- name : choose_a_name_for_the_file.csv
- contents : Result of step 1’s base64 Text
Step 3 - Send email
- File : Result of step 2 (or maybe https:Result of step 2)
1 Like
Thanks Pierre,
I added the step 2 “CSV Creator - New file from Base64” with Result of Step 1 (Create CSV from JSON (SSA)'s Base64 Text)in the contents
In the step 3 send email, you do need to add "https:" in front of result of step2 (—otherwise the email still doesn’t include the attachment)
I’m not sure if there’s a cleaner way to do this, but I ended up using a custom state to concatenate "https:" with the result of Step 2. Then I entered the custom state in the file field of my email, and it works.
The email correctly includes the CSV file!
Thanks again 
1 Like