Title says the root of the problem. I’m thinking this is because CORS, but I’ve had no luck with
fetch or the newly introduced
Finding the same thing with two different APIs:
The more frustrating issue I’m running into is that there’s no error message or anything I can find in the stack using
debugger; - the script exists and there’s simply no output.
Could this be because Airtable scripts don’t support “redirect: follow”?
If so, is the best workaround to dump all the logic into a cloud function like Google Apps Scripts, Netlify Functions, Code by Zapier, etc?
@Bill.French thank you! You led me to the solution:
The Stripe API does work within an Airtable Script - I was missing an
await before my
remoteFetchAsync call, which was causing the empty output.
The Toggl API does not work within an Airtable Script, probably because of the
redirect: follow method. When I added the
await, the fetch returned a
400: Bad Request, which I’ll assume is because of the
The Toggl API call worked perfectly from within an Autocode endpoint that took me about 15 minutes to set-up. Thanks for the referral :crown:
Excellent - this [Autocode] integration platform is firing on most of the cylinders and checking almost all of the boxes now. And they have a pretty nice free tier, so that’s especially helpful for prototyping solutions.