I made the “forms → make → airtable” thing work.
But with a form that includes a file upload (. jpg) the airtable never receives a file or the path to the file (in divhunt storage).
All the data lands in the divhunt form, including the picture, so that works as intended.
But it lands NOT in the airtable that I connected via make.
All the other data from the other form fields of this form lands in airtable.
I tried to receive the pic in the airtable field as short text and as file, but neither one works.
Can someone help me with that?
Many thanks in advance.
J.
Dear @MixxMaster reading your posts, you seem to have mastered the REST API connection. Did you manage to do POST Requests successfully? I struggle to get dynamic data int the body section of the REST mask…
When testing with a static version it works great and I get data in airtable. But the goal is to fill data from my form in an array or vars via custom js and then use this in the body.
Do you might have a idea? would appreciate your help and be very thankful. Greetings, J.
I use POST to get a Bearer token that I cache for 15 minutes, and then it renews. For any subsequence requests, this token is accessed through the ${rest-get('token')} and inserted in the “HEADERS” section of the POST request as Authorization : Bearer ${rest->get('token')} (in my case)
I suspect you can save your data from the form in a variable (or several), access those variables in REST, and insert them in the HEADERS section as needed… But as I don’t really know your way, it’s hard to give any advice.
Variables live in different global sections like: ${rest->get('variable)} | ${value->get('variable)} | ${page->get('variable')} | ${data->get('variable)} | etc..
@dejan was a big help (crucial) to get everything working for me as there is basically no documentation yet…
@MixxMaster thanks a lot, I think the variables approach is a very good idea, that I will try.
And then putting together the body like in your given examples should be a breeze.
Thanks a lot!!!
