Automations error (but not on Block): Response status was 302 'Moved Temporarily' but redirect mode was set to 'error'
Yes! I am getting that same error just in the last 3 days, and only when it is run as an automation.
You can see below that it worked fine for several days, then 3 days in a row it failed, with the message you described (except mine says it was “permanently” moved):
In my case, the API I was using did change their URL scheme. But I adjusted my script to match their new URL scheme after that very first failure. I verified that it worked. Next day, it failed to fetch from the updated URL with the same error. Today, it seems to have corrected itself :man_shrugging: . Who knows?
Thank you and super interesting! Hope it corrects itself.
It looks like Google Scripts Webapps don’t actually expose the final URL for security reasons, so what’s served up as their endpoint is actually just a redirect.
For some reason, Airtable Scripting Blocks can follow that redirect correctly, but automations can’t.
To illustrate – the expected value returned is “128” here.
SCRIPTING BLOCK
AUTOMATION TOOL
Thanks! I’m unfamiliar with the followRedirects parameter but I gave it a shot in the header and it didn’t work. I also tried the “redirect: follow” parameter and received this error:
That does appear to confirm the issue. Wonder if there are any workarounds.
This seems to be an accurate assessment of the issue.
I think the right approach (when attempting to create a seamless integration between Action Scripts and Google Apps Script) is to make requests using the redirects : "follow" option in Fetch().
let postOptions = {
method: "post",
headers: {
'Accept' : 'application/json'
},
redirect : "follow",
body: JSON.stringify(payload)
}
When doing so, the error message is far more revealing: :slightly_smiling_face: Airtable simply doesn’t support the ability to follow API platforms that require response redirects. I also see no workaround for harvesting the response.header.location to perform the correct [redirected] request.
I believe Airtable needs to remedy this and soon because it makes it entirely impossible to integrate Google Apps Script, Google Cloud Platform, and many other systems that use this technique for stringent security measures.
My workaround (for now) is a Firebase or Google Cloud function as the proxy much the way @Mike_Mauer has done with PipeDrive.
