Answered
I am able to follow the basic steps to creating a zap in Zapier, but when it comes to capturing looped data that is entered within an app you have to use a csv file for those unique items. I see that we can download these files (csv) and even have them emailed on a schedule, so the automation is there.
My question pertains to how to get that file to zapier from an email. Not sure you can. I assume this is where the power of API comes in and I do not know how to set this up.
I submitted a help ticket but wanted to see if anyone has been able to solve this without API.
0
Comments
Please sign in to leave a comment.
Hi John,
I'm hoping other people chime in, but I think you could do it using Google Sheets (instead of the emailed CSV). What do you want to do with the data once it's in Zapier (eg what are you trying to connect it to)?
Edit: I'm having reading comprehension problems, John. I see that you're trying to get the data into Google Sheets. That should be possible without needing the CSV, but let me double check with the loops.
Hi John,
So here's what I did to get the Zap to take the file in the email and get it into google sheets.
Trigger:
My trigger is a new labeled email in gmail (in my case, the label is submissions, and I have a filter in my inbox sending anything with auto-results into this folder, but you could do that manually).
Action:
The action is to upload a file in google drive. Then I mapped the email attachment to the file. Here's the key: there's an option under the file field that asks if you want to convert to document. You want to select yes - this will turn the submission into a google sheet.
When I open the sheet in google drive now, each loop item is its own line (which I think was what you were going for, but obviously correct me if I'm wrong).
One thing I did notice is that when it's coming over as the scheduled report instead of an individual submission, it's getting zipped. Google drive has some add-ons that allow you to unzip (I'm using one called zip extractor), but obviously that's less automated than is ideal. I'll play with this some more and see if I can get around this using reports, but if possible you could just add an email address to each submission with the specific goal of triggering this Zap.
So Julia was able to show me a super simply fix and it was something that I overlooked.
When setting up a zap that is pulling info from a looped screen you need to select "Create Spreadsheet Row(s)" under "show less common options"
When this is selected it will allow you to see the options for the looped screen and pulls each submitted line to create a new row.
Awesome! And so much easier. Thanks for the update, John!
this sounds like a great workaround, the only thing is that the least you can schedule the CSV to be emailed is daily, so if multiple submissions are being done throughout the day, Google sheets can only be updated once in 24 hours.
or is there a workaround for that too?
Unless I'm misunderstanding, if you set it up to collect new spreadsheet rows via the Zap, it would update every time there is a submission and there would be no need for the email.