I need to get the data of a CSV file into Make with an instant webhook once it gets submitted through a form.
- I tried triggering a webhook when a new file gets uploaded in Airtable, but this doesn’t bring the CSV data or link with it so I can’t use it in Make.
- I also tried with a watch file upload in Google drive but the problem is that the webhook doesn’t get triggered instantly. The scenario only starts when I set it to, so not when data arrives.
Any ideas or workarounds for this?
Hello @Sam_Bastiaens,
Are you able to explain your workflow in a little more detail?
I’m seeing Airtable, CSV file, Google Drive, Webhook, but just not seeing how you’d like it all to fit together…
What is the trigger?
Where is the file stored, who puts it there, and how?
Thanks!
Hey Donald,
Thanks for getting back.
I’ll try to explain the flow below again. It’s pretty simple actually.
A form is submitted. The form contains a CSV file. This can be either an Airtable form or Google form.
The Make scenario gets triggered by a webhook and we should get a way to get the CSV data into the Make scenario. But this is where the problem comes in.
If I use Airtable and fetch the record associated with this form that’s been submitted, there no CSV data.
If we use a Google form and just get the CSV in Drive we can use a Watch drive files module, but the problem is it’s a pending trigger so doesn’t fire as soon as the file gets uploaded.
From there it’s to upload the CSV to Millionverifier in the next module but I know how to do that, the problem is just getting the CSV data into the scenario the first place.
Got it. We just need to tackle one a time.
If you want two different triggers (a Google Form Submission and an Airtable Form Submission), you’re going to need at least 1 scenario for each.
I would separate your scenarios, one to handle the Google Form and the other to handle the Airtable form.
Both should get the info you need and pass it on to a third scenario that accepts the data in a “standard” format.
Build out the third scenario such that anything, form or otherwise, is able to submit data to it, including the form fields, CSV data, etc…
For Airtable, why do you say there is no CSV data? Do you think it’s a timing issue and the data isn’t available as quickly as the form is submitted?
How are you fetching the record, which module are you using and how are you locating the record that the form created?
Hello @Sam_Bastiaens,
A suggestion from @Donald_Mitchell is also works.
But I’m thinking about another type of workflow to implement this.
→ Use Airtable as a Data Storage for all types of forms.
→ Create Table(response), set all the fields, and then go to Table Permission set Who can create records?-> specific users and then select a user with API access.
⇒ Now Go to make and set up a Scenario using Airtable’s “Watch Records” when the record is created on that specific response table.
- Remember when the Airtable form is submitted that itself creates a new record in that response table.
- To handle Google Form responses create another scenario when that Google form is submitted and store that data in Airtable.
Now 1. and 2. both of them trigger the “Watch Records” scenario.
Your CSV is always stored in Airtable’s Attachment field.
The attachment field always returns the public download URL for the file and download URLs stay active for at least 2 hours after receiving them. Airtable Attachment URL Behavior | Airtable Support
After you get that attachment URL just use HTTP to download it and then use Parse CSV.
You get all the CSV data in multiple bundles.
I hope this helps you.
P.S.: Always search first, Check Make Academy. If this is helpful, mark it as a solution
and
Need expert help or have questions? Contact or comment below! 
1 Like