We’re excited to open up a beta for a new remoteFetchAsync function in the Scripting App.
One of the most common issues we see users run into when writing scripts is in trying to use the fetch API to communicate with an external service. Because Scripting App scripts run directly in the user’s browser, fetch requests will be blocked by the browser if the target server doesn’t support Cross-Origin Resource Sharing (CORS).
The new remoteFetchAsync method transmits the request from Airtable’s own servers rather from the user’s browser, thereby getting around CORS issues. remoteFetchAsync works very similarly to fetch and expects the same inputs, except for a handful of “gotchas” stemming from the fact that this is run from a backend.
We’d love to get your feedback on this new API.
To sign up for the beta, fill out the form here and we’ll enable the beta on your account. You’ll then be able to check out the documentation for remoteFetchAsynchere.
Hi @Taylor_Savage , @Stephen_Suen ,
This seems to be a huge New Year’s gift from Airtable !
It’s an “anti-CORS Error” for the Scripting App : this time, Airtable touched a subject that had already been poisoning development hours as often as that !
Let’s welcome, applaud and hurry to subscribe to this Beta to confront it with our previous nightmares !