Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

File added to Amazon S3 as text instead of CSV

  • July 21, 2021
  • 3 replies
  • 1339 views
W

I have a Zap set up between Zendesk and s3, but when grabbing the file from s3 the file is being created as a full text file. Does anyone have advice on configuring the file to be transferred as a .csv?

 

Best answer by SamB

Just wanted to follow up here as in the screenshot it looks like the Mimetype field hasn’t been specified. This may well be why Amazon S3 was having some trouble reading the file as a CSV. 

Setting the Mimetype field to be text/csv should help to let Amazon S3 know that it’s a CSV file that’s being uploaded.

If that doesn’t work, then it may be worth uploading the file to another app first to generate the CSV file before sending it to Amazon S3. For example, you could use an app like EasyCSV to create the CSV. Then in the File field on the Amazon S3 step, you’d select the file generated from the EasyCSV step. 

W
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Troy TessaloneZapier Orchestrator & Solution Partner
  • Zapier Orchestrator & Solution Partner
  • July 25, 2021

Hi @Will Schmitz 

Please post screenshots of how your Zap step is configured, thanks.

⚡ Troy Tessalone - AutomationAce.com | Platinum Zapier Solution Partner | #1 Zapier Community Contributor
W
  • Will SchmitzBeginner
  • Author
  • Beginner
  • July 26, 2021

This post has been edited by a moderator to remove sensitive information. Please remember to obfuscate any personally identifiable information prior to posting as this is a public forum. 


cc686450f75dd182ab1fb1535b460bc8.png

I have created a partial workaround using | as a delimitator, but would prefer the file uploaded to actually be .csv file type 

SamB
Community Manager
Forum|alt.badge.img+11
  • SamBCommunity Manager
  • Community Manager
  • Answer
  • September 21, 2021

Just wanted to follow up here as in the screenshot it looks like the Mimetype field hasn’t been specified. This may well be why Amazon S3 was having some trouble reading the file as a CSV. 

Setting the Mimetype field to be text/csv should help to let Amazon S3 know that it’s a CSV file that’s being uploaded.

If that doesn’t work, then it may be worth uploading the file to another app first to generate the CSV file before sending it to Amazon S3. For example, you could use an app like EasyCSV to create the CSV. Then in the File field on the Amazon S3 step, you’d select the file generated from the EasyCSV step. 

Terms & ConditionsAccessibility statement